Asus RT-AC87R

[DualBurritos]

Hello everyone. I hate to be one of those people that joins a forum just to ask a question. But sadly, my boss is on my case and I need to solve this issue.

Could someone please help me identify if this is a router issue or an ISP issue?

Here are the logs.

Oct 9 14:23:43 WAN Connection: Ethernet link down.
Oct 9 14:23:43 stop_nat_rules: apply the redirect_rules!
Oct 9 14:23:52 WAN Connection: Ethernet link up.
Oct 9 14:23:52 rc_service: wanduck 532:notify_rc restart_wan_if 0
Oct 9 14:23:54 miniupnpd[711]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 9 14:23:54 miniupnpd[711]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 9 14:23:54 miniupnpd[711]: Failed to get ip address for interface vlan2
Oct 9 14:23:57 WAN Connection: ISP's DHCP did not function properly.
Oct 9 14:24:10 miniupnpd[711]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 9 14:24:10 miniupnpd[711]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 9 14:24:10 miniupnpd[711]: Failed to get ip address for interface vlan2
Oct 9 14:24:24 miniupnpd[711]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Oct 9 14:24:25 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan2_vlan2)!
Oct 9 14:24:26 rc_service: udhcpc 847:notify_rc stop_upnp
Oct 9 14:24:26 rc_service: udhcpc 847:notify_rc start_upnp
Oct 9 14:24:26 rc_service: waitting "stop_upnp" via udhcpc ...
Oct 9 14:24:26 miniupnpd[711]: received signal 15, good-bye
Oct 9 14:24:27 miniupnpd[894]: HTTP listening on port 54903
Oct 9 14:24:27 miniupnpd[894]: Listening for NAT-PMP traffic on port 5351
Oct 9 14:24:27 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 20 seconds.
Oct 9 14:24:28 WAN Connection: WAN was restored.
Oct 9 14:24:48 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan2_vlan2)!
Oct 9 14:24:48 WAN Connection: ISP's DHCP did not function properly.
Oct 9 14:24:48 stop_nat_rules: apply the redirect_rules!
Oct 9 14:24:48 rc_service: udhcpc 907:notify_rc stop_upnp
Oct 9 14:24:48 rc_service: udhcpc 907:notify_rc start_upnp
Oct 9 14:24:48 rc_service: waitting "stop_upnp" via udhcpc ...
Oct 9 14:24:48 miniupnpd[894]: received signal 15, good-bye
Oct 9 14:24:49 rc_service: udhcpc 907:notify_rc stop_ntpc
Oct 9 14:24:49 rc_service: udhcpc 907:notify_rc start_ntpc
Oct 9 14:24:49 rc_service: waitting "stop_ntpc" via udhcpc ...
Oct 9 14:24:50 miniupnpd[957]: HTTP listening on port 45375
Oct 9 14:24:50 miniupnpd[957]: Listening for NAT-PMP traffic on port 5351
Oct 9 14:24:51 dhcp client: bound 68.40.7.141 via 68.40.0.1 during 342057 seconds.
Oct 9 14:24:52 WAN Connection: WAN was restored.
Oct 9 14:24:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan2_vlan2)!

Oct 10 09:44:12 WAN Connection: Ethernet link down.
Oct 10 09:44:13 stop_nat_rules: apply the redirect_rules!
Oct 10 09:44:22 WAN Connection: Ethernet link up.
Oct 10 09:44:22 rc_service: wanduck 532:notify_rc restart_wan_if 0
Oct 10 09:44:27 WAN Connection: ISP's DHCP did not function properly.
Oct 10 09:44:31 start_nat_rules: apply the nat_rules(/tmp/nat_rules_vlan2_vlan2)!
Oct 10 09:44:32 rc_service: udhcpc 3035:notify_rc stop_upnp
Oct 10 09:44:32 rc_service: udhcpc 3035:notify_rc start_upnp
Oct 10 09:44:32 rc_service: waitting "stop_upnp" via udhcpc ...
Oct 10 09:44:32 miniupnpd[3009]: received signal 15, good-bye
Oct 10 09:44:34 miniupnpd[3083]: HTTP listening on port 51661
Oct 10 09:44:34 miniupnpd[3083]: Listening for NAT-PMP traffic on port 5351
Oct 10 09:44:34 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 20 seconds.
Oct 10 09:44:36 WAN Connection: WAN was restored.

I think this is a ISP issue but my boss seems to think differently.

We are using a cat5e cable and a Motorola SURFboard SB6121.

Any help is greatly appreciated.

 

[mteicher]

Hello,

Have you logged into the cable modem and looked at its logs?
You might try 192.168.100.1

 

[RMerlin]

Oct 9 14:23:43 WAN Connection: Ethernet link down.
Oct 9 14:23:43 stop_nat_rules: apply the redirect_rules!
Oct 9 14:23:52 WAN Connection: Ethernet link up.

Must be a tend this week.

In any case, this indicates that for nearly 10 seconds, your modem was physically disconnected from the router. THis usually indicates that the modem has rebooted, either due to a hardware failure, or a loss in RF signal from the ISP causing it to reboot and resync.

Very unlikely to be a router issue (unless the Ethernet port of the router is defective).

 

[DualBurritos]

Hello,

Have you logged into the cable modem and looked at its logs?
You might try 192.168.100.1

Looking at the modem logs. I'm seeing a lot of things with today's date.

Here is a paste of the logs. http://pastebin.com/18APrped

We called our ISP and they are sending out a tech to see what's going on. Apparently we have a weak signal.

 

[RMerlin]

Looking at the modem logs. I'm seeing a lot of things with today's date.

Here is a paste of the logs. http://pastebin.com/18APrped

We called our ISP and they are sending out a tech to see what's going on. Apparently we have a weak signal.

Indeed. See this line here:

Jan 01 1970 00:00:13    6-Notice        N/A     Cable Modem Reboot due to T4 timeout ;CM-MAC=a4:7a:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

That confirms what the router was seeing - the modem was rebooting due to signal issues.

 

[DualBurritos]

Indeed. See this line here:

Jan 01 1970 00:00:13    6-Notice        N/A     Cable Modem Reboot due to T4 timeout ;CM-MAC=a4:7a:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

That confirms what the router was seeing - the modem was rebooting due to signal issues.

Thank you very much for clearing all this up.

 

[mteicher]

Looking at the modem logs. I'm seeing a lot of things with today's date.

Here is a paste of the logs. http://pastebin.com/18APrped

We called our ISP and they are sending out a tech to see what's going on. Apparently we have a weak signal.

Hello,

Yup as RMerlin indicated and the modem logs show the cable modem is rebooting.