WAN Connection: ISP's DHCP did not function properly

[Sky1111]

Folks, I having WAN disconnect issue and I do not know where the problem really is - router or modem/ISP?
My cable Internet - 35/3 - was activated about a week ago; initially it was all great, but now I am getting constant WAN disconnects. Please help to understand where the problem is!

Setup:
Modem: Thompson DCM476 modem, Software Version: STAC.02.50
Software Model: a81a
Bootloader: 2.3.1
Router: ASUS RT-AC56U, tried latest Merlin firmwares (.40, .39), currently running latest posted ASUS firmware - RT-AC56U_3.0.0.4_374_4561-g5f5c8d8.trx

Full log is attached. Note the connection restoration in the log is due to the router reboot. Key error message:
"WAN Connection: ISP's DHCP did not function properly"

Yet rebooting router OR modem resolves the issue temporarily. Please help!

 

[RMerlin]

Try turning off the modem for about 10 mins to fully reset the existing lease from your ISP.

I find it odd that they renew your lease every hour (3600 secs). A lot of ISPs will assign 24-hours leaves.

 

[Sky1111]

Hi Merlin - can't believe you are not asleep at 4am - million thanks for reply...

Here is what I did before I saw your reply:

- changed DHCP query to "Normal"
- hard reset DCM476 via rest button to force the modem to rescan the channels
- rebooted the router

I want to leave it to see if that makes any difference. If not, I will unplug the modem for ~30 min

P.S. ISP - Acanac (Rogers)

 

[Diveblaster]

Folks, I having WAN disconnect issue and I do not know where the problem really is - router or modem/ISP?
My cable Internet - 35/3 - was activated about a week ago; initially it was all great, but now I am getting constant WAN disconnects. Please help to understand where the problem is!

Setup:
Modem: Thompson DCM476 modem, Software Version: STAC.02.50
Software Model: a81a
Bootloader: 2.3.1
Router: ASUS RT-AC56U, tried latest Merlin firmwares (.40, .39), currently running latest posted ASUS firmware - RT-AC56U_3.0.0.4_374_4561-g5f5c8d8.trx

Full log is attached. Note the connection restoration in the log is due to the router reboot. Key error message:
"WAN Connection: ISP's DHCP did not function properly"

Yet rebooting router OR modem resolves the issue temporarily. Please help!

Hi and first of all ty our own magic-user Merlin ^^
I experienced the same the other day. Never happend before and i've been using Merlin's software the last 12 months updated them as they have been released.

Taken from systemlog:
quote
Apr 3 08:37:41 WAN Connection: ISP's DHCP did not function properly.
Apr 3 08:38:09 WAN Connection: Ethernet link down.
Apr 3 08:38:12 WAN Connection: Ethernet link up.
Apr 3 08:38:12 rc_service: wanduck 292:notify_rc restart_wan_if 0
Apr 3 08:38:12 dnsmasq[446]: read /etc/hosts - 5 addresses
Apr 3 08:38:12 dnsmasq[446]: read /etc/hosts.dnsmasq - 2 addresses
Apr 3 08:38:12 dnsmasq-dhcp[446]: read /etc/ethers - 7 addresses
Apr 3 07:38:12 stop_wan(): perform DHCP release
Apr 3 08:38:12 kernel: Attempt to kill tasklet from interrupt
Apr 3 08:38:12 kernel: br0: port 1(vlan1) entering disabled state
Apr 3 08:38:12 kernel: br0: port 1(vlan1) entering listening state
Apr 3 08:38:12 kernel: br0: port 1(vlan1) entering learning state
Apr 3 08:38:12 kernel: br0: topology change detected, propagating
Apr 3 08:38:12 kernel: br0: port 1(vlan1) entering forwarding state
Apr 3 08:38:14 dnsmasq[446]: read /etc/hosts - 5 addresses
Apr 3 08:38:14 dnsmasq[446]: read /etc/hosts.dnsmasq - 2 addresses
Apr 3 08:38:14 dnsmasq-dhcp[446]: read /etc/ethers - 7 addresses
Apr 3 08:38:15 WAN Connection: ISP's DHCP did not function properly.
Apr 3 08:38:22 WAN Connection: Ethernet link down.
Apr 3 08:38:57 WAN Connection: Ethernet link up.
Apr 3 08:38:57 rc_service: wanduck 292:notify_rc restart_wan_if 0
End quote

