Home » Mailing list archives » linux-ath5k-devel » 2010 » March » 21

[ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33

Previous thread: [ath5k-devel] [PATCH 1/3] ath5k: rework calibration timer by Bruno Randolf on Friday, March 19, 2010 - 3:09 am. (10 messages)

Next thread: [ath5k-devel] Atheros HW/cfg80211 ignore nonUS regdom with "EEPROM regdomain: 0x0" by Jiri Moravec on Monday, March 22, 2010 - 4:41 am. (3 messages)
[view original message]
From: Jiri Moravec
Subject: [ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33
Date: Saturday, March 20, 2010 - 6:06 pm

I can't add wlan0 interface into bridge with kernel >= 2.6.33. Am I alone with such problem?

2.6.32.10:
------------------------------------------------------------------------------
~ # modprobe ath5k
~ # brctl addbr br0
~ # brctl addif br0 wlan0
~ # brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.0019e08d0c32       no              wlan0
~ # modprobe sky2
~ # brctl addif br0 eth1
~ # brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.0019e08d0c32       no              eth1
                                                        wlan0
------------------------------------------------------------------------------

2.6.33.1/2.6.34-rc2:
------------------------------------------------------------------------------
~ # modprobe ath5k
~ # brctl addbr br0
~ # brctl addif br0 wlan0
can't add wlan0 to bridge br0: Operation not supported
~ # modprobe sky2
~ # brctl addif br0 eth1
~ # brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.0022158079ab       no              eth1
------------------------------------------------------------------------------

PCI card:
03:06.0 Ethernet controller: Atheros Communications Inc. AR5413 802.11abg NIC (rev 01)
        Subsystem: Atheros Communications Inc. EnGenius EMP-8602 (400mw) or Compex WLM54AG (SuperAG)
        Flags: bus master, medium devsel, latency 168, IRQ 21
        Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2
        Kernel driver in use: ath5k
        Kernel modules: ath5k
03:06.0 0200: 168c:001b (rev 01)
        Subsystem: 168c:2062
        Flags: bus master, medium devsel, latency 168, IRQ 21
        Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [44] Power Management version 2
        Kernel driver in use: ath5k
        Kernel modules: ath5k


Thanks for your help.

Jiri ...
[ message continues ]
[view original message]
From: Pavel Roskin
Subject: Re: [ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33
Date: Saturday, March 20, 2010 - 11:39 pm

It's no longer possible to add an interface in the managed mode to a
bridge.  You should run hostapd first to pure the interface to the
master mode.

Bridging doesn't work on the station side anyway because the 802.11
header has three addresses (except when WDS is used) omitting the
address that would be needed for a station to send or receive a packet
on behalf of another system.

-- 
Regards,
Pavel Roskin
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

[ message continues ]
[view original message]
From: Jiri Moravec
Subject: Re: [ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33
Date: Sunday, March 21, 2010 - 2:09 am

Thanks for clarification.

_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

[ message continues ]
[view original message]
From: Gus Wirth
Subject: Re: [ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33
Date: Sunday, March 21, 2010 - 9:15 am

But there are ways around that. For example, there is a patch called
arpnat that affects ebtables, used by projects like Gargoyle router that
does for MAC addresses that IP masquerading does for IP addresses.

As such, it is very useful to have a node in managed (station) mode be
able to be part of a bridge, as it allows the creation of an essentially
transparent connection.

Gus
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

[ message continues ]
[view original message]
From: Pavel Roskin
Subject: Re: [ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33
Date: Sunday, March 21, 2010 - 7:03 pm

As it stands now, it's more common that users without that patch try to
use bridging on the station side.  When/if arpnat is applied to the
kernel, the check for managed mode interfaces will need to be revised.

-- 
Regards,
Pavel Roskin
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

[ message continues ]
[view original message]
From: Jiri Moravec
Subject: Re: [ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33
Date: Monday, March 22, 2010 - 8:05 am

Hi
On some openwrt pages about Gargoyle and arpnat I found link to Felix Fietkau's patch
which was finally accepted to vanilla as commit 9bc383de37090ba7ca3ff32a12c9d809dc5867f0.
From this point there is probably support for 4addr mode (STATION/AP_VLAN), but what
is probably missing is athk5 support for it. Am I correct? Can somebody clarify this?

Thanks
Jiri Moravec

_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

[ message continues ]
[view original message]
From: Luis R. Rodriguez
Subject: Re: [ath5k-devel] can't add ath5k into bridge on kernel >=2.6.33
Date: Monday, March 22, 2010 - 10:45 am

I only recently got to pick Felix's brain about this. From what I gathered
essentially what you need:

  * on the STA add the 4-address flag, for now this requires using the iw add 4addr flag, iw should
    support a change command but I don't think we have it yet on iw.
  * on the AP/STA side have support for this feature on the kernel/hostapd side (git versions will do)
  * on hostapd use the wds_sta flag
  * Add the STA WDS'd interface to the bridge, everything will take care of itself after that

So the STA with 4-address frame support will allow the bridging layer to send
802.3 frames to through the STA interface, it will send it to the AP,
the AP with support for this will detect it and create a local interface
for the "peer" for sending future frames to it.

If someone can add this to the wiki:

http://wireless.kernel.org/en/users/Documentation/hostapd

it would be appreciated.

  Luis
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

[ message continues ]
Previous thread: [ath5k-devel] [PATCH 1/3] ath5k: rework calibration timer by Bruno Randolf on Friday, March 19, 2010 - 3:09 am. (10 messages)

Next thread: [ath5k-devel] Atheros HW/cfg80211 ignore nonUS regdom with "EEPROM regdomain: 0x0" by Jiri Moravec on Monday, March 22, 2010 - 4:41 am. (3 messages)