As none of my tries have been successful so far and 1.6.2 didn't bring any improvement either, I've gone back up to 1.7.x from may 20th, 2015. So from now on, we're once again on topic here
Currently, the router is at a location where it can barely (well, approx 35% quality) see my test WR-702. It fails to establish a connection for longer than 2 seconds:
Code: Select all
Sat May 30 20:31:07 2015 kern.info kernel: [ 145.030000] wlan0: authenticate with 64:70:02:6f:04:13
Sat May 30 20:31:07 2015 kern.info kernel: [ 145.040000] wlan0: send auth to 64:70:02:6f:04:13 (try 1/3)
Sat May 30 20:31:07 2015 kern.info kernel: [ 145.110000] wlan0: send auth to 64:70:02:6f:04:13 (try 2/3)
Sat May 30 20:31:07 2015 kern.info kernel: [ 145.180000] wlan0: send auth to 64:70:02:6f:04:13 (try 3/3)
Sat May 30 20:31:07 2015 kern.info kernel: [ 145.260000] wlan0: authentication with 64:70:02:6f:04:13 timed out
Sat May 30 20:31:12 2015 kern.info kernel: [ 149.820000] wlan0: authenticate with 64:70:02:6f:04:13
Sat May 30 20:31:12 2015 kern.info kernel: [ 149.830000] wlan0: direct probe to 64:70:02:6f:04:13 (try 1/3)
Sat May 30 20:31:12 2015 kern.info kernel: [ 150.050000] wlan0: send auth to 64:70:02:6f:04:13 (try 2/3)
Sat May 30 20:31:12 2015 kern.info kernel: [ 150.050000] wlan0: authenticated
Sat May 30 20:31:12 2015 kern.info kernel: [ 150.070000] wlan0: associate with 64:70:02:6f:04:13 (try 1/3)
Sat May 30 20:31:12 2015 kern.info kernel: [ 150.080000] wlan0: RX AssocResp from 64:70:02:6f:04:13 (capab=0x431 status=0 aid=1)
Sat May 30 20:31:12 2015 kern.info kernel: [ 150.090000] wlan0: associated
Sat May 30 20:31:12 2015 daemon.notice netifd: Network device 'wlan0' link is up
Sat May 30 20:31:22 2015 kern.info kernel: [ 160.200000] wlan0: deauthenticating from 64:70:02:6f:04:13 by local choice (Reason: 3=DEAUTH_LEAVING)
Sat May 30 20:31:22 2015 daemon.notice netifd: Network device 'wlan0' link is down
It may be related to the fact that channel 3 is quite busy there, but nevertheles, some 30% signal quality should be plenty. 1.6.2 was behaving the same in this location, so no reason to stick with it either.
I'm going to re-install the router at it's normal location and try the ping watchdog next.
Regards
Ektus.