Hi,
it's not possible for me to establish a reliable connection via WDS/WPA-PSK between two WRT54G's, both running WhiteRussian RC4.
At the beginning, if I reboot both routers, the connection remains stable for about one day. But afterwards, there's a packet loss of about 50%, and later on, the connection is fully broken until I manually run "wifi up".
The memory utilization is increasing steadily - after an uptime of circa 3 days, I'm not able to simply re-establish the connection by issuing "wifi up", because the nas-daemon stopped running. I also can see that there are 4 /sbin/hotplug processes running when this happens.
Killing all the running hotplug processes, restarting nas with "/etc/init.d/S41wpa" and issuing "wifi up" sometimes results in the following syslog entries:
[...]
Jan 3 10:13:53 (none) user.info : #1076 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1077 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1078 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1079 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1080 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1081 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1082 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1083 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1084 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1085 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1086 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1087 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : #1088 (0x1000b830)->0x1000b830: ^I0 sec 0 usec^I0x40a6bc
Jan 3 10:13:53 (none) user.info : ...(giving up)
[...]A second "wifi up" does it:
[...]
Jan 3 10:15:55 (none) kern.info kernel: br0: port 3(wds0.49153) entering disabled state
Jan 3 10:15:55 (none) kern.info kernel: br0: port 3(wds0.49153) entering disabled state
Jan 3 10:15:55 (none) kern.info kernel: device wds0.49153 left promiscuous mode
Jan 3 10:15:55 (none) kern.info kernel: device wds0.49153 entered promiscuous mode
Jan 3 10:15:55 (none) kern.info kernel: wds0.49153: attempt to add interface with same source address.
Jan 3 10:15:55 (none) kern.info kernel: br0: port 3(wds0.49153) entering learning state
Jan 3 10:15:55 (none) kern.info kernel: br0: port 3(wds0.49153) entering forwarding state
Jan 3 10:15:55 (none) kern.info kernel: br0: topology change detected, propagating
[...]uptime:
10:36:50 up 2 days, 21:49, load average: 0.01, 0.07, 0.10free:
total used free shared buffers
Mem: 14376 14056 320 0 0
Swap: 0 0 0
Total: 14376 14056 320Any ideas? I just read in another thread (http://forum.openwrt.org/viewtopic.php?id=3793) that disabling the watchdog functionality in wificonf could solve that problem - anyone else experiencing similar problems, especially concerning memory utilization and an unreliable WDS connection?
Martin