I'm using firmware version 3.0.0.4.374.40_0 (Merlin)
Other facts:
Router Asus RT-AC66U
ISP is Telia
Modem Technicolor TG799TSvn v2 (In bridge mode)

 

[Sky1111]

After the changes I mentioned above, few hours later:

Apr 5 04:51:44 WAN Connection: ISP's DHCP did not function properly.
Apr 5 04:51:44 stop_nat_rules: apply the redirect_rules!
Apr 5 04:54:35 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Apr 5 04:54:36 rc_service: udhcpc 725:notify_rc stop_upnp
Apr 5 04:54:36 rc_service: udhcpc 725:notify_rc start_upnp
Apr 5 04:54:36 miniupnpd[634]: received signal 15, good-bye
Apr 5 04:54:36 rc_service: waitting "stop_upnp" via udhcpc ...
Apr 5 04:54:37 dhcp client: bound 198.91.144.154 via 198.91.144.129 during 172629 seconds.
Apr 5 04:54:37 miniupnpd[760]: HTTP listening on port 38315
Apr 5 04:54:37 miniupnpd[760]: Listening for NAT-PMP traffic on port 5351
Apr 5 04:54:39 WAN Connection: WAN was restored.

However, the connection was still up...

 

[bill1228]

Try turning off the modem for about 10 mins to fully reset the existing lease from your ISP.

I find it odd that they renew your lease every hour (3600 secs). A lot of ISPs will assign 24-hours leaves.

Merlin
You want to see a really crazy DHCP lease time take a look at AT&T Uverse.
My lease time 10 minutes, that is right, 10 minutes. That means that every 5 minutes we go through the renewal. Now that is crazy. Only time I have seen that done is when there really isn't enough leases for all clients possible.
The connection is solid though. I only use Uverse for Internet and IP phone. Use Dish for TV. Thinking of dropping Dish and just stream.
--bill

 

[RMerlin]

I experienced the same the other day. Never happend before and i've been using Merlin's software the last 12 months updated them as they have been released.

Completely different issue. The following two lines:

Apr 3 08:38:09 WAN Connection: Ethernet link down.
Apr 3 08:38:12 WAN Connection: Ethernet link up.

indicate that either your modem was rebooted, or you have a problem with the Ethernet cable between the modem and the router.

 

[Sky1111]

Hi Merlin,

I believe it was me who rebooted the modem at ~8:30am...

However, it seems like changing the setting on router did help... if the disconnects come back, I will move the router from the second floor to the basement next to the modem and will connect it with a short cable..

 

[Grump]

If you're using DMZ, port forward 67/68 UDP to your router's IP address. Sometimes DMZ can forward renew packets.

 

[Sky1111]

If you're using DMZ, port forward 67/68 UDP to your router's IP address. Sometimes DMZ can forward renew packets.

Sorry I am not clear: I do have one of the systems on my network in DMZ; do I forward port from that IP address?

 

[Diveblaster]

Completely different issue. The following two lines:

Apr 3 08:38:09 WAN Connection: Ethernet link down.
Apr 3 08:38:12 WAN Connection: Ethernet link up.

indicate that either your modem was rebooted, or you have a problem with the Ethernet cable between the modem and the router.

Ty mate ^^ sorry for disturbing. But i exp the same ..thought that was it.

 

[Sky1111]

the router was up for 1 day and 3 hrs so far, but I do see WAN connection drops and reconnects in the system log.

