Johannes Berg ad4bb6f888 cfg80211: disallow bridging managed/adhoc interfaces ... A number of people have tried to add a wireless interface (in managed mode) to a bridge and then complained that it doesn't work. It cannot work, however, because in 802.11 networks all packets need to be acknowledged and as such need to be sent to the right address. Promiscuous doesn't help here. The wireless address format used for these links has only space for three addresses, the * transmitter, which must be equal to the sender (origin) * receiver (on the wireless medium), which is the AP in the case of managed mode * the recipient (destination), which is on the APs local network segment In an IBSS, it is similar, but the receiver and recipient must match and the third address is used as the BSSID. To avoid such mistakes in the future, disallow adding a wireless interface to a bridge. Felix has recently added a four-address mode to the AP and client side that can be used (after negotiating that it is possible, which must happen out-of-band by setting up both sides) for bridging, so allow that case. Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Acked-by: Stephen Hemminger <shemminger@vyatta.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>		2009-11-19 11:08:54 -05:00
..
acpi
asm-generic
crypto
drm
keys
linux	cfg80211: disallow bridging managed/adhoc interfaces	2009-11-19 11:08:54 -05:00
math-emu
media
mtd
net	cfg80211: introduce capability for 4addr mode	2009-11-19 11:08:53 -05:00
pcmcia
rdma
rxrpc
scsi
sound
trace
video
xen
Kbuild