Tnx for the reply, i will do a new test with this FW, but Current firmware (1.9.0 and earlier) has been reported to brick recent models of Archer C7 v2 (Early 2016 and later), should I worry about it?Lantis wrote:Thanks for the log.
I fixed this issue in the following version 1.9.X.
viewtopic.php?f=14&t=8765
You can't preserve settings to this version if you upgrade.
Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
Moderator: Moderators
-
EvertonSSJ4
- Posts: 30
- Joined: Sun Mar 30, 2014 2:39 pm
- Location: Sta Maria / Brasil
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
TP-Link TL-WR941ND
TP-Link Archer C7
TP-Link Archer C7
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
Hi mate this new fw is fine to flash to the c7. The bug was a new flash chip that was in some new c7s, it is fixt in the latest build.EvertonSSJ4 wrote:Tnx for the reply, i will do a new test with this FW, but Current firmware (1.9.0 and earlier) has been reported to brick recent models of Archer C7 v2 (Early 2016 and later), should I worry about it?Lantis wrote:Thanks for the log.
I fixed this issue in the following version 1.9.X.
viewtopic.php?f=14&t=8765
You can't preserve settings to this version if you upgrade.
Linksys WRT3200ACM
NETGEAR Nighthawk R7800
NETGEAR R6260
NETGEAR Nighthawk R7800
NETGEAR R6260
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
Its all good nowTnx for the reply, i will do a new test with this FW, but Current firmware (1.9.0 and earlier) has been reported to brick recent models of Archer C7 v2 (Early 2016 and later), should I worry about it?
-
EvertonSSJ4
- Posts: 30
- Joined: Sun Mar 30, 2014 2:39 pm
- Location: Sta Maria / Brasil
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
Thank you, everything is working perfectly until now.ispyisail wrote:Its all good now
This firmware version is stable or experimental?
Future versions will come with its correction (this will be standard from now) or should I just download the versions you release?
If you do not mind, what was the problem that caused the failure PPPoe authentication?
Follows the current log:
Code: Select all
0#53 for domain free
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.142.171. 235#53 for domain bbs
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.211.32.1 62#53 for domain bbs
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 66.244.95.2 0#53 for domain bbs
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.142.171. 235#53 for domain dyn
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.211.32.1 62#53 for domain dyn
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 66.244.95.2 0#53 for domain dyn
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.142.171. 235#53 for domain parody
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.211.32.1 62#53 for domain parody
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 66.244.95.2 0#53 for domain parody
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.142.171. 235#53 for domain glue
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 95.211.32.1 62#53 for domain glue
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 66.244.95.2 0#53 for domain glue
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 176.58.118. 172#53 for domain bit
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 106.187.47. 17#53 for domain bit
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 178.32.31.4 1#53 for domain bit
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using local addresses only f or domain lan
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 156.154.70. 1#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 156.154.71. 1#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 189.38.95.9 5#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 189.38.95.9 6#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 200.175.5.1 39#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 200.175.89. 139#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 205.210.42. 205#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 208.67.220. 220#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 208.67.222. 222#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 209.244.0.3 #53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 209.244.0.4 #53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 4.2.2.1#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 4.2.2.2#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 64.68.200.2 00#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 8.8.4.4#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 8.8.8.8#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 156.154.70. 1#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 156.154.71. 1#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 189.38.95.9 5#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 189.38.95.9 6#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 200.175.5.1 39#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 200.175.89. 139#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 205.210.42. 205#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 208.67.220. 220#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 208.67.222. 222#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 209.244.0.3 #53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 209.244.0.4 #53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 4.2.2.1#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 4.2.2.2#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 64.68.200.2 00#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 8.8.4.4#53
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: using nameserver 8.8.8.8#53
Thu Jun 23 18:22:50 2016 daemon.err dnsmasq[6449]: bad name at /etc/hosts line 1 8
Thu Jun 23 18:22:50 2016 daemon.err dnsmasq[6449]: bad name at /etc/hosts line 1 9
Thu Jun 23 18:22:50 2016 daemon.err dnsmasq[6449]: bad name at /etc/hosts line 2 3
Thu Jun 23 18:22:50 2016 daemon.err dnsmasq[6449]: bad name at /etc/hosts line 2 9
Thu Jun 23 18:22:50 2016 daemon.err dnsmasq[6449]: bad name at /etc/hosts line 3 3
Thu Jun 23 18:22:50 2016 daemon.err dnsmasq[6449]: bad name at /etc/hosts line 3 5
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: read /etc/hosts - 36 address es
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq[6449]: read /tmp/hosts/dhcp - 1 add resses
Thu Jun 23 18:22:50 2016 daemon.info dnsmasq-dhcp[6449]: read /etc/ethers - 34 a ddresses
Thu Jun 23 18:22:50 2016 daemon.warn dnsmasq-dhcp[6449]: not giving name Media-C enter.lan to the DHCP lease of 192.168.1.179 because the name exists in /etc/hos ts with address 192.168.1.200
Thu Jun 23 18:22:50 2016 daemon.warn dnsmasq-dhcp[6449]: not giving name Media-C enter to the DHCP lease of 192.168.1.179 because the name exists in /etc/hosts w ith address 192.168.1.200
Thu Jun 23 18:22:51 2016 daemon.notice miniupnpd[6059]: shutting down MiniUPnPd
Thu Jun 23 18:22:54 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:22:54 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:23:03 2016 daemon.err miniupnpd[6902]: could not open lease file: /var/upnp.leases
Thu Jun 23 18:23:03 2016 daemon.notice miniupnpd[6902]: HTTP listening on port 5 000
Thu Jun 23 18:23:03 2016 daemon.notice miniupnpd[6902]: Listening for NAT-PMP/PC P traffic on port 5351
Thu Jun 23 18:23:55 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:23:55 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:25:11 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:25:11 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:26:24 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:26:24 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:27:27 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:27:27 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: Usage: uci [<options>] <comman d> [<arguments>]
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]:
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: Commands:
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: batch
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: export [<config>]
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: import [<config>]
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: changes [<config>]
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: commit [<config>]
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: add <config> <sec tion-type>
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: add_list <config>.<sec tion>.<option>=<string>
Thu Jun 23 18:28:02 2016 daemon.err uhttpd[1629]: del_list <config>.<sec tion>.<option>=<string>
Thu Jun 23 18:28:05 2016 daemon.notice miniupnpd[6902]: shutting down MiniUPnPd
Thu Jun 23 18:28:11 2016 daemon.err uhttpd[1629]: iptables: No chain/target/matc h by that name.
Thu Jun 23 18:28:19 2016 daemon.err miniupnpd[8454]: could not open lease file: /var/upnp.leases
Thu Jun 23 18:28:19 2016 daemon.notice miniupnpd[8454]: HTTP listening on port 5 000
Thu Jun 23 18:28:19 2016 daemon.notice miniupnpd[8454]: Listening for NAT-PMP/PC P traffic on port 5351
Thu Jun 23 18:28:45 2016 kern.info kernel: [ 1125.870000] nf_conntrack: automati c helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Thu Jun 23 18:29:03 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:29:03 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:29:20 2016 daemon.notice miniupnpd[8454]: shutting down MiniUPnPd
Thu Jun 23 18:29:34 2016 daemon.err miniupnpd[9637]: could not open lease file: /var/upnp.leases
Thu Jun 23 18:29:34 2016 daemon.notice miniupnpd[9637]: HTTP listening on port 5 000
Thu Jun 23 18:29:34 2016 daemon.notice miniupnpd[9637]: Listening for NAT-PMP/PC P traffic on port 5351
Thu Jun 23 18:30:22 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:30:22 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:31:30 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:31:30 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:31:32 2016 daemon.notice miniupnpd[9637]: shutting down MiniUPnPd
Thu Jun 23 18:31:44 2016 daemon.err uhttpd[1629]: Bad argument `192.168.1.30'
Thu Jun 23 18:31:44 2016 daemon.err uhttpd[1629]: Try `iptables -h' or 'iptables --help' for more information.
Thu Jun 23 18:31:47 2016 daemon.err miniupnpd[10886]: could not open lease file: /var/upnp.leases
Thu Jun 23 18:31:47 2016 daemon.notice miniupnpd[10886]: HTTP listening on port 5000
Thu Jun 23 18:31:47 2016 daemon.notice miniupnpd[10886]: Listening for NAT-PMP/P CP traffic on port 5351
Thu Jun 23 18:32:54 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:32:54 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:33:22 2016 daemon.err uhttpd[1629]: uci: Entry not found
Thu Jun 23 18:33:22 2016 daemon.notice miniupnpd[10886]: shutting down MiniUPnPd
Thu Jun 23 18:33:34 2016 daemon.err uhttpd[1629]: Bad argument `192.168.1.30'
Thu Jun 23 18:33:34 2016 daemon.err uhttpd[1629]: Try `iptables -h' or 'iptables --help' for more information.
Thu Jun 23 18:33:37 2016 daemon.err miniupnpd[12138]: could not open lease file: /var/upnp.leases
Thu Jun 23 18:33:37 2016 daemon.notice miniupnpd[12138]: HTTP listening on port 5000
Thu Jun 23 18:33:37 2016 daemon.notice miniupnpd[12138]: Listening for NAT-PMP/P CP traffic on port 5351
Thu Jun 23 18:34:30 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:34:30 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
Thu Jun 23 18:35:26 2016 authpriv.info dropbear[12887]: Child connection from 19 2.168.1.179:54355
Thu Jun 23 18:35:35 2016 authpriv.notice dropbear[12887]: Password auth succeede d for 'root' from 192.168.1.179:54355
Thu Jun 23 18:35:41 2016 daemon.info dnsmasq-dhcp[6449]: DHCPINFORM(br-lan) 192. 168.1.179 90:2b:34:fd:d1:d7
Thu Jun 23 18:35:41 2016 daemon.info dnsmasq-dhcp[6449]: DHCPACK(br-lan) 192.168 .1.179 90:2b:34:fd:d1:d7 Media-Center
root@Gargoyle:~#
TP-Link TL-WR941ND
TP-Link Archer C7
TP-Link Archer C7
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
Experimental but many people have tested it and its one of the best versions ever maybe better and 1.6.2. (could be classed as stable)
The patch should say forever, but who knows the future?
The patch should say forever, but who knows the future?
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
I try to fix as much as possible.
The fix will be part of the next major official release of gargoyle. Until that time, ispyisail builds are the best you can get. They are the latest bug fixes.
The issue was that your modem was trying to set up an IPv6 connection, however this is unsupported in gargoyle.
I've removed the ability for it to attempt this style of connection.
The fix will be part of the next major official release of gargoyle. Until that time, ispyisail builds are the best you can get. They are the latest bug fixes.
The issue was that your modem was trying to set up an IPv6 connection, however this is unsupported in gargoyle.
I've removed the ability for it to attempt this style of connection.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
-
EvertonSSJ4
- Posts: 30
- Joined: Sun Mar 30, 2014 2:39 pm
- Location: Sta Maria / Brasil
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
I had noticed this problem when I tried to update my WR941ND to a higher version, as at the time it did not work I ended up going back to 1.6.2 and was all ok but now with the purchase that I did (Archer 1750) I was forced to ask help you and without this support and help that you have dedicated my C7 would become obsolete, unused since it without authenticating PPPoe not have usefulness in my network (my modem is bridged to prevent my ISP access your settings).
Thank you again for all the support, patience and help of all because without it would be with a new device unused since I am totally dependent on the Gargoyle firmware on my devices.
Thank you again for all the support, patience and help of all because without it would be with a new device unused since I am totally dependent on the Gargoyle firmware on my devices.
TP-Link TL-WR941ND
TP-Link Archer C7
TP-Link Archer C7
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
Not a problem 
enjoy
enjoy https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
-
EvertonSSJ4
- Posts: 30
- Joined: Sun Mar 30, 2014 2:39 pm
- Location: Sta Maria / Brasil
Re: Gargoyle (1.8.1 and 1.9.0) won't connect via PPPoE
Everything working perfectly so far without dropping or congested network:
thanks a lot
thanks a lot
TP-Link TL-WR941ND
TP-Link Archer C7
TP-Link Archer C7