What does the following mean:
Apr 5 08:27:25 miniupnpd[888]: received signal 15, good-bye
Apr 5 08:27:26 dhcp client: bound 198.91.144.154 via 198.91.144.129 during 3600 seconds.
Apr 5 08:27:26 miniupnpd[957]: HTTP listening on port 48361
Apr 5 08:27:26 miniupnpd[957]: Listening for NAT-PMP traffic on port 5351
Apr 5 08:27:29 WAN Connection: WAN was restored.
Apr 5 09:27:28 WAN Connection: ISP's DHCP did not function properly.
Apr 5 09:27:28 stop_nat_rules: apply the redirect_rules!
Apr 5 09:30:15 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Apr 5 09:30:15 rc_service: udhcpc 995:notify_rc stop_upnp
Apr 5 09:30:15 miniupnpd[957]: received signal 15, good-bye
Apr 5 09:30:15 rc_service: udhcpc 995:notify_rc start_upnp
Apr 5 09:30:15 rc_service: waitting "stop_upnp" via udhcpc ...
Apr 5 09:30:16 dhcp client: bound 198.91.144.154 via 198.91.144.129 during 172631 seconds.
Apr 5 09:30:16 miniupnpd[1031]: HTTP listening on port 41078
Apr 5 09:30:16 miniupnpd[1031]: Listening for NAT-PMP traffic on port 5351
Apr 5 09:30:18 WAN Connection: WAN was restored.

 

[RMerlin]

the router was up for 1 day and 3 hrs so far, but I do see WAN connection drops and reconnects in the system log.

What does the following mean:
Apr 5 08:27:25 miniupnpd[888]: received signal 15, good-bye
Apr 5 08:27:26 dhcp client: bound 198.91.144.154 via 198.91.144.129 during 3600 seconds.
Apr 5 08:27:26 miniupnpd[957]: HTTP listening on port 48361
Apr 5 08:27:26 miniupnpd[957]: Listening for NAT-PMP traffic on port 5351
Apr 5 08:27:29 WAN Connection: WAN was restored.
Apr 5 09:27:28 WAN Connection: ISP's DHCP did not function properly.
Apr 5 09:27:28 stop_nat_rules: apply the redirect_rules!
Apr 5 09:30:15 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Apr 5 09:30:15 rc_service: udhcpc 995:notify_rc stop_upnp
Apr 5 09:30:15 miniupnpd[957]: received signal 15, good-bye
Apr 5 09:30:15 rc_service: udhcpc 995:notify_rc start_upnp
Apr 5 09:30:15 rc_service: waitting "stop_upnp" via udhcpc ...
Apr 5 09:30:16 dhcp client: bound 198.91.144.154 via 198.91.144.129 during 172631 seconds.
Apr 5 09:30:16 miniupnpd[1031]: HTTP listening on port 41078
Apr 5 09:30:16 miniupnpd[1031]: Listening for NAT-PMP traffic on port 5351
Apr 5 09:30:18 WAN Connection: WAN was restored.

It means miniupnpd was told to restart.

 

[Grump]

Sorry I am not clear: I do have one of the systems on my network in DMZ; do I forward port from that IP address?

Forward 67/68 to your routers IP.

WAN > Virtual Server

Service name: dhcp1
Port Range: 67
Local Address: 192.168.1.1 (or whatever IP your router has)
Local Port: 67
Protocol: BOTH
Add

Service name: dhcp2
Port Range: 68
Local Address: 192.168.1.1 (or whatever IP your router has)
Local Port: 68
Protocol: BOTH
Add

Apply.

 

[Sky1111]

Forward 67/68 to your routers IP.

WAN > Virtual Server

Service name: dhcp1
Port Range: 67
Local Address: 192.168.1.1 (or whatever IP your router has)
Local Port: 67
Protocol: BOTH
Add

Service name: dhcp2
Port Range: 68
Local Address: 192.168.1.1 (or whatever IP your router has)
Local Port: 68
Protocol: BOTH
Add

Apply.

Thanks for clarification - done!