commodore DD-WRT User
Joined: 20 Jun 2010 Posts: 162
|
Posted: Thu Aug 15, 2019 6:43 Post subject: WAN is up (but only after 30 sec. or so) |
|
For the last couple of weeks, I've noticed that WAN connection isn't immediately established (i.e. after turning on the router). It takes about 30 seconds after the booting has allegedly ended. What could be the reason?
The related segment of log entries is therefore also repeated - see example below:
Code: |
2019/08/15 08:28:09,40 M <6>jan 1 00:00:45 kernel: [ 45.260000] atheros ar8216/ar8236/ar8316 ag71xx-mdio.0:00: port 5 is down
2019/08/15 08:28:09,40 M <5>jan 1 00:00:45 kernel: [ 45.270000] random: nonblocking pool is initialized
2019/08/15 08:28:11,40 M <6>jan 1 00:00:47 kernel: [ 47.270000] atheros ar8216/ar8236/ar8316 ag71xx-mdio.0:00: port 5 is up
2019/08/15 08:28:14,63 I udp 0.0.0.0 fr.a2dfp.net 68 255.255.255.255 67 id=1 len=576
2019/08/15 08:28:18,06 M : dnsmasq : daemon successfully stopped
2019/08/15 08:28:18,09 M : dnsmasq : daemon successfully started
2019/08/15 08:28:18,12 M : wland : daemon successfully stopped
2019/08/15 08:28:18,14 M : wland : daemon successfully started
2019/08/15 08:28:18,15 M : wan : wan is up. ip: X.X.X.X
2019/08/15 08:28:18,17 M : process_monitor : successfully started
2019/08/15 08:28:18,25 M ntpclient[1171]: connecting to x.x.x.x [x.x.x.x] ...
2019/08/15 08:28:18,25 M ntpclient[1171]: time set from x.x.x.x [x.x.x.x].
2019/08/15 08:28:18,25 M process_monitor[1168]: cyclic ntp update success (servers x.x.x.x)
2019/08/15 08:28:19,21 M : vpn modules : vpn modules successfully unloaded
2019/08/15 08:28:19,48 M process_monitor[1168]: restarting cron (time sync change)
2019/08/15 08:28:19,62 M : process_monitor : daemon successfully stopped
2019/08/15 08:28:19,68 M : cron : daemon successfully started
2019/08/15 08:28:19,68 M cron[1585]: (cron) startup (fork ok)
2019/08/15 08:28:19,74 M : process_monitor : successfully started
2019/08/15 08:28:19,76 M process_monitor[1587]: we need to re-update after 3600 seconds
2019/08/15 08:28:19,76 M process_monitor[1587]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
2019/08/15 08:28:20,76 I udp 0.0.0.0 fr.a2dfp.net 68 255.255.255.255 67 id=5 len=576
2019/08/15 08:28:20,79 I udp 0.0.0.0 fr.a2dfp.net 68 255.255.255.255 67 id=6 len=576
2019/08/15 08:28:30,96 M : ttraff: data collection started
2019/08/15 08:28:52,60 M : dnsmasq : daemon successfully stopped
2019/08/15 08:28:52,63 M : dnsmasq : daemon successfully started
2019/08/15 08:28:52,66 M : wland : daemon successfully stopped
2019/08/15 08:28:52,68 M : wland : daemon successfully started
2019/08/15 08:28:52,68 M : wan : wan is up. ip: X.X.X.X
2019/08/15 08:28:52,71 M : process_monitor : daemon successfully stopped
2019/08/15 08:28:52,72 M : process_monitor : successfully started
2019/08/15 08:28:52,76 M ntpclient[1698]: connecting to x.x.x.x [x.x.x.x] ...
2019/08/15 08:28:52,76 M ntpclient[1698]: time set from x.x.x.x [x.x.x.x].
2019/08/15 08:28:52,76 M process_monitor[1694]: cyclic ntp update success (servers x.x.x.x)
2019/08/15 08:28:52,76 M process_monitor[1694]: we need to re-update after 3600 seconds
2019/08/15 08:28:52,76 M process_monitor[1694]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
2019/08/15 08:28:53,26 M : vpn modules : vpn modules successfully unloaded
|
The first "wan is up" is a lie, as there is no connection yet (all IPs on the relevant UI page are 0.0.0.0 at that time). Only about 30 seconds later (the second "wan is up") the connection is actually working. |
|