mac80211: disallow bridging managed/adhoc interfaces
Subsystems (4)
RFC 1/1 mac80211: 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.
--- include/linux/if.h | 1 + net/bridge/br_if.c | 4 ++++ net/mac80211/cfg.c | 9 ++++++++- net/mac80211/iface.c | 17 +++++++++++++++-- 4 files changed, 28 insertions(+), 3 deletions(-)
include/linux/if.h +1 -0
@@ -70,6 +70,7 @@#define IFF_XMIT_DST_RELEASE 0x400/* dev_hard_start_xmit() is allowed to * release skb->dst */ +#define IFF_DONT_BRIDGE 0x800/* disallow bridging this ether dev */ #define IF_GET_IFACE 0x0001/* for querying only */ #define IF_GET_PROTO 0x0002
net/bridge/br_if.c +4 -0
@@ -390,6 +390,10 @@ int br_add_if(struct net_bridge *br, strif (dev->br_port !=NULL )return -EBUSY ; +/* No bridging devices that dislike that (e.g. wireless) */ +if (dev->priv_flags &IFF_DONT_BRIDGE ) +return -EINVAL ; + p =new_nbp (br, dev);if (IS_ERR (p))return PTR_ERR (p);
net/mac80211/cfg.c +8 -1
@@ -106,8 +106,15 @@ static int ieee80211_change_iface(struct params->mesh_id_len, params->mesh_id); -if (params->use_4addr >=0 ) +if (params->use_4addr >=0 ) { sdata->use_4addr = !!params->use_4addr; + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ; + +if ((sdata->vif.type ==NL80211_IFTYPE_STATION || + sdata->vif.type ==NL80211_IFTYPE_ADHOC ) && + !sdata->use_4addr) + sdata->dev->priv_flags |=IFF_DONT_BRIDGE ; + }if (sdata->vif.type !=NL80211_IFTYPE_MONITOR || !flags)return 0 ;
net/mac80211/iface.c +15 -2
@@ -769,6 +769,11 @@ int ieee80211_if_change_type(struct ieee sdata->local->hw.conf.channel->band); sdata->drop_unencrypted =0 ; sdata->use_4addr =0 ; +if (sdata->vif.type ==NL80211_IFTYPE_STATION || + sdata->vif.type ==NL80211_IFTYPE_ADHOC ) + sdata->dev->priv_flags |=IFF_DONT_BRIDGE ; +else + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ;return 0 ; }
@@ -843,8 +848,16 @@ int ieee80211_if_add(struct ieee80211_lo params->mesh_id_len, params->mesh_id); -if (params && params->use_4addr >=0 ) - sdata->use_4addr = !!params->use_4addr; +if (sdata->vif.type ==NL80211_IFTYPE_STATION || + sdata->vif.type ==NL80211_IFTYPE_ADHOC ) + sdata->dev->priv_flags |=IFF_DONT_BRIDGE ; +else + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ; + +if (params && params->use_4addr >0 ) { + sdata->use_4addr = true; + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ; + }mutex_lock (&local->iflist_mtx);list_add_tail_rcu (&sdata->list, &local->interfaces);
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 19 lines · Johannes Berg
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 segmentIn 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.
Quoted 6 lines
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 <[email protected]>
ACK -- we get these complaints fairly often...
I don't think I've sent the 4addr stuff to Dave yet. Should I just take this through my tree?
John
Signature · 6 lines
John W. Linville Someday the world will need a hero, and you [email protected] might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Johannes Berg
maintainerQuoted 8 lines · John W. Linville
Quoted 8 lines
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.
Quoted 6 lines
Quoted 1 line
Signed-off-by Johannes Berg <[email protected]>ACK -- we get these complaints fairly often...
I don't think I've sent the 4addr stuff to Dave yet. Should I just take this through my tree?
After ack from Stephen maybe?
johannes
net/bridge/br_if.c int br_add_if(struct net_bridge *br, str · line 395
Quoted 9 lines · On Tuesday 17 November 2009 14:46:25 Johannes Berg wrote:
net/bridge/br_if.c +3
-0@@ -390,6 +390,10 @@ int br_add_if(struct net_bridge *br, strif (dev->br_port !=NULL )return -EBUSY ; +/* No bridging devices that dislike that (e.g. wireless) */ +if (dev->priv_flags &IFF_DONT_BRIDGE ) +return -EINVAL ;
-EOPNOTSUPP?
That would probably produce a better error message in userspace.
Signature · 1 line
Greetings, Michael.
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Michael Buesch
Quoted 6 lines · On Tuesday 17 November 2009 14:46:25 Johannes Berg wrote:
net/bridge/br_if.c +0
-0@@ -390,6 +390,10 @@ int br_add_if(struct net_bridge *br, strif (dev->br_port !=NULL )return -EBUSY ;
Quoted 6 lines
net/bridge/br_if.c int br_add_if(struct net_bridge *br, str · line 395
Quoted 3 lines
net/bridge/br_if.c +3
-0+/* No bridging devices that dislike that (e.g. wireless) */ +if (dev->priv_flags &IFF_DONT_BRIDGE ) +return -EINVAL ;
-EOPNOTSUPP?
That would probably produce a better error message in userspace.
Yes, good point.
Signature · 6 lines
John W. Linville Someday the world will need a hero, and you [email protected] might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 7 lines · Michael Buesch
Quoted 6 lines · On Tuesday 17 November 2009 14:46:25 Johannes Berg wrote:
net/bridge/br_if.c +0
-0@@ -390,6 +390,10 @@ int br_add_if(struct net_bridge *br, strif (dev->br_port !=NULL )return -EBUSY ;
Quoted 6 lines
net/bridge/br_if.c int br_add_if(struct net_bridge *br, str · line 395
Quoted 3 lines
net/bridge/br_if.c +3
-0+/* No bridging devices that dislike that (e.g. wireless) */ +if (dev->priv_flags &IFF_DONT_BRIDGE ) +return -EINVAL ;
-EOPNOTSUPP?
That would probably produce a better error message in userspace.
Good idea, will wait a bit for other comments and fix this when I send as [PATCH].
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · On Tue, 17 Nov 2009 15:07:48 +0100 Johannes Berg <[email protected]>…
Quoted 7 lines · Michael Buesch
Quoted 6 lines · On Tuesday 17 November 2009 14:46:25 Johannes Berg wrote:
net/bridge/br_if.c +0
-0@@ -390,6 +390,10 @@ int br_add_if(struct net_bridge *br, strif (dev->br_port !=NULL )return -EBUSY ;
Quoted 6 lines
Quoted 6 lines
net/bridge/br_if.c int br_add_if(struct net_bridge *br, str · line 395
Quoted 3 lines
net/bridge/br_if.c +3
-0+/* No bridging devices that dislike that (e.g. wireless) */ +if (dev->priv_flags &IFF_DONT_BRIDGE ) +return -EINVAL ;
-EOPNOTSUPP?
That would probably produce a better error message in userspace.
But there are people bridging wireless, and hostap even has a mode for that. Especially people are bridging to wireless when the other interfaces are VMs.
Quoted 2 lines · Stephen Hemminger
But there are people bridging wireless, and hostap even has a mode for that.
But that's the AP side, which this patch doesn't attempt to prevent. It just makes no sense to bridge when connected to an AP or part of an IBSS.
johannes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · On Tue, 17 Nov 2009 17:43:43 +0100 Johannes Berg…
Quoted 2 lines · Stephen Hemminger
But there are people bridging wireless, and hostap even has a mode for that.
But that's the AP side, which this patch doesn't attempt to prevent. It just makes no sense to bridge when connected to an AP or part of an IBSS.
Then how does this work now? And will your change break it?
kvm1
/
====> wlan0 --- bridge-- kvm2
\
kvm3--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Johannes Berg
maintainerQuoted 7 lines · Stephen Hemminger
Then how does this work now? And will your change break it?
kvm1 / ====> wlan0 --- bridge-- kvm2 \ kvm3
What's the type of wlan0? If it's managed, i.e. connected to an AP, it /doesn't/ actually work now, which is my point.
johannes
Quoted 13 lines · Stephen Hemminger
Quoted 9 lines · On Tue, 17 Nov 2009 17:43:43 +0100 Johannes Berg…
Quoted 2 lines · Stephen Hemminger
But there are people bridging wireless, and hostap even has a mode for that.
But that's the AP side, which this patch doesn't attempt to prevent. It just makes no sense to bridge when connected to an AP or part of an IBSS.
Quoted 7 lines
Then how does this work now? And will your change break it?
kvm1 / ====> wlan0 --- bridge-- kvm2 \ kvm3
Are you sure 'bridge' isn't NAT-ed to wlan0 like libvirt/etc do by default? That's about the only way it can possibly work correctly with wifi.
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Johannes Berg
maintainerRFC v2 1/1 mac80211: disallow bridging managed/adhoc interfaces
In reply to Johannes BergA 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.
---
v2: * change error code as requested by Michael
* disallow changing wireless mode on a bridged iface
Should more (all?) of this be in cfg80211?
include/linux/if.h | 1 + net/bridge/br_if.c | 4 ++++ net/mac80211/cfg.c | 9 ++++++++- net/mac80211/iface.c | 22 ++++++++++++++++++++-- 4 files changed, 33 insertions(+), 3 deletions(-)
include/linux/if.h +1 -0
@@ -70,6 +70,7 @@#define IFF_XMIT_DST_RELEASE 0x400/* dev_hard_start_xmit() is allowed to * release skb->dst */ +#define IFF_DONT_BRIDGE 0x800/* disallow bridging this ether dev */ #define IF_GET_IFACE 0x0001/* for querying only */ #define IF_GET_PROTO 0x0002
net/bridge/br_if.c +4 -0
@@ -390,6 +390,10 @@ int br_add_if(struct net_bridge *br, strif (dev->br_port !=NULL )return -EBUSY ; +/* No bridging devices that dislike that (e.g. wireless) */ +if (dev->priv_flags &IFF_DONT_BRIDGE ) +return -EOPNOTSUPP ; + p =new_nbp (br, dev);if (IS_ERR (p))return PTR_ERR (p);
net/mac80211/cfg.c +8 -1
@@ -106,8 +106,15 @@ static int ieee80211_change_iface(struct params->mesh_id_len, params->mesh_id); -if (params->use_4addr >=0 ) +if (params->use_4addr >=0 ) { sdata->use_4addr = !!params->use_4addr; + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ; + +if ((sdata->vif.type ==NL80211_IFTYPE_STATION || + sdata->vif.type ==NL80211_IFTYPE_ADHOC ) && + !sdata->use_4addr) + sdata->dev->priv_flags |=IFF_DONT_BRIDGE ; + }if (sdata->vif.type !=NL80211_IFTYPE_MONITOR || !flags)return 0 ;
net/mac80211/iface.c +20 -2
@@ -745,6 +745,11 @@ int ieee80211_if_change_type(struct ieeeif (type == sdata->vif.type)return 0 ; +/* if it's part of a bridge, reject changing type to station/ibss */ +if (sdata->dev->br_port && (type ==NL80211_IFTYPE_ADHOC || + type ==NL80211_IFTYPE_STATION )) +return -EBUSY ; +/* Setting ad-hoc mode on non-IBSS channel is not supported. */ if (sdata->local->oper_channel->flags &IEEE80211_CHAN_NO_IBSS && type ==NL80211_IFTYPE_ADHOC )
@@ -769,6 +774,11 @@ int ieee80211_if_change_type(struct ieee sdata->local->hw.conf.channel->band); sdata->drop_unencrypted =0 ; sdata->use_4addr =0 ; +if (sdata->vif.type ==NL80211_IFTYPE_STATION || + sdata->vif.type ==NL80211_IFTYPE_ADHOC ) + sdata->dev->priv_flags |=IFF_DONT_BRIDGE ; +else + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ;return 0 ; }
@@ -843,8 +853,16 @@ int ieee80211_if_add(struct ieee80211_lo params->mesh_id_len, params->mesh_id); -if (params && params->use_4addr >=0 ) - sdata->use_4addr = !!params->use_4addr; +if (sdata->vif.type ==NL80211_IFTYPE_STATION || + sdata->vif.type ==NL80211_IFTYPE_ADHOC ) + sdata->dev->priv_flags |=IFF_DONT_BRIDGE ; +else + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ; + +if (params && params->use_4addr >0 ) { + sdata->use_4addr = true; + sdata->dev->priv_flags &= ~IFF_DONT_BRIDGE ; + }mutex_lock (&local->iflist_mtx);list_add_tail_rcu (&sdata->list, &local->interfaces);
A message that is not in the archive (sent off-list or not yet received): 1258490898.21197.42.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 int ieee80211_if_change_type(struct ieee · line 751
Quoted 10 lines · Johannes Berg
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 renamed from net/mac80211/iface.c 2009-11-17 14:20:19.000000000 +0100 +4
-0@@ -745,6 +745,11 @@ int ieee80211_if_change_type(struct ieee if (type == sdata->vif.type) return 0; + /* if it's part of a bridge, reject changing type to station/ibss */ + if (sdata->dev->br_port && (type == NL80211_IFTYPE_ADHOC || + type == NL80211_IFTYPE_STATION)) + return -EBUSY;
Busy doesn't seem like the right error here ... maybe use -EOPNOTSUPP like the next test?
Thanks,
Signature · 8 lines
Julian Calaby Email: [email protected] .Plan: http://sites.google.com/site/juliancalaby/ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Johannes Berg
maintainerQuoted 7 lines · Julian Calaby
Quoted 6 lines · Johannes Berg
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 renamed from net/mac80211/iface.c 2009-11-17 14:20:19.000000000 +0100 +0
-0@@ -745,6 +745,11 @@ int ieee80211_if_change_type(struct ieee if (type == sdata->vif.type) return 0;
Quoted 7 lines
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 int ieee80211_if_change_type(struct ieee · line 751
Quoted 4 lines
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 renamed from net/mac80211/iface.c 2009-11-17 14:20:19.000000000 +0100 +4
-0+ /* if it's part of a bridge, reject changing type to station/ibss */ + if (sdata->dev->br_port && (type == NL80211_IFTYPE_ADHOC || + type == NL80211_IFTYPE_STATION)) + return -EBUSY;Busy doesn't seem like the right error here ... maybe use
-EOPNOTSUPPlike the next test?
Not sure, it's a temporary error and you can fix it by removing it from the bridge, so it's "busy" in the sense that it is fixed to the current mode or any other bridging mode by being in the bridge ... it's not that it doesn't support the mode.
johannes
Quoted 16 lines · Johannes Berg
Quoted 7 lines · Julian Calaby
Quoted 6 lines · Johannes Berg
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 renamed from net/mac80211/iface.c 2009-11-17 14:20:19.000000000 +0100 +0
-0@@ -745,6 +745,11 @@ int ieee80211_if_change_type(struct ieee if (type == sdata->vif.type) return 0;Quoted 7 lines
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 int ieee80211_if_change_type(struct ieee · line 751
Quoted 4 lines
net/mac80211/iface.c 2009-11-17 17:56:08.000000000 +0100 renamed from net/mac80211/iface.c 2009-11-17 14:20:19.000000000 +0100 +4
-0+ /* if it's part of a bridge, reject changing type to station/ibss */ + if (sdata->dev->br_port && (type == NL80211_IFTYPE_ADHOC || + type == NL80211_IFTYPE_STATION)) + return -EBUSY;Busy doesn't seem like the right error here ... maybe use
-EOPNOTSUPPlike the next test?
Quoted 4 lines
Not sure, it's a temporary error and you can fix it by removing it from the bridge, so it's "busy" in the sense that it is fixed to the current mode or any other bridging mode by being in the bridge ... it's not that it doesn't support the mode.
Arguably the test following this (ensuring that we don't set ad-hoc mode on a non-ad-hoc channel) is equally temporary - i.e. both actions require the user to do something before they'll work again.
But then, the test after that - for whether the interface is running - returns -EBUSY - and is just as easy to remedy, so........
Thanks,
Signature · 4 lines
Julian Calaby Email: [email protected] .Plan: http://sites.google.com/site/juliancalaby/
Quoted 19 lines · On Tue, 17 Nov 2009 21:48:18 +0100 Johannes Berg <[email protected]>…
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 segmentIn 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.
Quoted 6 lines
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 <[email protected]>
Looks good, maybe true four-address mode support will be available more widely, and this will no longer be an issue.
Johannes Berg
maintainerQuoted 7 lines · Stephen Hemminger
Quoted 4 lines
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.
Looks good, maybe true four-address mode support will be available more widely, and this will no longer be an issue.
Doubt it, it breaks the current 802.11 standard, and I think 802.1X too if you use WPA/RSN. Anyway, thanks.
I'll take a look tomorrow if we can do this generically in cfg80211, and then send a [PATCH] either way.
johannes
Quoted 3 lines
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
[...]
Quoted 2 lines
To avoid such mistakes in the future, disallow adding a wireless interface to a bridge.
As someone who's been bitten by this, I fully support this change. Still, it makes me wonder: my broadcom-based home-router using the wl.o driver can be set in "client bridge" mode. How does it work?
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): jwvy6m4bnqp.fsf-monnier+gmane.linux.kernel.wireless.general-mXXj517/[email protected]
Quoted 10 lines · Stefan Monnier
Quoted 3 lines
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
[...]
Quoted 2 lines
To avoid such mistakes in the future, disallow adding a wireless interface to a bridge.
As someone who's been bitten by this, I fully support this change. Still, it makes me wonder: my broadcom-based home-router using the wl.o driver can be set in "client bridge" mode. How does it work?
If I'm not mistaken, that has a bunch of code embedded in it that among other things can do a layer-2 version of NAT to rewrite the MAC adresses for frames on the air.
YMMV...
John
Signature · 6 lines
John W. Linville Someday the world will need a hero, and you [email protected] might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · John W. Linville
Quoted 3 lines
As someone who's been bitten by this, I fully support this change. Still, it makes me wonder: my broadcom-based home-router using the wl.o driver can be set in "client bridge" mode. How does it work?
If I'm not mistaken, that has a bunch of code embedded in it that among other things can do a layer-2 version of NAT to rewrite the MAC adresses for frames on the air.
Yeah, that's how it works. You can probably achieve the same effect with the ebtable_nat module in ebtables but I've never even attempted to try that.
johannes
Quoted 2 lines · Johannes Berg
To avoid such mistakes in the future, disallow adding a wireless interface to a bridge.
Hello,
after the latest git pull my Linux AP stopt working because the system is not allowed to add the wlan0 interface to a bridge.
I bisected the problem and ended up here.
So my question is, what is the right way to go after this patch, to bridge the wireless with the wired network interface on the AP, if bridging of the wlan interface isn't allowed anymore?
Routing isn't an option here, because the two interfaces should form one common boadcast domain.
It have worked fine all the time and the hostapd documantaion at the linuxwireless.org
(http://linuxwireless.org/en/users/Documentation/hostapd#Configuring_hostapd)
describes how to bridge both interfaces on the AP, too.
And from now on all that should be wrong?
Sorry, I am confused.
Johannes Berg
maintainerQuoted 9 lines · Markus Baier
Quoted 2 lines · Johannes Berg
To avoid such mistakes in the future, disallow adding a wireless interface to a bridge.
Hello,
after the latest git pull my Linux AP stopt working because the system is not allowed to add the wlan0 interface to a bridge.
You're mistaken. You _can_ still bridge an AP interface, it just needs to be in AP mode. You should be using hostapd to control the bridging.
johannes
Hi, thanks for the fast reply
Ok, that is my fault.
At the moment I bridge the interfaces at boot time before the start of the hostapd daemon.
So I will remove the wlan0 line from bridge section of the gentoo net rc-script and hope that hostapd will take over that task.
Tanks,
Markus
Johannes Berg
maintainerQuoted 3 lines · Markus Baier
So I will remove the wlan0 line from bridge section of the gentoo net rc-script and hope that hostapd will take over that task.
Well you do have to configure it to do that, but that should be one line in the hostapd config.
johannes