radios talk but IP link missing (old: WDS bridging - kernel freeze)
Project Manager
projekt.manager
Tue Mar 18 20:52:42 PST 2003
Hi all,
Following the mysterious kernel freezes I had a couple of days ago,
thanks to tips from Jermey & Aditya, they are now resolved and I was
able to get my 3 laptops (2 in a WDS bridge, 1 managed station) talking
to each other, with only one of them connected to a wired net. Looking
something like:
http://www.wapsol.de/~ashant/iwn_wds1.png
It's the green shaded part that I got to work (and would like at some
point to complete the picture), but only briefly as I am unable to
reproduce it. Points are:
1) I can see the /proc/net/hostap/xx:xx:xx:xx:xx MAC addrs of the nodes
being registered on each other, but the managed laptop and the WDS nodes
are unable to obtain DHCP addresses from the 192.168.15.254 node.
Assiging Static IP didn't help either.
2) I made sure that
prism2_param wlan0 ap_bridge_packets 0
3) I see repeated kernel log errors
kernel: br0: retransmitting tcn bpdu
kernel: wlan0: Could not find STA for this TX error
My scripts (looking quite like Jermey's) are (attached):
on 192.168.15.12 is ap-wds-node.sh
on 192.168.15.254 is ap-wds-nucleus.sh
The kernel errors seems telling, but I can't find any specific info on
them. Would anybody be able to put the pieces together.
Cheers, TIA
Aditya S Chikodi wrote:
> Hi There
>
> On a brief look through of ur script and the dump one difference that I
> found in the setup, in comparison with mine, is the 'mode'. The mode is
> always set 'managed' [never changed to 'repeater']. The rest of the
> configuration is the same.
>
> As for this message
>
> " Mar 16 03:35:21 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode "
>
> - the interface [wlan0wds0] is being added as part of the bridge rather than
> the WDS repeater interface.
>
> I haven't used the repeater mode explicitly but understand that the
> configuration requirements may differ for the same. The reason being that
> the repeater functionality will/ should be handled by the driver itself
> without interfacing with the bridge module [Driver based on the 4 address,
> includes RA and TA, should be able to decide on repeating the received Layer
> 2 frames]
>
> I haven't come across the kernel freeze problem.
>
> Hope this information helps a little
>
> Regards
> Aditya
>
> -----Original Message-----
> From: hostap-admin at shmoo.com [mailto:hostap-admin at shmoo.com]On Behalf Of
> Project Manager
> Sent: Sunday, March 16, 2003 5:35 PM
> To: hostap at shmoo.com
> Subject: WDS bridging - kernel freeze
>
>
> Hi all,
>
> Sorry about this long one, but thought I'd supply all data at once...
>
> Trying to:
> setup WDS using bridging tools following
> instructions in the README.prism2 doc and have consistently
> faced a kernel freeze problem. It just freezes.
>
> My WLAN NIC's are:
>
> Node-A. DWL-650
> Node-B. Proxim RangeLAN-DS (f/w 0.8.3)
>
> I use these small scripts to setup the WDS on each of my HostAP laptops,
> so any faults can be spotted in this.
>
> on Node-A:
>
> #!/bin/bash
>
> OTHER_END_MAC="00:60:b3:67:35:ab"
>
> iwconfig wlan0 mode repeater essid nextgen
> iwpriv wlan0 wds_add $OTHER_END_MAC
>
> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 wlan0
> brctl addif br0 wlan0wds0
>
> ifconfig eth0 0.0.0.0
> ifconfig wlan0 0.0.0.0
> ifconfig wlan0wds0 0.0.0.0
> ifconfig br0 192.168.15.254 up
>
> on Node-B:
>
> #!/bin/bash
>
> OTHER_END_MAC="00:05:5d:f3:0f:88"
>
> iwconfig wlan0 mode repeater essid nextgen
> iwpriv wlan0 wds_add $OTHER_END_MAC
>
> brctl addbr br0
> brctl addif br0 eth0
> # brctl addif br0 wlan0
> brctl addif br0 wlan0wds0
>
> ifconfig eth0 0.0.0.0
> # ifconfig wlan0 0.0.0.0
> ifconfig wlan0wds0 0.0.0.0
> ifconfig br0 192.168.15.253 up
>
>
> It seems like the sticking point is the bridging part as indicated by
> the syslog messages:
>
> on Node-A
>
> Mar 16 03:35:20 bonsai kernel: wlan0: received WDS[4 addr] frame from
> unknown TA=00:60:b3:67:35:ab
> Mar 16 03:35:21 bonsai kernel: prism2: wlan0: operating mode changed 3 -> 4
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus=2 (Disconnected)
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus: BSSID=00:05:5d:f3:0f:88
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus=1 (Connected)
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus: BSSID=00:00:00:00:00:00
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus=2 (Disconnected)
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus: BSSID=00:00:00:00:00:00
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus=1 (Connected)
> Mar 16 03:35:21 bonsai kernel: wlan0: LinkStatus: BSSID=00:00:00:00:00:00
> Mar 16 03:35:21 bonsai kernel: wlan0: registered WDS netdevice wlan0wds0
> Mar 16 03:35:21 bonsai kernel: NET4: Ethernet Bridge 008 for NET4.0
> Mar 16 03:35:21 bonsai kernel: device eth0 entered promiscuous mode
> Mar 16 03:35:21 bonsai kernel: device wlan0 entered promiscuous mode
> Mar 16 03:35:21 bonsai kernel: device wlan0wds0 entered promiscuous mode
> Mar 16 03:35:21 bonsai kernel: wlan0: prism2_open
> Mar 16 03:35:21 bonsai kernel: wlan0wds0: prism2_open
> Mar 16 03:35:21 bonsai kernel: br0: port 3(wlan0wds0) entering listening
> state
> Mar 16 03:35:21 bonsai kernel: br0: port 2(wlan0) entering listening state
> Mar 16 03:35:21 bonsai kernel: br0: port 1(eth0) entering listening state
> Mar 16 03:35:21 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:35:22 bonsai last message repeated 2 times
> Mar 16 03:35:22 bonsai kernel: br0: port 3(wlan0wds0) entering blocking
> state
> Mar 16 03:35:24 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:35:28 bonsai last message repeated 3 times
> Mar 16 03:35:29 bonsai /etc/hotplug/net.agent[1332]: No HW description
> found ... exiting
> Mar 16 03:35:29 bonsai /etc/hotplug/net.agent[1356]: No HW description
> found ... exiting
> Mar 16 03:35:30 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:35:30 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:35:31 bonsai kernel: wlan0: no IPv6 routers present
> Mar 16 03:35:32 bonsai kernel: wlan0wds0: no IPv6 routers present
> Mar 16 03:35:32 bonsai kernel: br0: no IPv6 routers present
> Mar 16 03:35:32 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:35:34 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:35:36 bonsai kernel: br0: port 2(wlan0) entering learning state
> Mar 16 03:35:36 bonsai kernel: br0: port 1(eth0) entering learning state
> Mar 16 03:35:36 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:35:50 bonsai last message repeated 7 times
> Mar 16 03:35:51 bonsai kernel: br0: port 2(wlan0) entering forwarding state
> Mar 16 03:35:51 bonsai kernel: br0: topology change detected, sending
> tcn bpdu
> Mar 16 03:35:51 bonsai kernel: br0: port 1(eth0) entering forwarding state
> Mar 16 03:35:51 bonsai kernel: br0: topology change detected
> Mar 16 03:35:51 bonsai kernel: wlan0: prism2_tx: trying to use non-WDS
> link in Repeater mode
> Mar 16 03:38:25 bonsai syslogd 1.4.1: restart.
>
> Node-A freeze occurs at this point.
>
> on Node-B
>
> Mar 16 03:39:40 linux kernel: prism2: wlan0: operating mode changed 3 -> 4
> Mar 16 03:39:40 linux kernel: wlan0: LinkStatus=2 (Disconnected)
> Mar 16 03:39:40 linux kernel: wlan0: LinkStatus: BSSID=00:60:b3:67:35:ab
> Mar 16 03:39:40 linux kernel: wlan0: LinkStatus=1 (Connected)
> Mar 16 03:39:40 linux kernel: wlan0: hfa384x_get_rid - RID len mismatch:
> rid=0xfd42, len=40 (expected 6)
> Mar 16 03:39:40 linux kernel: wlan0: could not read CURRENTBSSID after
> LinkStatus event
> Mar 16 03:39:40 linux kernel: wlan0: LinkStatus=2 (Disconnected)
> Mar 16 03:39:40 linux kernel: wlan0: LinkStatus: BSSID=00:00:00:00:00:00
> Mar 16 03:39:40 linux kernel: wlan0: LinkStatus=1 (Connected)
> Mar 16 03:39:40 linux kernel: wlan0: LinkStatus: BSSID=00:00:00:00:00:00
> Mar 16 03:39:40 linux kernel: wlan0: registered WDS netdevice wlan0wds0
> Mar 16 03:39:40 linux kernel: NET4: Ethernet Bridge 008 for NET4.0
> Mar 16 03:39:40 linux kernel: device eth0 entered promiscuous mode
> Mar 16 03:39:40 linux kernel: device wlan0wds0 entered promiscuous mode
> Mar 16 03:39:41 linux kernel: wlan0wds0: prism2_open
> Mar 16 03:39:41 linux kernel: br0: port 2(wlan0wds0) entering listening
> state
> Mar 16 03:39:41 linux kernel: br0: port 1(eth0) entering listening state
> Mar 16 03:39:48 linux /etc/hotplug/net.agent[1987]: No HW description
> found ... exiting
> Mar 16 03:39:49 linux /etc/hotplug/net.agent[2007]: No HW description
> found ... exiting
> Mar 16 03:39:51 linux kernel: br0: no IPv6 routers present
> Mar 16 03:39:51 linux kernel: wlan0wds0: no IPv6 routers present
> Mar 16 03:42:17 linux syslogd 1.4.1: restart.
>
> Node-B the freeze occurs at this point.
>
> Also noticed something strange that upon the freeze the *caps-lock and
> scroll-lock LEDs* on the laptops (Node-A, B) kept blinking endlessly.
> Wouldn't think this is a bridging or hostap problem, but it could be a
> telling symbol of smthg obvious in kernel, if someone knows what it is.
>
> One last thing - I have a Win-XP WLAN station that is supposed to obtain
> access point services from this bridged network. This XP client seems
> to be associating with the *common essid* (which is 'nextgen' in this
> case) of the bridge, but cannot obtain dynamic IP from the *dhcp server
> on Node-A*.
>
> Again, sorry for the lengthy msg. Has anyone seens this problem? or
> know from syslog what's causing the freeze?
>
> TIA
>
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ap-wds-node.sh
Type: application/x-sh
Size: 1184 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20030318/1c65680e/attachment.sh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ap-wds-nucleus.sh
Type: application/x-sh
Size: 742 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20030318/1c65680e/attachment-0001.sh
More information about the Hostap
mailing list