• SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Power down and WAN isn't UP after power ON

MiCk

New Around Here
Hello,

My ISP modem has booting time longer than Asus RT-N66U.
So I have problem after power down with again connection WAN UP.

I use on WAN tab:
- WAN Connection Type: Automatic ISP
- DHCP query frequency: Aggressive mode or Normal mode (both tested)

It's some possibility to add some manual record in services-start to force WAN up or other way?
 
Usually, setting DHCP mode to Normal should work even with slow modems. If the modem isn't properly working yet, DHCP will ask again for a new lease 2 minutes later.

What are you getting in your System Log regarding WAN?
 
Records on log show WAN connection UP after 1:15 and at the first step has a local IP adres from ISP

Jan 1 01:00:34 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 30 seconds.
...
Jan 1 01:01:15 dhcp client: bound 84.10.xx.xx via 84.10.xx.yy during 3021 seconds.
...
Jan 1 01:01:15 dhcp client: bound 84.10.xx.xx via 84.10.xx.yy during 3021 seconds.

...but the status is still Disconnected on tab - Network Map in router and internet connection on local machines not exist.

After press Apply on WAN tab is get a log:

Jan 1 01:08:05 rc_service: httpd 317:notify_rc restart_wan_if 0
Jan 1 01:08:05 dnsmasq[713]: read /etc/hosts - 5 addresses
Jan 1 01:08:05 dnsmasq[713]: read /etc/hosts.dnsmasq - 9 addresses
Jan 1 01:08:05 dnsmasq-dhcp[713]: read /etc/ethers - 23 addresses
Jan 1 01:08:05 dnsmasq[713]: using nameserver 62.179.xx.xx#53
Jan 1 01:08:05 dnsmasq[713]: using nameserver 62.179.xx.xy#53
Jan 1 01:08:05 stop_wan(): perform DHCP release
Jan 1 01:08:05 kernel: br0: port 1(vlan1) entering disabled state
Jan 1 01:08:05 kernel: br0: port 1(vlan1) entering listening state
Jan 1 01:08:05 kernel: br0: port 1(vlan1) entering learning state
Jan 1 01:08:05 kernel: br0: topology change detected, propagating
Jan 1 01:08:05 kernel: br0: port 1(vlan1) entering forwarding state
Jan 1 01:08:07 dnsmasq[713]: read /etc/hosts - 5 addresses
Jan 1 01:08:07 dnsmasq[713]: read /etc/hosts.dnsmasq - 9 addresses
Jan 1 01:08:07 dnsmasq-dhcp[713]: read /etc/ethers - 23 addresses
Jan 1 01:08:07 dnsmasq[713]: read /etc/hosts - 5 addresses
Jan 1 01:08:07 dnsmasq[713]: read /etc/hosts.dnsmasq - 9 addresses
Jan 1 01:08:07 dnsmasq-dhcp[713]: read /etc/ethers - 23 addresses
Jan 1 01:08:07 dnsmasq[713]: using nameserver 62.179.xx.xx#53
Jan 1 01:08:07 dnsmasq[713]: using nameserver 62.179.xx.xy#53
Jan 1 01:08:07 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 1 01:08:07 dnsmasq[713]: exiting on receipt of SIGTERM
Jan 1 01:08:07 dnsmasq[762]: started, version 2.67 cachesize 1500
Jan 1 01:08:07 dnsmasq[762]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Jan 1 01:08:07 dnsmasq[762]: warning: interface ppp1* does not currently exist
Jan 1 01:08:07 dnsmasq[762]: asynchronous logging enabled, queue limit is 5 messages
Jan 1 01:08:07 dnsmasq-dhcp[762]: DHCP, IP range 192.168.8.2 -- 192.168.8.39, lease time 1d
Jan 1 01:08:07 dnsmasq[762]: read /etc/hosts - 5 addresses
Jan 1 01:08:07 dnsmasq[762]: read /etc/hosts.dnsmasq - 9 addresses
Jan 1 01:08:07 dnsmasq-dhcp[762]: read /etc/ethers - 23 addresses
Jan 1 01:08:07 dnsmasq[762]: using nameserver 62.179.xx.xx#53
Jan 1 01:08:07 dnsmasq[762]: using nameserver 62.179.xx.xy#53
Jan 1 01:08:07 rc_service: udhcpc 744:notify_rc stop_upnp
Jan 1 01:08:07 rc_service: udhcpc 744:notify_rc start_upnp
Jan 1 01:08:07 miniupnpd[778]: HTTP listening on port 43693
Jan 1 01:08:07 miniupnpd[778]: Listening for NAT-PMP traffic on port 5351
Jan 1 01:08:07 ddns: IP address, server and hostname have not changed since the last update.
Jan 1 01:08:10 WAN Connection: WAN was restored.

and the internet connection appear.
 
Your log shows that the LAN IP lease only has a 30 seconds duration. That means that after 30 seconds it should expire, and then your router will request a new IP, at which point it should hopefully be from your ISP. If it's still local, then the same thing will re-happen 30 seconds later.
 
Always about time 1:15 log show that router getting valid IP from ISP but the status on tab Internet map is still Disconnected and internet connection not exist.
I have to manually press the Apply on the WAN tab and then connection run rapidly.
This isn't comfortable when I lost connection with my NAS and other devices when I'm outside.
 
I don't see why that would be the case, especially if you do get a valid DHCP lease at that point.

Why not just disable the DHCP server inside your modem then? Sounds like it's configured to act as a router in addition to a modem.

You could always try to put a sleep 120 followed by a service restart_wan in services-start. A bit kludgy, but it might do the trick.

Ideally, you'd want a wan-start script that's more complex: check if the IP is a private IP, if it is then sleep 30 secs, then restart WAN.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top