gargoyle-ispy 2015-May-20 05:57.torrent

[ispyisail]

Is it possible to downgrade from 1.7.x 2015-05-20 to 1.6.2 while preserving settings?

very unlikely

[ektus]

Is it possible to downgrade from 1.7.x 2015-05-20 to 1.6.2 while preserving settings?

very unlikely

Is there risk of bricking or just "won't work"?


Regards
Ektus.

[nworbnhoj]

Is it possible to downgrade from 1.7.x 2015-05-20 to 1.6.2 while preserving settings?

No you cannot preserve settings between 1.6 an 1.7 in either direction as there is a (probable) risk of bricking.

[ektus]

Is it possible to downgrade from 1.7.x 2015-05-20 to 1.6.2 while preserving settings?

No you cannot preserve settings between 1.6 an 1.7 in either direction as there is a (probable) risk of bricking.

Okay, so I'll do it the hard way tomorrow morning.

Regards
Ektus.
(23:20 local time, gn8 and good morning to down under

[ektus]

I've installed 1.6.2 now. Immediately after, there was no connection to the remote AP, see attached log from the SSH session. The wifi command reported an error, but succeeded nevertheless, and now the link is working. Now to wait and see if it remains stable...
No, has already dropped again while I was typing
The SSH session is very sluggish, to the point of being unusable. Web interface is working fine, though. CPU load is low (as expected), don't know what's going on here. 1.6.2 seems to be worse than 1.7.x 2015-05-20

Code: Select all

login as: root
root@192.168.0.172's password:


BusyBox v1.19.4 (2014-08-26 19:54:00 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

------------------------------------------------------------------
|            _____                             _                 |
|           |  __ \                           | |                |
|           | |  \/ __ _ _ __ __ _  ___  _   _| | ___            |
|           | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \           |
|           | |_\ \ (_| | | | (_| | (_) | |_| | |  __/           |
|            \____/\__,_|_|  \__, |\___/ \__, |_|\___|           |
|                             __/ |       __/ |                  |
|                            |___/       |___/                   |
|                                                                |
|----------------------------------------------------------------|
| Gargoyle version 1.6.2    | OpenWrt Attitude Adjustment branch |
| Gargoyle revision b70bfc1 | OpenWrt revision r42171            |
| Built August 26, 2014     | Target  ar71xx/usb                 |
------------------------------------------------------------------
root@Gargoyle:~# arp
IP address       HW type     Flags       HW address            Mask     Device
192.168.0.180    0x1         0x2         00:90:a9:xx:xx:xx     *        br-lan
192.168.0.22     0x1         0x2         64:31:50:xx:xx:xx     *        br-lan
root@Gargoyle:~# ping 192.168.0.173
PING 192.168.0.173 (192.168.0.173): 56 data bytes
^C
--- 192.168.0.173 ping statistics ---
11 packets transmitted, 0 packets received, 100% packet loss
root@Gargoyle:~# wifi
command failed: Device or resource busy (-16)
Successfully initialized wpa_supplicant
root@Gargoyle:~# ping 192.168.0.173
PING 192.168.0.173 (192.168.0.173): 56 data bytes
64 bytes from 192.168.0.173: seq=0 ttl=64 time=5.186 ms
64 bytes from 192.168.0.173: seq=1 ttl=64 time=1.471 ms
64 bytes from 192.168.0.173: seq=2 ttl=64 time=3.266 ms
^C
--- 192.168.0.173 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.471/3.307/5.186 ms
root@Gargoyle:~#

New SSH session:

Code: Select all

login as: root
root@192.168.0.172's password:


BusyBox v1.19.4 (2014-08-26 19:54:00 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

------------------------------------------------------------------
|            _____                             _                 |
|           |  __ \                           | |                |
|           | |  \/ __ _ _ __ __ _  ___  _   _| | ___            |
|           | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \           |
|           | |_\ \ (_| | | | (_| | (_) | |_| | |  __/           |
|            \____/\__,_|_|  \__, |\___/ \__, |_|\___|           |
|                             __/ |       __/ |                  |
|                            |___/       |___/                   |
|                                                                |
|----------------------------------------------------------------|
| Gargoyle version 1.6.2    | OpenWrt Attitude Adjustment branch |
| Gargoyle revision b70bfc1 | OpenWrt revision r42171            |
| Built August 26, 2014     | Target  ar71xx/usb                 |
------------------------------------------------------------------
root@Gargoyle:~# ping 192.168.0.173
PING 192.168.0.173 (192.168.0.173): 56 data bytes
^C
--- 192.168.0.173 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
root@Gargoyle:~# wifi
command failed: Device or resource busy (-16)
Successfully initialized wpa_supplicant
root@Gargoyle:~# ping 192.168.0.173
PING 192.168.0.173 (192.168.0.173): 56 data bytes
64 bytes from 192.168.0.173: seq=0 ttl=64 time=12.721 ms
64 bytes from 192.168.0.173: seq=1 ttl=64 time=1.543 ms
^C
--- 192.168.0.173 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 1.543/7.132/12.721 ms
root@Gargoyle:~# logread
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.680000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.690000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.700000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.710000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.850000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.860000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.870000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.900000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:15 Gargoyle kern.warn kernel: [  311.920000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:28 Gargoyle kern.warn kernel: [  324.770000] net_ratelimit: 7 callbacks suppressed
May 30 07:33:28 Gargoyle kern.warn kernel: [  324.780000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:28 Gargoyle kern.warn kernel: [  324.790000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:28 Gargoyle kern.warn kernel: [  324.820000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:29 Gargoyle kern.warn kernel: [  324.980000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:29 Gargoyle kern.warn kernel: [  324.990000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:37 Gargoyle kern.warn kernel: [  333.310000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:37 Gargoyle kern.warn kernel: [  333.320000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:37 Gargoyle kern.warn kernel: [  333.360000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:37 Gargoyle kern.warn kernel: [  333.500000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:37 Gargoyle kern.warn kernel: [  333.510000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:41 Gargoyle kern.warn kernel: [  337.530000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:41 Gargoyle kern.warn kernel: [  337.540000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:41 Gargoyle kern.warn kernel: [  337.550000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:41 Gargoyle kern.warn kernel: [  337.560000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:41 Gargoyle kern.warn kernel: [  337.570000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:42 Gargoyle kern.warn kernel: [  338.770000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:43 Gargoyle kern.warn kernel: [  339.830000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:44 Gargoyle kern.warn kernel: [  340.840000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:46 Gargoyle kern.warn kernel: [  342.780000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:46 Gargoyle kern.warn kernel: [  342.780000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:46 Gargoyle kern.warn kernel: [  342.820000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:46 Gargoyle kern.warn kernel: [  342.950000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:46 Gargoyle kern.warn kernel: [  342.960000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:47 Gargoyle kern.warn kernel: [  342.980000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:47 Gargoyle kern.warn kernel: [  343.000000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:49 Gargoyle kern.warn kernel: [  345.040000] net_ratelimit: 3 callbacks suppressed
May 30 07:33:49 Gargoyle kern.warn kernel: [  345.040000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:49 Gargoyle kern.warn kernel: [  345.050000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:49 Gargoyle kern.warn kernel: [  345.780000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:50 Gargoyle kern.warn kernel: [  346.100000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:56 Gargoyle kern.warn kernel: [  352.890000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:56 Gargoyle kern.warn kernel: [  352.900000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:56 Gargoyle kern.warn kernel: [  352.940000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:57 Gargoyle kern.warn kernel: [  353.080000] br-lan: received packet on wlan0 with own address as source address
May 30 07:33:57 Gargoyle kern.warn kernel: [  353.090000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:01 Gargoyle kern.warn kernel: [  357.890000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:01 Gargoyle kern.warn kernel: [  357.900000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:01 Gargoyle kern.warn kernel: [  357.930000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:02 Gargoyle kern.warn kernel: [  358.070000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:02 Gargoyle kern.warn kernel: [  358.080000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.610000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.620000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.710000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.720000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.730000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.730000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.740000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.750000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.760000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:13 Gargoyle kern.warn kernel: [  369.770000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.910000] net_ratelimit: 155 callbacks suppressed
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.920000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.930000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.940000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.940000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.950000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.960000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:18 Gargoyle kern.warn kernel: [  374.970000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:19 Gargoyle kern.warn kernel: [  374.980000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:19 Gargoyle kern.warn kernel: [  375.020000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:19 Gargoyle kern.warn kernel: [  375.030000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.000000] net_ratelimit: 163 callbacks suppressed
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.000000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.010000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.020000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.030000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.040000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.050000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.060000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.090000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:38 Gargoyle kern.warn kernel: [  394.310000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:39 Gargoyle kern.warn kernel: [  395.100000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.160000] net_ratelimit: 105 callbacks suppressed
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.170000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.180000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.180000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.190000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.200000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.210000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.210000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.220000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.230000] br-lan: received packet on wlan0 with own address as source address
May 30 07:34:43 Gargoyle kern.warn kernel: [  399.240000] br-lan: received packet on wlan0 with own address as source address
May 30 07:37:44 Gargoyle kern.warn kernel: [  580.010000] net_ratelimit: 49 callbacks suppressed
May 30 07:37:44 Gargoyle kern.warn kernel: [  580.020000] br-lan: received packet on wlan0 with own address as source address
May 30 07:45:03 Gargoyle authpriv.info dropbear[2376]: Exit (root): Exited normally
May 30 07:45:05 Gargoyle authpriv.info dropbear[3398]: Child connection from 192.168.0.22:58297
May 30 07:45:19 Gargoyle authpriv.notice dropbear[3398]: Password auth succeeded for 'root' from 192.168.0.22:58297
May 30 07:50:57 Gargoyle authpriv.info dropbear[3398]: Exit (root): Exited normally
May 30 07:51:25 Gargoyle authpriv.info dropbear[3529]: Child connection from 192.168.0.22:58380
May 30 07:51:36 Gargoyle authpriv.notice dropbear[3529]: Password auth succeeded for 'root' from 192.168.0.22:58380
May 30 07:52:12 Gargoyle kern.info kernel: [ 1448.460000] wlan0: deauthenticating from 64:70:02:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
May 30 07:52:12 Gargoyle kern.info kernel: [ 1448.490000] br-lan: port 3(wlan0) entered disabled state
May 30 07:52:12 Gargoyle kern.info kernel: [ 1448.510000] br-lan: port 3(wlan0) entered disabled state
May 30 07:52:12 Gargoyle kern.info kernel: [ 1448.530000] device wlan0 left promiscuous mode
May 30 07:52:12 Gargoyle kern.info kernel: [ 1448.530000] br-lan: port 3(wlan0) entered disabled state
May 30 07:52:13 Gargoyle kern.info kernel: [ 1449.590000] device wlan0 entered promiscuous mode
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.060000] wlan0: authenticate with 64:70:02:xx:xx:xx
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.070000] wlan0: send auth to 64:70:02:xx:xx:xx (try 1/3)
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.080000] wlan0: authenticated
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.090000] wlan0: associate with 64:70:02:xx:xx:xx (try 1/3)
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.090000] wlan0: RX AssocResp from 64:70:02:xx:xx:xx (capab=0x431 status=0 aid=1)
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.100000] wlan0: associated
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.110000] br-lan: port 3(wlan0) entered forwarding state
May 30 07:52:14 Gargoyle kern.info kernel: [ 1450.110000] br-lan: port 3(wlan0) entered forwarding state
May 30 07:52:16 Gargoyle kern.info kernel: [ 1452.110000] br-lan: port 3(wlan0) entered forwarding state
May 30 07:52:21 Gargoyle kern.warn kernel: [ 1457.030000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:21 Gargoyle kern.warn kernel: [ 1457.730000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:22 Gargoyle kern.warn kernel: [ 1458.480000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:22 Gargoyle kern.warn kernel: [ 1458.490000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:22 Gargoyle kern.warn kernel: [ 1458.510000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:23 Gargoyle kern.warn kernel: [ 1459.490000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:23 Gargoyle kern.warn kernel: [ 1459.780000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:23 Gargoyle kern.warn kernel: [ 1459.790000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:23 Gargoyle kern.warn kernel: [ 1459.800000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:43 Gargoyle kern.warn kernel: [ 1479.780000] net_ratelimit: 3 callbacks suppressed
May 30 07:52:43 Gargoyle kern.warn kernel: [ 1479.790000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:43 Gargoyle kern.warn kernel: [ 1479.970000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:44 Gargoyle kern.warn kernel: [ 1480.500000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:44 Gargoyle kern.warn kernel: [ 1480.930000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:45 Gargoyle kern.warn kernel: [ 1481.100000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:45 Gargoyle kern.warn kernel: [ 1481.340000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:45 Gargoyle kern.warn kernel: [ 1481.700000] br-lan: received packet on wlan0 with own address as source address
May 30 07:52:47 Gargoyle kern.warn kernel: [ 1483.580000] br-lan: received packet on wlan0 with own address as source address
root@Gargoyle:~#

[ispyisail]

1.6.2 is stable

I would check for wifi interference or overlap

use your android or iphone to do a wifi scan of the area.

[ektus]

1.6.2 is stable

I would check for wifi interference or overlap

use your android or iphone to do a wifi scan of the area.

This is a green field location. No foreign networks around, and my own ones are well spread. At the location of the troublesome link, no other stations are visible on channel 3. That's where the current problem resides. There are no overlapping networks, and the other router on channel 3 is not visible there. See WLAN scan from my Android tablet below. stall2 is the WR702N I'm trying to connect to.

Regards
Ektus.

WLAN_Scan_20150530.jpg (37.06 KiB) Viewed 9077 times

[ispyisail]

hardware problem?

also check cables (I seen that before)

[ektus]

1.6.2 is stable

That may well be, but from browsing the forum I see some people having similar problems when running TP-LINK devices in client mode.

e.g.:
http://www.gargoyle-router.com/phpbb/vi ... =11&t=6253
http://www.gargoyle-router.com/phpbb/vi ... =11&t=6636 (last post)
http://www.gargoyle-router.com/phpbb/vi ... =11&t=6292

to name just a few.

If there's no other solution, I might replace the WR702N with the WAP0006 and set the WR1043ND V2 to AP mode, but that's not the way I had planned it and the WAP0006 is already quite old...


Regards
Ektus.

[ektus]

hardware problem?

also check cables (I seen that before)

The TL-WR1043ND V2.1 is new (just a few days old). There are no cables involved, ping running on the 1043ND and checking the WLAN link only.

I could replace the WR702N with some other access point to see if that one is the problem, but why should it be if simply re-starting the wifi reliably revives the connection?

Perhaps I could try the ping watchdog, but would have to call a custom script to restart wifi as that is not an inbuilt option. Also, the ping watchdog seems not to be available with 1.6.2.


Regards
Ektus.