Hi Francesco, Thank you for reporting this weird behavior. I've only observed something similar with marginal links: is the link quality good? Another thing you might want to check is the value of the dot11MeshMaxPeerLinks. Imagine a mesh with 3 nodes, where each node is configure to only accept max 1 peer link. Since peer links are symmetric, this will leave one node constantly trying to establish a link but never succeeding.
Cheers, Javier 2009/2/27 Francesco <[email protected]>: > Kernel is 2.6.28.7 in all nodes (now grown to six). > Four are ubuntu-laptop, one is a desktop PC, other 2 are Alix and Soekris > boards. > After few tests it seems to be a driver related problems, i actually use > ath5k driver on atheros wifi cards, and these drivers are not so stable > yet.. > I found a good compromise with 20090226 release compiled on my machine. > > ifconfig now shows > >> eth0 Link encap:Ethernet HWaddr 00:1b:38:2a:62:ab >> inet addr:10.210.63.60 Bcast:10.210.63.255 Mask:255.255.255.0 >> inet6 addr: fe80::21b:38ff:fe2a:62ab/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:5667 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:2978 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:1696883 (1.6 MB) TX bytes:643598 (643.5 KB) >> Interrupt:219 Base address:0xa000 >> >> lo Link encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:10 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:996 (996.0 B) TX bytes:996 (996.0 B) >> >> mesh Link encap:Ethernet HWaddr 00:1e:4c:02:94:95 >> inet addr:192.168.3.12 Bcast:192.168.3.255 Mask:255.255.255.0 >> inet6 addr: fe80::21e:4cff:fe02:9495/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:104 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:9460 (9.4 KB) TX bytes:13400 (13.4 KB) >> >> wmaster0 Link encap:UNSPEC HWaddr >> 00-1E-4C-02-94-95-00-00-00-00-00-00-00-00-00-00 >> UP RUNNING MTU:0 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > while stations dumped are > > Station 00:0c:42:2c:d9:43 (on mesh) > inactive time: 956 ms > rx bytes: 263342 > tx bytes: 2196 > mesh llid: 45225 > mesh plid: 45098 > mesh plink: ESTAB > Station 00:0c:42:2c:d8:fc (on mesh) > inactive time: 676 ms > rx bytes: 263497 > tx bytes: 2153 > mesh llid: 15713 > mesh plid: 59515 > mesh plink: ESTAB > Station 00:0b:6b:2e:21:64 (on mesh) > inactive time: 232 ms > rx bytes: 306992 > tx bytes: 724 > mesh llid: 17029 > mesh plid: 28442 > mesh plink: ESTAB > Station 00:30:f1:a9:f1:90 (on mesh) > inactive time: 189616 ms > rx bytes: 1641289 > tx bytes: 2843 > mesh llid: 4386 > mesh plid: 21423 > mesh plink: ESTAB > Station 00:0b:6b:34:88:94 (on mesh) > inactive time: 283600 ms > rx bytes: 21224 > tx bytes: 2244 > mesh llid: 55327 > mesh plid: 19624 > mesh plink: ESTAB > > (missing one, the one from which i am writing) > > When i get problem, wifi interface, after ifconfig mesh up, starts sending > garbage at high rate trying to associate (i presume) wih the other node, but > do not succed even after 10 minutes. > > in station dump the mesh plink varies: OPEN_SNT, HOLDING, LISTEN, but never > get to ESTAB. > > As you can see now everything is working...i haven't found a regular pattern > for this weird behaviour. > > Plus, killing interface (ifconfig down) and bringing it up after short time > seems to solve the problem. > > > > > > On Mon, Feb 23, 2009 at 7:00 PM, Javier Cardona <[email protected]> wrote: >> >> Francesco, >> >> 2009/2/23 Francesco <[email protected]>: >> > Hi all, i am trying to build a testbed for some experiments with 80211s. >> > At the moment i have 2 machines running openwrt, ath5k drivers. >> > 80211s stack is up and running and i can see and ping between two nodes. >> > I assigned 192.168.3.1 and 192.168.3.2 fixed IPs. >> > I set up my laptop runnin ubuntu intrepid, ath5k and of course 80211s >> > stack >> > to add it to the mesh. >> > The node is assigned 192.168.3.3 ip fixed address. >> > When i set mesh interface up, i see trough iw mesh station dump that it >> > sees >> > only one of the other two nodes on mesh, and is not able to ping any. >> > >> > I tried to give it a 192.168.3.12 ip and now it enter the mesh network, >> > and >> > ping other nodes. >> > >> > Did anyone experienced similar problems? >> > Don't know if it is a bug, maybe i am missing something in mesh ip >> > configuration..maybe not >> >> I cannot think of any reason why you would see one node and not the >> other, assuming that alll three are in radio range. >> >> If you have not solved it yet, could you provide the kernel version >> number that you are running in all three machines? >> The output of ifconfig and iw (mpath and station dump) would also be >> useful to troubleshoot this. >> >> Cheers, >> >> Javier >> >> >> -- >> Javier Cardona >> cozybit Inc. >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://open80211s.com/mailman/listinfo/devel > > > > -- > Francesco Cappuccio > > > _______________________________________________ > Devel mailing list > [email protected] > http://open80211s.com/mailman/listinfo/devel > > -- Javier Cardona cozybit Inc. _______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
