Hi Javier
I applied your patch too, but it didn't help.
I manage now to have both networks up, the 802.11s network on the mesh0
interface and the hostapd runing on the bridge br0 and wlan0 interface setting
up a 802.11g network.
However, either the 802.11s works, but the hostapd has some issues (see below
for details), or the hostapd runs smoothly, but the mesh network is not
working. Both together does not work.
I'm using the git versions of compat-wireless and hostapd from late december
2011 with a 2.6.37.6 kernel.
I set up the interfaces as follows:
iw phy phy0 interface add wlan0 type __ap
iw phy phy0 interface add mesh0 type mp mesh_id uavmesh
brctl addbr br0
ip link set down dev wlan0
ip link set down dev mesh0
iw dev mesh0 set channel 1
ip link set address 00:12:cf:d2:dc:23 dev wlan0
ip link set address 00:12:cf:d2:dc:24 dev mesh0
brctl addif br0 wlan0
brctl addif br0 mesh0
ip addr add 0.0.0.0/0 dev mesh0
ip addr add 0.0.0.0/0 dev wlan0
ip link set address 00:12:cf:d2:dc:24 dev br0
ip link set dev mesh0 up
ip addr add 192.168.230.13/24 dev br0
ip link set up dev br0
hostapd -B /etc/hostapd.conf
/etc/init.d/rc.udhcpd start
The issue with this setup (udhcpd has no influence):
The mesh network works, but the hostapd access point has some issues: I can
connect with ubuntu notebooks. But the logs on the mesh node are full of the
following:
Jan 1 01:42:07 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 1 notification
Jan 1 01:42:07 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 4 notification
Jan 1 01:42:07 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 1/4 msg of 4-Way Handshake
Jan 1 01:42:07 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:07 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:07 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:07 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:07 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
received EAPOL-Key frame (4/4 Pairwise)
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:08 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 1 notification
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 4 notification
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 1/4 msg of 4-Way Handshake
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
received EAPOL-Key frame (2/4 Pairwise)
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
received EAPOL-Key frame (4/4 Pairwise)
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:08 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 1 notification
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 4 notification
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 1/4 msg of 4-Way Handshake
Jan 1 01:42:08 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
received EAPOL-Key frame (2/4 Pairwise)
Jan 1 01:42:08 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:09 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:09 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:09 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:09 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:09 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:09 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:09 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 1 notification
Jan 1 01:42:09 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 4 notification
Jan 1 01:42:09 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 1/4 msg of 4-Way Handshake
Jan 1 01:42:09 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:09 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:09 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:09 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 3/4 msg of 4-Way Handshake
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:10 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 1 notification
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 4 notification
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 1/4 msg of 4-Way Handshake
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
received EAPOL-Key frame (2/4 Pairwise)
Jan 1 01:42:10 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:10 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:10 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:10 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
received EAPOL-Key frame (2/2 Group)
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:10 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:10 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:10 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:10 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 1 notification
Jan 1 01:42:10 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 4 notification
Jan 1 01:42:11 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:11 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:11 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:11 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:11 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:11 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 1 notification
Jan 1 01:42:11 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
event 4 notification
Jan 1 01:42:11 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 1/4 msg of 4-Way Handshake
Jan 1 01:42:11 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:11 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:11 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:11 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:11 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
sending 3/4 msg of 4-Way Handshake
Jan 1 01:42:11 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 WPA:
pairwise key handshake completed (WPA)
Jan 1 01:42:12 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:12 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:12 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:12 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:12 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 2
Jan 1 01:42:12 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:12 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 0
Jan 1 01:42:13 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:13 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:13 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:13 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:13 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
Jan 1 01:42:13 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: association OK (aid 2)
Jan 1 01:42:13 uav4 daemon.info hostapd: wlan0: STA 00:16:ce:36:4d:46 IEEE
802.11: associated (aid 2)
Jan 1 01:42:13 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-REASSOCIATE.indication(00:16:ce:36:4d:46)
Jan 1 01:42:13 uav4 daemon.debug hostapd: wlan0: STA 00:16:ce:36:4d:46 MLME:
MLME-DELETEKEYS.request(00:16:ce:36:4d:46)
Jan 1 01:42:13 uav4 user.debug kernel: wlan0: moving STA 00:16:ce:36:4d:46 to
state 1
however, the connection seems to work more or less, thoug there is about 15%
packetloss (every few seconds).
With an android smartphone I can connect, but get disconected after ~20
seconds. Also iOS (iPhone and iPad) can connect but get disconnected after ~10
seconds.
I can ping the devices while they are connected.
A log of such a try to connect with the android smartphone looks like this:
Jan 1 02:07:13 uav4 daemon.debug hostapd: wlan0: STA 38:e7:d8:d2:8b:2e IEEE
802.11: authentication OK (open system)
Jan 1 02:07:13 uav4 daemon.debug hostapd: wlan0: STA 38:e7:d8:d2:8b:2e WPA:
event 0 notification
Jan 1 02:07:13 uav4 daemon.debug hostapd: wlan0: STA 38:e7:d8:d2:8b:2e MLME:
MLME-AUTHENTICATE.indication(38:e7:d8:d2:8b:2e, OPEN_SYSTEM)
Jan 1 02:07:13 uav4 daemon.debug hostapd: wlan0: STA 38:e7:d8:d2:8b:2e MLME:
MLME-DELETEKEYS.request(38:e7:d8:d2:8b:2e)
Jan 1 02:07:13 uav4 daemon.info hostapd: wlan0: STA 38:e7:d8:d2:8b:2e IEEE
802.11: authenticated
Jan 1 02:07:13 uav4 daemon.debug hostapd: wlan0: STA 38:e7:d8:d2:8b:2e IEEE
802.11: association OK (aid 1)
Jan 1 02:07:13 uav4 daemon.info hostapd: wlan0: STA 38:e7:d8:d2:8b:2e IEEE
802.11: associated (aid 1)
Jan 1 02:07:13 uav4 daemon.debug hostapd: wlan0: STA 38:e7:d8:d2:8b:2e MLME:
MLME-ASSOCIATE.indication(38:e7:d8:d2:8b:2e)
Jan 1 02:07:13 uav4 daemon.debug hostapd: wlan0: STA 38:e7:d8:d2:8b:2e MLME:
MLME-DELETEKEYS.request(38:e7:d8:d2:8b:2e)
Jan 1 02:07:13 uav4 user.debug kernel: wlan0: moving STA 38:e7:d8:d2:8b:2e to
state 2
my hostapd.conf looks like this:
interface=wlan0
bridge=br0
driver=nl80211
ssid=uavwlan
hw_mode=g
channel=1
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ignore_broadcast_ssid=0
dump_file=/root/hostapd.dump
logger_syslog=-1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0
wpa=1
wpa_passphrase=12341234
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP
eapol_version=1
auth_algs=3
eapol_key_index_workaround=0
eap_server=0
I tried also other hostapd.conf with wpa=0 and no special eap configurations.
Nothing helped.
So, if I change the way I set up my devices as follows (setting up mesh0 after
the start of hostapd):
iw phy phy0 interface add wlan0 type __ap
iw phy phy0 interface add mesh0 type mp mesh_id uavmesh
brctl addbr br0
ip link set down dev wlan0
ip link set down dev mesh0
iw dev mesh0 set channel 1
ip link set address 00:12:cf:d2:dc:23 dev wlan0
ip link set address 00:12:cf:d2:dc:24 dev mesh0
brctl addif br0 wlan0
brctl addif br0 mesh0
ip addr add 0.0.0.0/0 dev mesh0
ip addr add 0.0.0.0/0 dev wlan0
ip link set address 00:12:cf:d2:dc:24 dev br0
# ip link set dev mesh0 up <- don't set up mesh0 here
ip addr add 192.168.230.13/24 dev br0
ip link set up dev br0
hostapd -B /etc/hostapd.conf
/etc/init.d/rc.udhcpd start
ip link set dev mesh0 up <- set it up at the end
Then the hostapd works smoothly and I can connect with all devices. But, the
mesh network does not work.
iw dev mesh0 station dump outputs nothing. It seems that there is an issue
with hostapd running on the bridge containing a set up mesh0 interface.
That's how "ip addr list" looks like:
16: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000
link/ether 00:12:cf:d2:dc:23 brd ff:ff:ff:ff:ff:ff
inet6 fe80::212:cfff:fed2:dc23/64 scope link
valid_lft forever preferred_lft forever
17: mesh0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state
UNKNOWN qlen 1000
link/ether 00:12:cf:d2:dc:24 brd ff:ff:ff:ff:ff:ff
inet6 fe80::212:cfff:fed2:dc24/64 scope link
valid_lft forever preferred_lft forever
18: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN
link/ether 00:12:cf:d2:dc:24 brd ff:ff:ff:ff:ff:ff
inet 192.168.230.13/24 scope global br0
inet6 fe80::212:cfff:fed2:dc24/64 scope link
valid_lft forever preferred_lft forever
Is it correct that the bridge and mesh interface must have the same MAC
address, but wlan0 must have a different one?
Is it correct that the mesh interface must be "set up" before the bridge is
"set up" to work properly?
Is there anything wrong in my process to set up the entire system or in the
configuration?
Summary: if the mesh0 interface is set up (and the mesh network works),
hostapd as some issues. If the mesh interfaces are not set up, hostapd runs
ok.
Any ideas what the issue could be?
Thanks
Simon
On Friday 23 December 2011 07:32:33 Javier Cardona wrote:
> Hi Simon and Kai,
>
> Thanks for reporting this issue. This seems to be a sk buffer
> overrun, probably caused by this patch:
>
> commit 3b69a9c5f264d62a0cf46ea61ed3da732c1f88c2
> Author: Thomas Pedersen <[email protected]>
> Date: Wed Oct 26 14:47:25 2011 -0700
>
> mac80211: comment allocation of mesh frames
>
> Remove most references to magic numbers, save a few bytes and hopefully
> improve readability.
>
> Signed-off-by: Thomas Pedersen <[email protected]>
> Signed-off-by: John W. Linville <[email protected]>
>
> We'll fix that next year, when Thomas or myself return from vacation.
> If you need something sooner than that, you can probably work around
> the issue by increasing the allocated sk buffer size. Or you can try
> the patch that I'll submit shortly to the list.
>
> Cheers,
>
> Javier
>
>
>
>
> On Thu, Dec 22, 2011 at 7:54 AM, Simon Morgenthaler
>
> <[email protected]> wrote:
> > Hi
> >
> > I guess, I'm having exactly the same issue, but using an Atheros AR2315
> > SoC and the ath5k driver and an older compat-wireless packet (2011-07-24)
> > with a 2.6.37.6 kernel.
> >
> > I have the same setup, hostapd running on wlan0 and a mesh network
> > (80211s) on mesh0. Both interfaces are the same phy0 and are bridged with
> > a br0 interface.
> >
> > Sometimes the setup seems to work, but often the whole node crashes (most
> > likely the kernel) after a few minutes and reboots.
> >
> > Any idea?
> >
> > Thanks!
> >
> > Simon
> >
> > On Thursday 22 December 2011 16:39:25 Kai Scharwies wrote:
> >> Hello.
> >>
> >> I was trying to create a meshnode which is also a hotspot using the
> >> following steps:
> >> 1. Create virtual interfaces
> >> iw dev wlan0 del
> >> iw phy phy0 interface add mesh0 type mp
> >> iw phy phy0 interface add ap0 type mp (hostapd will change the type to
> >> AP) 2. Set ip-adresses, enable routing, etc.
> >> 3. Start hostapd for interface ap0 (channel 13 HT40-) - Clients can
> >> connect fine 4. On interface mesh0 start authsae or issue unencrypted
> >> mesh (on same channel of course) join via iw on both meshnode and
> >> (mesh)gateway (same result)
> >> Station dump shows states to switch between OPEN_SNT, HOLDING, LISTEN,
> >> but never ESTAB.
> >>
> >> As soon as hostapd is killed and step 4 is repeated the mesh is working
> >> fine. Issuing step 3 after step 4 seems to work but eventually the mesh
> >> de-establishes or even the kernel crashes:
> >>
> >> [ 5762.749369] ath: Failed to stop TX DMA, queues=0x10f!
> >> [ 5762.754738] skb_over_panic: text:d0cc78f3 len:43 put:17
> >> head:cfdcb400 data:cfdcb42e tail:0xcfdcb459 end:0xcfdcb450 dev:<NULL>
> >> [ 5762.766246] ------------[ cut here ]------------
> >> [ 5762.769483] kernel BUG at net/core/skbuff.c:127!
> >> [ 5762.769483] invalid opcode: 0000 [#1]
> >> [ 5762.769483] last sysfs file: /sys/devices/virtual/net/lo/operstate
> >> [ 5762.769483] Modules linked in: iptable_filter aes_i586 aes_generic
> >> ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack
> >> nf_defrag_ipv4 ip_tables x_tables ipv6 arc4 ath9k mac80211 cfg80211
> >> ath9k_common ath9k_hw ath rtc_cmos ftdi_sio rtc_core compat usbserial
> >> rtc_lib evdev led_class ext4 jbd2 crc16 ohci_hcd r6040 ehci_hcd mii
> >> usbcore [last unloaded: scsi_wait_scan]
> >> [ 5762.769483]
> >> [ 5762.769483] Pid: 1092, comm: phy0 Not tainted 2.6.34.10 #1 /
> >> [ 5762.769483] EIP: 0060:[<c11f7792>] EFLAGS: 00000292 CPU: 0
> >> [ 5762.769483] EIP is at skb_over_panic+0x32/0x40
> >> [ 5762.769483] EAX: 00000087 EBX: d0cc78f3 ECX: cfd01d8c EDX: c130d274
> >> [ 5762.769483] ESI: 0000005e EDI: cff092e0 EBP: 0000003f ESP: cfd01d88
> >> [ 5762.769483] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
> >> [ 5762.769483] Process phy0 (pid: 1092, ti=cfd00000 task=cf30c760
> >> task.ti=cfd00000)
> >> [ 5762.769483] Stack:
> >> [ 5762.769483] c130d274 d0cc78f3 0000002b 00000011 cfdcb400 cfdcb42e
> >> cfdcb459 cfdcb450
> >> [ 5762.769483] <0> c130b44e cfdcb448 c11f94c3 cf11f420 d0cc78f3
> >> cf740a60 1fdf4140 cf1c5d80
> >> [ 5762.769483] <0> 00000018 cff9c120 cf498000 00000001 cf11f420
> >> d0cc528e 0000003f d0cdce08
> >> [ 5762.769483] Call Trace:
> >> [ 5762.769483] [<d0cc78f3>] ? mesh_path_error_tx+0x123/0x210 [mac80211]
> >> [ 5762.769483] [<c11f94c3>] ? skb_put+0x33/0x40
> >> [ 5762.769483] [<d0cc78f3>] ? mesh_path_error_tx+0x123/0x210 [mac80211]
> >> [ 5762.769483] [<d0cc528e>] ? mesh_plink_broken+0x7e/0xb0 [mac80211]
> >> [ 5762.769483] [<d0c9a29f>] ? ieee80211_tx_status+0x9cf/0xc10
> >> [mac80211] [ 5762.769483] [<c10a5a57>] ? kmem_cache_free+0x57/0x80
> >> [ 5762.769483] [<d0d42555>] ? ath_tx_complete_buf+0xd5/0x130 [ath9k]
> >> [ 5762.769483] [<d0d44281>] ? ath_drain_txq_list+0xe1/0x140 [ath9k]
> >> [ 5762.769483] [<d0d44328>] ? ath_draintxq+0x48/0x180 [ath9k]
> >> [ 5762.769483] [<d0d45c3e>] ? ath_drain_all_txq+0xfe/0x140 [ath9k]
> >> [ 5762.769483] [<d0d3bf46>] ? ath_prepare_reset+0x46/0xb0 [ath9k]
> >> [ 5762.769483] [<d0d3d78f>] ? ath_reset_internal+0x5f/0x1a0 [ath9k]
> >> [ 5762.769483] [<d0d3db30>] ? ath_reset_work+0x0/0x10 [ath9k]
> >> [ 5762.769483] [<d0d3d8ee>] ? ath_reset+0x1e/0x80 [ath9k]
> >> [ 5762.769483] [<d0d3db30>] ? ath_reset_work+0x0/0x10 [ath9k]
> >> [ 5762.769483] [<c1034f1f>] ? worker_thread+0x10f/0x200
> >> [ 5762.769483] [<c1038240>] ? autoremove_wake_function+0x0/0x30
> >> [ 5762.769483] [<c1034e10>] ? worker_thread+0x0/0x200
> >> [ 5762.769483] [<c1037eb4>] ? kthread+0x64/0x70
> >> [ 5762.769483] [<c1037e50>] ? kthread+0x0/0x70
> >> [ 5762.769483] [<c1002e36>] ? kernel_thread_helper+0x6/0x10
> >> [ 5762.769483] Code: c9 74 2f 51 ff b0 a0 00 00 00 ff b0 9c 00 00 00
> >> ff b0 a8 00 00 00 ff b0 a4 00 00 00 52 ff 70 50 53 68 74 d2 30 c1 e8
> >> 32 2e 08 00 <0f> 0b 83 c4 24 eb fe b9 4e b4 30 c1 eb ca 55 57 56 53 83
> >> ec 04
> >> [ 5762.769483] EIP: [<c11f7792>] skb_over_panic+0x32/0x40 SS:ESP
> >> 0068:cfd01d88 [ 5763.039324] ---[ end trace b99b70cd3652a432 ]---
> >> [ 5763.044013] Kernel panic - not syncing: Fatal exception in interrupt
> >> [ 5763.050450] Pid: 1092, comm: phy0 Tainted: G D 2.6.34.10 #1
> >> [ 5763.056788] Call Trace:
> >> [ 5763.059314] [<c127a56a>] ? panic+0x37/0x91
> >> [ 5763.063577] [<c1005027>] ? oops_end+0x77/0x80
> >> [ 5763.068099] [<c1003636>] ? do_invalid_op+0x66/0x80
> >> [ 5763.073058] [<c11f7792>] ? skb_over_panic+0x32/0x40
> >> [ 5763.078104] [<c1002e29>] ? common_interrupt+0x29/0x30
> >> [ 5763.083333] [<c1022807>] ? vprintk+0x107/0x340
> >> [ 5763.088042] [<d0cc78f3>] ? mesh_path_error_tx+0x123/0x210 [mac80211]
> >> [ 5763.094591] [<c127c20e>] ? error_code+0x5e/0x70
> >> [ 5763.099385] [<d0cc78f3>] ? mesh_path_error_tx+0x123/0x210 [mac80211]
> >> [ 5763.106017] [<d0cc007b>] ? sta_ht_capa_read+0x2bb/0x5d0 [mac80211]
> >> [ 5763.112385] [<c10035d0>] ? do_invalid_op+0x0/0x80
> >> [ 5763.117256] [<c11f7792>] ? skb_over_panic+0x32/0x40
> >> [ 5763.122399] [<d0cc78f3>] ? mesh_path_error_tx+0x123/0x210 [mac80211]
> >> [ 5763.128941] [<c11f94c3>] ? skb_put+0x33/0x40
> >> [ 5763.133471] [<d0cc78f3>] ? mesh_path_error_tx+0x123/0x210 [mac80211]
> >> [ 5763.140107] [<d0cc528e>] ? mesh_plink_broken+0x7e/0xb0 [mac80211]
> >> [ 5763.146467] [<d0c9a29f>] ? ieee80211_tx_status+0x9cf/0xc10
> >> [mac80211] [ 5763.153096] [<c10a5a57>] ? kmem_cache_free+0x57/0x80
> >> [ 5763.158246] [<d0d42555>] ? ath_tx_complete_buf+0xd5/0x130 [ath9k]
> >> [ 5763.164524] [<d0d44281>] ? ath_drain_txq_list+0xe1/0x140 [ath9k]
> >> [ 5763.170721] [<d0d44328>] ? ath_draintxq+0x48/0x180 [ath9k]
> >> [ 5763.176392] [<d0d45c3e>] ? ath_drain_all_txq+0xfe/0x140 [ath9k]
> >> [ 5763.182495] [<d0d3bf46>] ? ath_prepare_reset+0x46/0xb0 [ath9k]
> >> [ 5763.188510] [<d0d3d78f>] ? ath_reset_internal+0x5f/0x1a0 [ath9k]
> >> [ 5763.194700] [<d0d3db30>] ? ath_reset_work+0x0/0x10 [ath9k]
> >> [ 5763.200365] [<d0d3d8ee>] ? ath_reset+0x1e/0x80 [ath9k]
> >> [ 5763.205683] [<d0d3db30>] ? ath_reset_work+0x0/0x10 [ath9k]
> >> [ 5763.211345] [<c1034f1f>] ? worker_thread+0x10f/0x200
> >> [ 5763.216480] [<c1038240>] ? autoremove_wake_function+0x0/0x30
> >> [ 5763.222310] [<c1034e10>] ? worker_thread+0x0/0x200
> >> [ 5763.227267] [<c1037eb4>] ? kthread+0x64/0x70
> >> [ 5763.231704] [<c1037e50>] ? kthread+0x0/0x70
> >> [ 5763.236051] [<c1002e36>] ? kernel_thread_helper+0x6/0x10
> >>
> >>
> >> I am using Atheros 92xx cards and a compat-wireless built from the
> >> o80211s git tree a couple of days ago.
> >>
> >> Usually this setup should be doable, right?
> >> I would be glad to help resolving the issues causing this.
> >>
> >> Is there another mailinglist which should be set on CC? (Maybe
> >> ath9k-devel, wireless-dev, hostap)
> >>
> >> Best regards,
> >> Kai
> >> _______________________________________________
> >> Devel mailing list
> >> [email protected]
> >> http://open80211s.com/mailman/listinfo/devel
> >
> > _______________________________________________
> > Devel mailing list
> > [email protected]
> > http://open80211s.com/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
[email protected]
http://open80211s.com/mailman/listinfo/devel
