pppoe not connecting WRT1200AC
Moderator: Moderators
pppoe not connecting WRT1200AC
Hi,
I have searched the forum for an answer to my problem I have found many unanswered posts with questions similar to mine.
I am running gargoyle-ispy 2015-October-18 05-57 on a wrt1200AC and trying to connect by pppoe to my Vigor 120 modem. I have selected pppoe and entered my username and password then save settings. I then turn off the modem and router and wait. I turn the modem on and wait for a link then turn router on. Problem is that Gargoyle is picking up the management IP of the modem and not the external IP. If I disable dhcp on the modem then Gargoyle does not get any IP and I cannot ping external addresses. I know I am doing things right because I can connect to the internet almost immediately if I flash either the stock or DD-WRT firmwares.
The firmwares are like Goldilocks. Stock is too simple, DD-WRT is too complicated and Gargoyle is just right.
Help appreciated.
I have searched the forum for an answer to my problem I have found many unanswered posts with questions similar to mine.
I am running gargoyle-ispy 2015-October-18 05-57 on a wrt1200AC and trying to connect by pppoe to my Vigor 120 modem. I have selected pppoe and entered my username and password then save settings. I then turn off the modem and router and wait. I turn the modem on and wait for a link then turn router on. Problem is that Gargoyle is picking up the management IP of the modem and not the external IP. If I disable dhcp on the modem then Gargoyle does not get any IP and I cannot ping external addresses. I know I am doing things right because I can connect to the internet almost immediately if I flash either the stock or DD-WRT firmwares.
The firmwares are like Goldilocks. Stock is too simple, DD-WRT is too complicated and Gargoyle is just right.
Help appreciated.
Re: pppoe not connecting WRT1200AC
Does this help?
http://www.gargoyle-router.com/wiki/dok ... ario-modem
http://www.gargoyle-router.com/wiki/dok ... ario-modem
Can you help someone else get Gargoyle up and running?
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
TL-WDR3600 : Gargoyle 1.9.0 : NBN FixedWireless
TL-WR1043ND-V2 : Gargoyle 1.8.0 : 3G Huawei E160E
Re: pppoe not connecting WRT1200AC
If it picks up the management ip that means that the PPPoE hasn't established a connection.
Leaving DHCP on on the modem is recommended to allow auto setup of a static route to the modem but not necessary. Ultimately follow the guide linked in whatever way works for you and we can fix the rest.
Leaving DHCP on on the modem is recommended to allow auto setup of a static route to the modem but not necessary. Ultimately follow the guide linked in whatever way works for you and we can fix the rest.
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.
Re: pppoe not connecting WRT1200AC
Hi,
I have tried as the link nworbnhoj posted, which is what I was doing anyway.
I have atached a link to screenshots of what I see in Gargoyle and DD-WRT
As you can see DD-WRT connects correctly whilst Gargoyle does not
https://www.dropbox.com/sh/5uqwgp5dsf27 ... bVj_a?dl=0
Sorry I don't know how to put a picture into the post itself.
If I disable dhcp on the modem then Gargoyle gets the DNS servers from my ISP but not a gateway. If I enable DHCP then Gargoyle does not get anything apart from the modem management IP.
How do I get a log ?
Thanks.
I have tried as the link nworbnhoj posted, which is what I was doing anyway.
I have atached a link to screenshots of what I see in Gargoyle and DD-WRT
As you can see DD-WRT connects correctly whilst Gargoyle does not
https://www.dropbox.com/sh/5uqwgp5dsf27 ... bVj_a?dl=0
Sorry I don't know how to put a picture into the post itself.
If I disable dhcp on the modem then Gargoyle gets the DNS servers from my ISP but not a gateway. If I enable DHCP then Gargoyle does not get anything apart from the modem management IP.
How do I get a log ?
Thanks.
Re: pppoe not connecting WRT1200AC
You'll need to SSH into the gargoyle router and type "logread"
Your modem is in full bridge mode correct?
Your modem is in full bridge mode correct?
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.
Re: pppoe not connecting WRT1200AC
Hi,
Thanks for helping.
Yes the modem is in full bridged mode. Here is the log.
Hope this helps and thanks again.
Thanks for helping.
Yes the modem is in full bridged mode. Here is the log.
Code: Select all
BusyBox v1.23.2 (2015-10-18 05:48:50 NZDT) built-in shell (ash)
------------------------------------------------------------------
| _____ _ |
| | __ \ | | |
| | | \/ __ _ _ __ __ _ ___ _ _| | ___ |
| | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \ |
| | |_\ \ (_| | | | (_| | (_) | |_| | | __/ |
| \____/\__,_|_| \__, |\___/ \__, |_|\___| |
| __/ | __/ | |
| |___/ |___/ |
| |
|----------------------------------------------------------------|
| Gargoyle version 1.9.X | OpenWrt Chaos Calmer branch |
| Gargoyle revision 8d5bed3 | OpenWrt revision r47165 |
| Built October 18, 2015 | Target mvebu/default |
------------------------------------------------------------------
root@Gargoyle:~# logread
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.181123] ieee80211 phy0: Channe l: 60: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.186118] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.193219] ieee80211 phy0: Channe l: 64: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.198214] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.205303] ieee80211 phy0: Channe l: 100: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.210379] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.217467] ieee80211 phy0: Channe l: 104: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.222546] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.229624] ieee80211 phy0: Channe l: 108: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.234703] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.241785] ieee80211 phy0: Channe l: 112: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.246860] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.253941] ieee80211 phy0: Channe l: 116: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.259017] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.266098] ieee80211 phy0: Channe l: 120: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.271187] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.278271] ieee80211 phy0: Channe l: 124: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.283359] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.290438] ieee80211 phy0: Channe l: 128: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.295520] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.302616] ieee80211 phy0: Channe l: 132: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.307694] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.314783] ieee80211 phy0: Channe l: 136: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.319866] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.326967] ieee80211 phy0: Channe l: 140: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.332061] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.339146] ieee80211 phy0: Channe l: 149: 0x0 0x0 0xf
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.344244] ieee80211 phy0: 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.351340] cfg80211: Regulatory d omain changed to country: DE
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.357203] cfg80211: DFS Master region: ETSI
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.361505] cfg80211: (start_fre q - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Sat Oct 17 20:22:05 2015 user.emerg syslog: ERROR: No valid dynamic DNS service configurations defined
Sat Oct 17 20:22:05 2015 user.emerg syslog: (Did you specify correct configurati on file path?)
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.371310] cfg80211: (2400000 K Hz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.379351] cfg80211: (5150000 K Hz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.388878] cfg80211: (5250000 K Hz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.398403] cfg80211: (5470000 K Hz - 5725000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.406531] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
Sat Oct 17 20:22:05 2015 daemon.notice netifd: Bridge 'br-lan' link is down
Sat Oct 17 20:22:05 2015 daemon.notice netifd: Interface 'lan' has link connecti vity loss
Sat Oct 17 20:22:05 2015 kern.info kernel: [ 17.414982] br-lan: port 1(eth1) e ntered disabled state
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Network device 'eth0' link is up
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Interface 'wan' has link connecti vity
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Interface 'wan' is setting up now
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Interface 'wan6' has link connect ivity
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Interface 'wan6' is setting up no w
Sat Oct 17 20:22:06 2015 kern.info kernel: [ 18.380901] mvneta f1034000.ethern et eth0: link up
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Interface 'wan6' is now up
Sat Oct 17 20:22:06 2015 kern.info kernel: [ 18.410906] mvneta f1070000.ethern et eth1: link up
Sat Oct 17 20:22:06 2015 kern.info kernel: [ 18.415740] br-lan: port 1(eth1) e ntered forwarding state
Sat Oct 17 20:22:06 2015 kern.info kernel: [ 18.421192] br-lan: port 1(eth1) e ntered forwarding state
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Network device 'eth1' link is up
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Bridge 'br-lan' link is up
Sat Oct 17 20:22:06 2015 daemon.notice netifd: Interface 'lan' has link connecti vity
Sat Oct 17 20:22:06 2015 daemon.info pppd[2128]: Plugin rp-pppoe.so loaded.
Sat Oct 17 20:22:06 2015 daemon.info pppd[2128]: RP-PPPoE plugin version 3.8p co mpiled against pppd 2.4.7
Sat Oct 17 20:22:06 2015 daemon.notice pppd[2128]: pppd 2.4.7 started by root, u id 0
Sat Oct 17 20:22:06 2015 daemon.info pppd[2128]: PPP session is 6
Sat Oct 17 20:22:06 2015 daemon.warn pppd[2128]: Connected to 00:50:7f:f4:62:78 via interface eth0
Sat Oct 17 20:22:06 2015 kern.info kernel: [ 18.591878] pppoe-wan: renamed fro m ppp0
Sat Oct 17 20:22:06 2015 daemon.info pppd[2128]: Using interface pppoe-wan
Sat Oct 17 20:22:06 2015 daemon.notice pppd[2128]: Connect: pppoe-wan <--> eth0
Sat Oct 17 20:22:08 2015 kern.info kernel: [ 20.420885] br-lan: port 1(eth1) e ntered forwarding state
Sat Oct 17 20:22:09 2015 kern.debug kernel: [ 21.738322] UDP: bad checksum. Fr om 192.168.1.100:62832 to 192.168.1.1:53 ulen 39
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: started, version 2.73 caches ize 150
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: compile time options: no-IPv 6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-i pset no-auth no-DNSSEC loop-detect inotify
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: DNS service limited to local subnets
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq-dhcp[2474]: DHCP, IP range 192.168. 1.100 -- 192.168.1.249, lease time 12h
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain micro
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain micro
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain micro
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain oss
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain oss
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain oss
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain null
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain null
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain null
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain ing
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain ing
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain ing
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain indy
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain indy
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain indy
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain gopher
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain gopher
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain gopher
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain geek
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain geek
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain geek
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain fur
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain fur
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain fur
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain free
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain free
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain free
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain bbs
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain bbs
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain bbs
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain dyn
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain dyn
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain dyn
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain parody
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain parody
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain parody
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain glue
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain glue
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain glue
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 176.58.118. 172#53 for domain bit
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 106.187.47. 17#53 for domain bit
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 178.32.31.4 1#53 for domain bit
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using local addresses only f or domain lan
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: reading /tmp/resolv.conf.aut o
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain micro
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain micro
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain micro
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain oss
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain oss
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain oss
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain null
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain null
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain null
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain ing
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain ing
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain ing
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain indy
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain indy
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain indy
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain gopher
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain gopher
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain gopher
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain geek
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain geek
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain geek
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain fur
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain fur
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain fur
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain free
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain free
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain free
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain bbs
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain bbs
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain bbs
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain dyn
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain dyn
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain dyn
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain parody
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain parody
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain parody
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.142.171. 235#53 for domain glue
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 95.211.32.1 62#53 for domain glue
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 66.244.95.2 0#53 for domain glue
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 176.58.118. 172#53 for domain bit
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 106.187.47. 17#53 for domain bit
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using nameserver 178.32.31.4 1#53 for domain bit
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: using local addresses only f or domain lan
Sat Oct 17 20:22:11 2015 daemon.warn dnsmasq[2474]: ignoring nameserver 192.168. 1.1 - local interface
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: read /etc/hosts - 2 addresse s
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq[2474]: read /tmp/hosts/dhcp - 1 add resses
Sat Oct 17 20:22:11 2015 daemon.info dnsmasq-dhcp[2474]: read /etc/ethers - 0 ad dresses
Sat Oct 17 20:22:16 2015 kern.debug kernel: [ 28.425202] UDP: bad checksum. Fr om 192.168.1.100:62536 to 192.168.1.1:53 ulen 34
Sat Oct 17 20:22:17 2015 daemon.info dnsmasq-dhcp[2474]: DHCPREQUEST(br-lan) 192 .168.1.100 08:62:66:c5:d1:58
Sat Oct 17 20:22:17 2015 daemon.info dnsmasq-dhcp[2474]: DHCPACK(br-lan) 192.168 .1.100 08:62:66:c5:d1:58 Default-PC
Sat Oct 17 20:22:30 2015 user.notice root: vsftpd init: mounted = 0
Sat Oct 17 20:22:30 2015 user.emerg syslog: ERROR: No drives attached, no direct ories to share!
Sat Oct 17 20:22:30 2015 daemon.info procd: - init complete -
Sat Oct 17 20:22:36 2015 daemon.warn pppd[2128]: LCP: timeout sending Config-Req uests
Sat Oct 17 20:22:36 2015 daemon.notice pppd[2128]: Connection terminated.
Sat Oct 17 20:22:36 2015 daemon.info pppd[2128]: Sent PADT
Sat Oct 17 20:22:36 2015 daemon.notice pppd[2128]: Modem hangup
Sat Oct 17 20:22:36 2015 daemon.info pppd[2128]: Exit.
Sat Oct 17 20:22:36 2015 daemon.notice netifd: Interface 'wan' is now down
Sat Oct 17 20:22:36 2015 daemon.notice netifd: Interface 'wan' is setting up now
Sat Oct 17 20:22:36 2015 daemon.info pppd[2627]: Plugin rp-pppoe.so loaded.
Sat Oct 17 20:22:36 2015 daemon.info pppd[2627]: RP-PPPoE plugin version 3.8p co mpiled against pppd 2.4.7
Sat Oct 17 20:22:36 2015 daemon.notice pppd[2627]: pppd 2.4.7 started by root, u id 0
Sat Oct 17 20:22:36 2015 daemon.info pppd[2627]: PPP session is 6
Sat Oct 17 20:22:36 2015 daemon.warn pppd[2627]: Connected to 00:50:7f:f4:62:78 via interface eth0
Sat Oct 17 20:22:36 2015 kern.info kernel: [ 48.831883] pppoe-wan: renamed fro m ppp0
Sat Oct 17 20:22:37 2015 daemon.info pppd[2627]: Using interface pppoe-wan
Sat Oct 17 20:22:37 2015 daemon.notice pppd[2627]: Connect: pppoe-wan <--> eth0
Sat Oct 17 20:22:41 2015 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0)
Sat Oct 17 20:22:41 2015 authpriv.info dropbear[2821]: Child connection from 192 .168.1.100:59509
Sat Oct 17 20:22:50 2015 authpriv.notice dropbear[2821]: Password auth succeeded for 'root' from 192.168.1.100:59509
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.warn pppd[2128]: LCP: timeout sending Config-Req
uests
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.notice pppd[2128]: Connection terminated.
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.info pppd[2128]: Sent PADT
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.notice pppd[2128]: Modem hangup
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.info pppd[2128]: Exit.
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.notice netifd: Interface 'wan' is now down
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.notice netifd: Interface 'wan' is setting up now
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.info pppd[2627]: Plugin rp-pppoe.so loaded.
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.info pppd[2627]: RP-PPPoE plugin version 3.8p co
mpiled against pppd 2.4.7
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.notice pppd[2627]: pppd 2.4.7 started by root, u
id 0
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.info pppd[2627]: PPP session is 6
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 daemon.warn pppd[2627]: Connected to 00:50:7f:f4:62:78
via interface eth0
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:36 2015 kern.info kernel: [ 48.831883] pppoe-wan: renamed fro
m ppp0
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:37 2015 daemon.info pppd[2627]: Using interface pppoe-wan
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:37 2015 daemon.notice pppd[2627]: Connect: pppoe-wan <--> eth0
-ash: can't open --: no such file
-ash: Sat: not found
root@Gargoyle:~# Sat Oct 17 20:22:41 2015 user.notice firewall: Reloading firewall due to ifup of
wan6 (eth0)
-ash: syntax error: unexpected "("
root@Gargoyle:~#
Re: pppoe not connecting WRT1200AC
Here is a log from my successful PPPoE connection.
Code: Select all
Mon Nov 2 12:00:12 2015 daemon.info pppd[2090]: CHAP authentication succeeded
Mon Nov 2 12:00:12 2015 daemon.notice pppd[2090]: CHAP authentication succeeded
Mon Nov 2 12:00:12 2015 daemon.notice pppd[2090]: peer from calling number 00:90:1A:A3:BC:2A authorized
Mon Nov 2 12:00:12 2015 daemon.notice pppd[2090]: local IP address xxx.xxx.xxx.xxx
Mon Nov 2 12:00:12 2015 daemon.notice pppd[2090]: remote IP address xxx.xxx.xxx.xxx
Mon Nov 2 12:00:12 2015 daemon.notice pppd[2090]: primary DNS address 61.9.195.193
Mon Nov 2 12:00:12 2015 daemon.notice pppd[2090]: secondary DNS address 61.9.194.49
Mon Nov 2 12:00:12 2015 daemon.notice netifd: Network device 'pppoe-wan' link is up
Mon Nov 2 12:00:12 2015 daemon.notice netifd: Interface 'wan' is now up
Mon Nov 2 12:00:13 2015 kern.info kernel: [ 39.701651] br-lan: port 1(eth0) entered forwarding state
Mon Nov 2 12:00:13 2015 kern.info kernel: [ 40.143865] br-lan: port 2(wlan0) entered forwarding state
Mon Nov 2 12:00:13 2015 kern.info kernel: [ 40.149444] br-lan: port 2(wlan0) entered forwarding state
Mon Nov 2 12:00:13 2015 daemon.notice netifd: Network alias 'pppoe-wan' link is up
Mon Nov 2 12:00:13 2015 daemon.notice netifd: Interface 'wan_6' is enabled
Mon Nov 2 12:00:13 2015 daemon.notice netifd: Interface 'wan_6' has link connectivity
Mon Nov 2 12:00:13 2015 daemon.notice netifd: Interface 'wan_6' is setting up now
Mon Nov 2 12:00:13 2015 daemon.notice netifd: Interface 'wan_6' is now up
Mon Nov 2 12:00:14 2015 kern.info kernel: [ 41.111685] br-lan: port 3(wlan1) entered forwarding state
Mon Nov 2 12:00:15 2015 kern.info kernel: [ 42.141660] br-lan: port 2(wlan0) entered forwarding state
<-- SNIP DNSMASQ IRRELEVANT NOTIFICATIONS -->
Mon Nov 2 12:11:52 2015 user.notice firewall: Reloading firewall due to ifup of wan6 (eth1)
Mon Nov 2 12:11:54 2015 user.notice firewall: Reloading firewall due to ifup of wan (pppoe-wan)
Mon Nov 2 12:11:59 2015 kern.warn kernel: [ 85.572158] ipt_bandwidth: timezone shift of 660 minutes detected, adjusting
Mon Nov 2 12:11:59 2015 kern.warn kernel: [ 85.579236] old minutes west=0, new minutes west=-660
Mon Nov 2 12:12:04 2015 kern.info kernel: [ 90.252532] IMQ driver unloaded successfully.
Mon Nov 2 12:12:04 2015 kern.info kernel: [ 90.270004] Hooked IMQ after mangle on INPUT
Mon Nov 2 12:12:04 2015 kern.info kernel: [ 90.274486] Hooked IMQ after mangle on FORWARD
Mon Nov 2 12:12:04 2015 kern.info kernel: [ 90.279049] IMQ driver loaded successfully. (numdevs = 1, numqueues = 1, imq_dev_accurate_stats = 1)
Mon Nov 2 12:12:04 2015 kern.info kernel: [ 90.288292] Hooking IMQ before NAT on PREROUTING.
Mon Nov 2 12:12:04 2015 kern.info kernel: [ 90.293156] Hooking IMQ after NAT on POSTROUTING.
Mon Nov 2 12:12:04 2015 daemon.err insmod: module is already loaded - cls_fw
Mon Nov 2 12:12:04 2015 daemon.err insmod: module is already loaded - cls_flow
Mon Nov 2 12:12:04 2015 daemon.err insmod: module is already loaded - sch_hfsc
Mon Nov 2 12:12:04 2015 daemon.err insmod: module is already loaded - sch_sfq
Mon Nov 2 12:12:13 2015 local5.info qosmon[5562]: starting socketfd = 5, statusfd = 4
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.
Re: pppoe not connecting WRT1200AC
I have installed Gargoyle on a TP-Lonk router and had a look at the log.
CHAP authentication successful
PPP LCP Receive Configuration Reject
Disconnected
with the 1200AC I mostly get file errors no attempt at authentication.
Looks like Gargoyle does not like my ISP whilst DD-WRT, stock Linksys and stock TP-Link are OK with it.
Any ideas?
CHAP authentication successful
PPP LCP Receive Configuration Reject
Disconnected
with the 1200AC I mostly get file errors no attempt at authentication.
Looks like Gargoyle does not like my ISP whilst DD-WRT, stock Linksys and stock TP-Link are OK with it.
Any ideas?
Re: pppoe not connecting WRT1200AC
I don't really see any reason for it not too.
Have you tried reflashing a new version in case something was corrupt.
Also you used the correct version yes? Caiman
Have you tried reflashing a new version in case something was corrupt.
Also you used the correct version yes? Caiman
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.
Re: pppoe not connecting WRT1200AC
Update on problem
On the 1200ac I can connect to internet by PPPoE if I flash DD-WRT, Stock and now also openWRT. Gargoyle still gets disconnected with receive configuration reject.
I have also repeated the same flashes on my old TL-WDR3600 (TP-Link stock obviously) and can connect on every firmware except Gargoyle which disconnects with the same message.
I am still worried that the WAN IP being reported is the modem management IP and not the actual WAN IP
On the 1200ac I can connect to internet by PPPoE if I flash DD-WRT, Stock and now also openWRT. Gargoyle still gets disconnected with receive configuration reject.
I have also repeated the same flashes on my old TL-WDR3600 (TP-Link stock obviously) and can connect on every firmware except Gargoyle which disconnects with the same message.
I am still worried that the WAN IP being reported is the modem management IP and not the actual WAN IP