Page 2 of 4
Re: No WAN ip after reboot
Posted: Fri Feb 12, 2016 2:34 am
by Lantis
By all means leave it turned on. It's just for the first X hours after being enabled it has to scan the drive.
Depending on size this can take a long time.
If I'm going to rebuild my database I tend to kick it off before going to bed.
Re: No WAN ip after reboot
Posted: Fri Mar 18, 2016 3:12 pm
by 11freddy
I have an almost identical problem- Archer C7 v2 running 1.8.1.
I replaced a 1043ND running 1.7.? with this router and it doesn't get a WAN IP / complete PPPoE login unless I reset my modem... the 1043 didn't have this issue. Unfortunately I changed both HW and SW at the same time so cannot say for certain which is the culprit...
Not sure it matters but my modem is a SmartRG 505 VDSL modem (bridged).
If I power cycle both modem / router or just modem the problem goes away.
Any thoughts?
THanks...
Re: No WAN ip after reboot
Posted: Fri Mar 18, 2016 4:05 pm
by purfikt
Yeah, I'm still having the same issue. Everything else is working great. Earlier I was experiencing high CPU load, but that turned out to be due to using the webcam feature.
The power has gone out once since I last posted and it worked out ok, because it power cycled both the router and the modem. I've also replaced my cable modem to make sure it wasn't the problem. I would like to set up scheduled reboots, but right now I can't because it will not regain WAN IP without rebooting the modem.
Archer C7 v2
Current version: 1.9.X (Built 20160211-2045 git@be6ac8c)
Re: No WAN ip after reboot
Posted: Sat Mar 19, 2016 12:15 pm
by 11freddy
Is there some investigation we should do to help understand why this is happening?
Should we post this formally as a bug?
Re: No WAN ip after reboot
Posted: Sat Mar 19, 2016 5:05 pm
by Lantis
Sounds more like an openwrt problem than gargoyle.
You're both using the exact same hardware and experiencing the same problem.
No other users report this problem. Even myself I can reboot modem or router individually without the other and the link renegotiated within 60 seconds.
I guess you could replicate the issue and then do a logread and see why the ppp daemon is upset.
This is probably important information to include in an openwrt bug report anyway.
Re: No WAN ip after reboot
Posted: Sat Mar 19, 2016 5:51 pm
by 11freddy
OK. Will try this tomorrow...
When you say this works for you, is it with the same HW also?
Does the fact my problem is with a PPPoE login and Purfikt's is acquiring a DHCP address mean anything? Assume there is different software for these two activities...
Thanks.
Re: No WAN ip after reboot
Posted: Sat Mar 19, 2016 6:03 pm
by Lantis
Different hardware.
If I had to guess, both problems are DHCP related.
Re: No WAN ip after reboot
Posted: Sun Mar 20, 2016 8:03 am
by 11freddy
Here is the logread...
Had a look over at OpenWRT, wasn't clear to me where to raise a 'bug' report? Do you just create a new thread under Barrier Breaker?
Would it receive any attention- as they are on Chaos Calmer...?
THanks.
/etc/crontabs$ logread
Sun Mar 20 07:40:34 2016 daemon.info pppd[2680]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:40:34 2016 daemon.notice pppd[2680]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:40:34 2016 kern.info kernel: [ 212.600000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:40:34 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:40:34 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:40:49 2016 daemon.warn pppd[2680]: Timeout waiting for PADO packets
Sun Mar 20 07:40:49 2016 daemon.err pppd[2680]: Unable to complete PPPoE Discovery
Sun Mar 20 07:40:49 2016 daemon.info pppd[2680]: Exit.
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:40:49 2016 kern.info kernel: [ 227.050000] eth0: link down
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:40:49 2016 daemon.notice netifd: wan (2688): sh: 3 5: bad number
Sun Mar 20 07:40:49 2016 daemon.info pppd[2697]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:40:49 2016 daemon.info pppd[2697]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:40:49 2016 daemon.notice pppd[2697]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:40:49 2016 kern.info kernel: [ 227.610000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:40:49 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:41:04 2016 daemon.warn pppd[2697]: Timeout waiting for PADO packets
Sun Mar 20 07:41:04 2016 daemon.err pppd[2697]: Unable to complete PPPoE Discovery
Sun Mar 20 07:41:04 2016 daemon.info pppd[2697]: Exit.
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:41:04 2016 kern.info kernel: [ 242.210000] eth0: link down
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:41:04 2016 daemon.notice netifd: wan (2707): sh: 3 5: bad number
Sun Mar 20 07:41:04 2016 daemon.info dnsmasq-dhcp[2286]: DHCPINFORM(br-lan) 172.16.16.148 38:63:bb:c7:a2:22
Sun Mar 20 07:41:04 2016 daemon.info dnsmasq-dhcp[2286]: DHCPACK(br-lan) 172.16.16.148 38:63:bb:c7:a2:22 ONW-EJACOBSO-02
Sun Mar 20 07:41:04 2016 daemon.info pppd[2716]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:41:04 2016 daemon.info pppd[2716]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:41:04 2016 daemon.notice pppd[2716]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:41:04 2016 kern.info kernel: [ 242.650000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:41:04 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:41:19 2016 daemon.warn pppd[2716]: Timeout waiting for PADO packets
Sun Mar 20 07:41:19 2016 daemon.err pppd[2716]: Unable to complete PPPoE Discovery
Sun Mar 20 07:41:19 2016 daemon.info pppd[2716]: Exit.
Sun Mar 20 07:41:19 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:41:19 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:41:19 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:41:19 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:41:19 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:41:19 2016 kern.info kernel: [ 257.390000] eth0: link down
Sun Mar 20 07:41:19 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:41:19 2016 daemon.notice netifd: wan (2724): sh: 3 5: bad number
Sun Mar 20 07:41:19 2016 daemon.info pppd[2733]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:41:19 2016 daemon.info pppd[2733]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:41:19 2016 daemon.notice pppd[2733]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:41:20 2016 kern.info kernel: [ 258.350000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:41:20 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:41:20 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:41:34 2016 daemon.warn pppd[2733]: Timeout waiting for PADO packets
Sun Mar 20 07:41:34 2016 daemon.err pppd[2733]: Unable to complete PPPoE Discovery
Sun Mar 20 07:41:34 2016 daemon.info pppd[2733]: Exit.
Sun Mar 20 07:41:34 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:41:34 2016 kern.info kernel: [ 272.550000] eth0: link down
Sun Mar 20 07:41:34 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:41:34 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:41:34 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:41:34 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:41:34 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:41:34 2016 daemon.notice netifd: wan (2741): sh: 3 5: bad number
Sun Mar 20 07:41:34 2016 daemon.info pppd[2750]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:41:34 2016 daemon.info pppd[2750]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:41:34 2016 daemon.notice pppd[2750]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:41:35 2016 kern.info kernel: [ 273.360000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:41:35 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:41:35 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:41:49 2016 daemon.warn pppd[2750]: Timeout waiting for PADO packets
Sun Mar 20 07:41:49 2016 daemon.err pppd[2750]: Unable to complete PPPoE Discovery
Sun Mar 20 07:41:49 2016 daemon.info pppd[2750]: Exit.
Sun Mar 20 07:41:49 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:41:49 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:41:49 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:41:49 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:41:49 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:41:49 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:41:49 2016 kern.info kernel: [ 287.730000] eth0: link down
Sun Mar 20 07:41:50 2016 daemon.notice netifd: wan (2758): sh: 3 5: bad number
Sun Mar 20 07:41:50 2016 daemon.info pppd[2767]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:41:50 2016 daemon.info pppd[2767]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:41:50 2016 daemon.notice pppd[2767]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:41:50 2016 kern.info kernel: [ 288.370000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:41:50 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:41:50 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:42:05 2016 daemon.warn pppd[2767]: Timeout waiting for PADO packets
Sun Mar 20 07:42:05 2016 daemon.err pppd[2767]: Unable to complete PPPoE Discovery
Sun Mar 20 07:42:05 2016 daemon.info pppd[2767]: Exit.
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:42:05 2016 kern.info kernel: [ 302.900000] eth0: link down
Sun Mar 20 07:42:05 2016 daemon.notice netifd: wan (2775): sh: 3 5: bad number
Sun Mar 20 07:42:05 2016 daemon.info pppd[2784]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:42:05 2016 daemon.info pppd[2784]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:42:05 2016 daemon.notice pppd[2784]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:42:05 2016 kern.info kernel: [ 303.380000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:42:05 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:42:18 2016 daemon.info dnsmasq-dhcp[2286]: DHCPINFORM(br-lan) 172.16.16.148 38:63:bb:c7:a2:22
Sun Mar 20 07:42:18 2016 daemon.info dnsmasq-dhcp[2286]: DHCPACK(br-lan) 172.16.16.148 38:63:bb:c7:a2:22 ONW-EJACOBSO-02
Sun Mar 20 07:42:20 2016 daemon.warn pppd[2784]: Timeout waiting for PADO packets
Sun Mar 20 07:42:20 2016 daemon.err pppd[2784]: Unable to complete PPPoE Discovery
Sun Mar 20 07:42:20 2016 daemon.info pppd[2784]: Exit.
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:42:20 2016 kern.info kernel: [ 318.060000] eth0: link down
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:42:20 2016 daemon.notice netifd: wan (2792): sh: 3 5: bad number
Sun Mar 20 07:42:20 2016 daemon.info pppd[2801]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:42:20 2016 daemon.info pppd[2801]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:42:20 2016 daemon.notice pppd[2801]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:42:20 2016 kern.info kernel: [ 318.390000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:42:20 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:42:35 2016 daemon.warn pppd[2801]: Timeout waiting for PADO packets
Sun Mar 20 07:42:35 2016 daemon.err pppd[2801]: Unable to complete PPPoE Discovery
Sun Mar 20 07:42:35 2016 daemon.info pppd[2801]: Exit.
Sun Mar 20 07:42:35 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:42:35 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:42:35 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:42:35 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:42:35 2016 kern.info kernel: [ 333.240000] eth0: link down
Sun Mar 20 07:42:35 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:42:35 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:42:35 2016 daemon.notice netifd: wan (2810): sh: 3 5: bad number
Sun Mar 20 07:42:35 2016 daemon.info pppd[2819]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:42:35 2016 daemon.info pppd[2819]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:42:35 2016 daemon.notice pppd[2819]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:42:36 2016 kern.info kernel: [ 333.950000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:42:36 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:42:36 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:42:50 2016 daemon.warn pppd[2819]: Timeout waiting for PADO packets
Sun Mar 20 07:42:50 2016 daemon.err pppd[2819]: Unable to complete PPPoE Discovery
Sun Mar 20 07:42:50 2016 daemon.info pppd[2819]: Exit.
Sun Mar 20 07:42:50 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:42:50 2016 kern.info kernel: [ 348.400000] eth0: link down
Sun Mar 20 07:42:50 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:42:50 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:42:50 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:42:50 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:42:50 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:42:50 2016 daemon.notice netifd: wan (2827): sh: 3 5: bad number
Sun Mar 20 07:42:50 2016 daemon.info pppd[2836]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:42:50 2016 daemon.info pppd[2836]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:42:50 2016 daemon.notice pppd[2836]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:42:51 2016 kern.info kernel: [ 348.960000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:42:51 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:42:51 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:43:05 2016 daemon.warn pppd[2836]: Timeout waiting for PADO packets
Sun Mar 20 07:43:05 2016 daemon.err pppd[2836]: Unable to complete PPPoE Discovery
Sun Mar 20 07:43:05 2016 daemon.info pppd[2836]: Exit.
Sun Mar 20 07:43:05 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:43:05 2016 kern.info kernel: [ 363.560000] eth0: link down
Sun Mar 20 07:43:05 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:43:05 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:43:05 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:43:05 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:43:05 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:43:05 2016 daemon.notice netifd: wan (2844): sh: 3 5: bad number
Sun Mar 20 07:43:05 2016 daemon.info pppd[2853]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:43:05 2016 daemon.info pppd[2853]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:43:05 2016 daemon.notice pppd[2853]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:43:06 2016 kern.info kernel: [ 363.970000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:43:06 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:43:06 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:43:20 2016 daemon.warn pppd[2853]: Timeout waiting for PADO packets
Sun Mar 20 07:43:20 2016 daemon.err pppd[2853]: Unable to complete PPPoE Discovery
Sun Mar 20 07:43:20 2016 daemon.info pppd[2853]: Exit.
Sun Mar 20 07:43:20 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:43:20 2016 kern.info kernel: [ 378.730000] eth0: link down
Sun Mar 20 07:43:20 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:43:20 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:43:20 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:43:20 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:43:20 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:43:21 2016 daemon.notice netifd: wan (2861): sh: 3 5: bad number
Sun Mar 20 07:43:21 2016 daemon.info pppd[2870]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:43:21 2016 daemon.info pppd[2870]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:43:21 2016 daemon.notice pppd[2870]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:43:21 2016 kern.info kernel: [ 378.980000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:43:21 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:43:21 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:43:32 2016 authpriv.info dropbear[2873]: Child connection from 172.16.16.148:58967
Sun Mar 20 07:43:36 2016 daemon.warn pppd[2870]: Timeout waiting for PADO packets
Sun Mar 20 07:43:36 2016 daemon.err pppd[2870]: Unable to complete PPPoE Discovery
Sun Mar 20 07:43:36 2016 daemon.info pppd[2870]: Exit.
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:43:36 2016 kern.info kernel: [ 393.900000] eth0: link down
Sun Mar 20 07:43:36 2016 daemon.notice netifd: wan (2879): sh: 3 5: bad number
Sun Mar 20 07:43:36 2016 kern.info kernel: [ 393.990000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:43:36 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Sun Mar 20 07:43:36 2016 daemon.info pppd[2888]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:43:36 2016 daemon.info pppd[2888]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:43:36 2016 daemon.notice pppd[2888]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:43:41 2016 authpriv.notice dropbear[2873]: Password auth succeeded for 'root' from 172.16.16.148:58967
Sun Mar 20 07:43:48 2016 daemon.info dnsmasq-dhcp[2286]: DHCPINFORM(br-lan) 172.16.16.148 38:63:bb:c7:a2:22
Sun Mar 20 07:43:48 2016 daemon.info dnsmasq-dhcp[2286]: DHCPACK(br-lan) 172.16.16.148 38:63:bb:c7:a2:22 ONW-EJACOBSO-02
Sun Mar 20 07:43:51 2016 daemon.warn pppd[2888]: Timeout waiting for PADO packets
Sun Mar 20 07:43:51 2016 daemon.err pppd[2888]: Unable to complete PPPoE Discovery
Sun Mar 20 07:43:51 2016 daemon.info pppd[2888]: Exit.
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Network device 'eth0' link is down
Sun Mar 20 07:43:51 2016 kern.info kernel: [ 409.080000] eth0: link down
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Mar 20 07:43:51 2016 daemon.notice netifd: wan (2903): sh: 3 5: bad number
Sun Mar 20 07:43:51 2016 daemon.info pppd[2912]: Plugin rp-pppoe.so loaded.
Sun Mar 20 07:43:51 2016 daemon.info pppd[2912]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 20 07:43:51 2016 daemon.notice pppd[2912]: pppd 2.4.7 started by root, uid 0
Sun Mar 20 07:43:51 2016 kern.info kernel: [ 409.550000] eth0: link up (1000Mbps/Full duplex)
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Network device 'eth0' link is up
Sun Mar 20 07:43:51 2016 daemon.notice netifd: Interface 'wan' has link connectivity
Re: No WAN ip after reboot
Posted: Sun Mar 20, 2016 6:14 pm
by 11freddy
I did a little more scouting around the OpenWRT site and found the place to report bugs...
While there, I found this:
https://dev.openwrt.org/ticket/18680
Seems like the same issue we are having... I rebooted the router and while it was in the 'bad' state I unplugged/replugged the WAN cable- it did fix the issue as described in the ticket.
If I'm interpreting the trail correctly there is a build of Chaos Calmer that resolves the problem (r45743) although the last post seems to call that into question...
Would the Gargoyle 1.9 branch be based on that fix?
Would you consider it stable enough to run on?
THanks...
Re: No WAN ip after reboot
Posted: Sun Mar 20, 2016 9:23 pm
by Lantis
It should be based on that fix yes.
I'd consider it stable enough. It never crashes for me.