gargoyle-ispy 2017-October-13 22:01.torrent
Moderator: Moderators
Re: gargoyle-ispy 2017-October-13 22:01.torrent
Thank you for the hard work.
Re: gargoyle-ispy 2017-October-13 22:01.torrent
uploading now
Re: gargoyle-ispy 2017-October-13 22:01.torrent
There was a problem with extroot (thumb drive plugged into wrong port). The router is running again, and currently downloading today's torrent.ektus wrote:Installed gargoyle_1.9.x-ar71xx-generic-archer-c5-squashfs-sysupgrade.bin 1.9.X (Built 20171012-1919 git@5e29860) on my C5v1, preserving settings (coming from the august 08, 2017 build).
It's running so far, but has problems. Plugin list remains empty, routing troubles. I'll investigate further tonight, as I'm off to work now.
I've still got routing problems. Setup: ISP (O2 Germany), ISP's router (O2 home box ADSL, branded Zyxel), WiFi, Archer C5 in gateway-mode with connection type DHCP (wireless).
Notebook connected to the Archer and alternatively directly to the O2 box.
Symptoms: Some hosts are not reachable from the Archer (either SSH commandline or attached clients), but some others can be reached and the problem vanishes if I connect the notebook directly to the modem.
Code: Select all
login as: root
root@192.168.3.1's password:
BusyBox v1.23.2 (2017-10-13 11:52:13 NZDT) built-in shell (ash)
------------------------------------------------------------------
| _____ _ |
| | __ \ | | |
| | | \/ __ _ _ __ __ _ ___ _ _| | ___ |
| | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \ |
| | |_\ \ (_| | | | (_| | (_) | |_| | | __/ |
| \____/\__,_|_| \__, |\___/ \__, |_|\___| |
| __/ | __/ | |
| |___/ |___/ |
| |
|----------------------------------------------------------------|
| Gargoyle version 1.9.X | OpenWrt Chaos Calmer branch |
| Gargoyle revision c4cb5d5 | OpenWrt commit 03d52cf |
| Built February 24, 2017 | Target ar71xx/ath10k |
------------------------------------------------------------------
root@Archer-Gargoyle:~# ping www.gargoyle-router.com
PING www.gargoyle-router.com (66.228.45.220): 56 data bytes
^C
--- www.gargoyle-router.com ping statistics ---
12 packets transmitted, 0 packets received, 100% packet loss
root@Archer-Gargoyle:~# ping www.ektus.de
PING www.ektus.de (80.77.24.242): 56 data bytes
64 bytes from 80.77.24.242: seq=0 ttl=55 time=30.851 ms
64 bytes from 80.77.24.242: seq=1 ttl=55 time=31.322 ms
64 bytes from 80.77.24.242: seq=2 ttl=55 time=31.621 ms
^C
--- www.ektus.de ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 30.851/31.264/31.621 ms
root@Archer-Gargoyle:~# traceroute www.ektus.de
traceroute to www.ektus.de (80.77.24.242), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 bundle-ether11.0003.dbrx.01.muc.de.net.telefonica.de (62.53.13.30) 28.501 ms 27.085 ms 25.314 ms
4 ae3-0.0001.corx.01.muc.de.net.telefonica.de (62.53.13.66) 34.571 ms 37.978 ms ae3-0.0002.corx.01.muc.de.net.telefonica.de (62.53.13.70) 34.777 ms
5 ae7-0.0001.corx.01.fra.de.net.telefonica.de (62.53.13.62) 32.947 ms 34.008 ms 46.016 ms
6 bundle-ether16.0002.dbrx.02.fra.de.net.telefonica.de (62.53.26.4) 32.190 ms bundle-ether15.0002.dbrx.02.fra.de.net.telefonica.de (62.53.26.0) 35.029 ms bundle-ether16.0002.dbrx.02.fra.de.net.telefonica.de (62.53.26.4) 31.675 ms
7 ae8-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.59) 33.974 ms ae7-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.57) 33.934 ms 31.588 ms
8 decix.ennit.net (80.81.192.83) 37.075 ms 31.863 ms 35.918 ms
9 decix.fra2.meerfarbig.net (80.77.16.33) 29.946 ms 33.271 ms 32.815 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * www.ektus.de (80.77.24.242) 29.050 ms
root@Archer-Gargoyle:~# traceroute www.gargoyle-router.com
traceroute to www.gargoyle-router.com (66.228.45.220), 30 hops max, 38 byte packets
1 192.168.4.2 (192.168.4.2) 2.071 ms 2.857 ms 3.104 ms
2 loopback1.91.brun.0025-03.muc.de.net.telefonica.de (62.52.200.113) 22.484 ms 22.243 ms 22.746 ms
3 bundle-ether11.0003.dbrx.01.muc.de.net.telefonica.de (62.53.13.30) 22.489 ms 23.545 ms 28.518 ms
4 ae3-0.0002.corx.01.muc.de.net.telefonica.de (62.53.13.70) 36.138 ms 35.909 ms 36.070 ms
5 ae7-0.0001.corx.02.fra.de.net.telefonica.de (62.53.13.64) 39.356 ms 36.959 ms 43.178 ms
6 ae1-0.0001.prrx.01.ams.nl.net.telefonica.de (62.53.24.173) 51.366 ms 35.234 ms 38.261 ms
7 er1.ams1.nl.above.net (80.249.208.122) 35.941 ms 36.266 ms 35.491 ms
8 ae14.cr1.ams10.nl.zip.zayo.com (64.125.21.77) 34.990 ms 36.189 ms 35.563 ms
9 ae27.cs1.ams10.nl.eth.zayo.com (64.125.27.0) 108.432 ms 106.540 ms 106.672 ms
10 ae6.cs1.lhr11.uk.eth.zayo.com (64.125.29.77) 106.944 ms 106.570 ms 128.865 ms
11 * ae5.cs1.lga5.us.eth.zayo.com (64.125.29.126) 107.098 ms *
12 ae0.cs2.lga5.us.eth.zayo.com (64.125.29.187) 107.151 ms 106.911 ms 106.301 ms
13 * * *
14 ae7.mpr2.ewr1.us.zip.zayo.com (64.125.30.207) 106.975 ms 106.387 ms 106.992 ms
15 128.177.26.242 (128.177.26.242) 115.925 ms 114.426 ms 113.720 ms
16 173.255.239.11 (173.255.239.11) 114.985 ms 116.196 ms 114.094 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
root@Archer-Gargoyle:~#
Re: gargoyle-ispy 2017-October-13 22:01.torrent
@ektus
It helps to find another gargoyle user with the same problem.
I can't reproduce the error
It helps to find another gargoyle user with the same problem.
I can't reproduce the error
Re: gargoyle-ispy 2017-October-13 22:01.torrent
@ektus
also have you given your router a failsafe reset/reflash to default?
also have you given your router a failsafe reset/reflash to default?
Re: gargoyle-ispy 2017-October-13 22:01.torrent
Not yet. The strange thing is it's working for some hosts and fails for some others. Amazon's http://ec2-reachability.amazonaws.com/ shows many failures, and sometimes it doesn't. I've had the problem for quite some time now, but not always. I suspect the ISP, perhaps the double-NAT.ispyisail wrote:@ektus
also have you given your router a failsafe reset/reflash to default?
Re: gargoyle-ispy 2017-October-13 22:01.torrent
Preserving setting on upgrade is not advised. Have you ever experienced anything like this on previous builds? Sounds like a failsafe reset/reflash is the best option here.ektus wrote:Installed gargoyle_1.9.x-ar71xx-generic-archer-c5-squashfs-sysupgrade.bin 1.9.X (Built 20171012-1919 git@5e29860) on my C5v1, preserving settings (coming from the august 08, 2017 build).
You can always make a backup before upgrading, and then manually restore the desired files through WinSCP. Saves a lot of time when setting everything up again.
That's what i do on every upgrade.
TP-Link Archer C7 v2 - Gargoyle 1.12.X
TP-Link WR842ND v2 - Gargoyle 1.10.X
TP-Link RE450 AC v2 - Stock FW 1.0.4
TP-Link WA850RE v1.2 - LEDE 17.01.1
TP-Link WR842ND v2 - Gargoyle 1.10.X
TP-Link RE450 AC v2 - Stock FW 1.0.4
TP-Link WA850RE v1.2 - LEDE 17.01.1
Re: gargoyle-ispy 2017-October-13 22:01.torrent
I haven't had update-related trouble, especially not during minor version jumps.
It's quite a hassle to re-enter evrything, expecially with this setup where I need channel 13, have extroot and transmission running. The problem has been there intermittently for quite some time now. Some days everything works as it should, some days half of the world is unreachable. I don't have any fancy rules as I'm the only user on this router. It's the basic functions that aren't working correctly sometimes, and as the traceroute shows, it looks like the connection problem is some 14 hops down the route, not directly in the router.
I did just now re-activate my spare TL-WR1043ND, running 1.9.0 built November 06, 2015. It experiences the very same problem, so I would exclude simple configuration errors or anything update-related. The client is different, too, with a windows 7 notebook on the Archer and a RPi3 running Raspian on the TL-WR1043.
Right now I can reach www.gargoyle-router.com through the Archer, but not through the TL-WR1043. Very weird. And a couple minutes later it fails again
Regards
Ektus.
It's quite a hassle to re-enter evrything, expecially with this setup where I need channel 13, have extroot and transmission running. The problem has been there intermittently for quite some time now. Some days everything works as it should, some days half of the world is unreachable. I don't have any fancy rules as I'm the only user on this router. It's the basic functions that aren't working correctly sometimes, and as the traceroute shows, it looks like the connection problem is some 14 hops down the route, not directly in the router.
I did just now re-activate my spare TL-WR1043ND, running 1.9.0 built November 06, 2015. It experiences the very same problem, so I would exclude simple configuration errors or anything update-related. The client is different, too, with a windows 7 notebook on the Archer and a RPi3 running Raspian on the TL-WR1043.
Right now I can reach www.gargoyle-router.com through the Archer, but not through the TL-WR1043. Very weird. And a couple minutes later it fails again

Regards
Ektus.