Rmerlin, please introduce a time delay setting for Wan Connection at boot

[dolftb]

Rmerlin, Thanks for everything you are doing!

See below verbage posted on the VIP.ASUS forum. Would you be able to build in a software timer delay for determining how long to wait, before connecting to cable modem, so that after home powerloss all will reboot and connect properly to WAN ?

On the Vip.asus forum:

"I have confirmed and isolated this issue on 3 separate RT-AC66R units, 1 RT-AC66U on multiple firmware versions:

Currently Running 3.0.0.4.270 and 3.0.0.4.266 beta 2 Merlin

After power outage and power restore, Cable modem and RT-AC66 reboot but there is no possible way to get the WAN connected again by Using "Quick Internet Setup". Tried switching modem and router on/off in different orders but to no avail.

I have also noticed that the router has the computer mac address sometimes filled in on its own under WAN settings => "clone MAC address" (wth ??) . I only see this after the power loss and reboot. deleting the MAC address in this box does not help restart WAN connection either.

My previous router worked just fine after a power loss coming back with WAN online.

I use internet for phone so when I loose power , and don't notice it , I wont receive phone calls until I found out by trying to get on the internet that the phone hasn't been working for who knows how long.

So after trying 3 different Rt-AC66 units and 2 different modems ( Motorola SB6120 and Sb6141) I have found that the ONLY way is after powerloss to boot cable modem 1st, then wait 120 secconds plug in the router and bam works every time!

Now I have rigged a "Timer On Delay" between the wall power outlet and the routers AC adapter to delay startup of the router for 120 secs. Works good now but not everyone can do this easily.

Rmerlin, any chance you can help all users on this in the firmware because I am convinced this is a huge problem. Asus support of course wants me to RMA all 3 routers Yeah right....hahahahaha!!!!

I think this may be the reason why many new users claim router to be DOA, when in fact its a setup problem.

Thanks

Dolf.

2x RT-AC66R and 1 RT-66ACU >
Motorola SB6120 and SB6141 Cable modem on Charter network >
"Auto IP" in WAN setup "

 

[bluepoint]

This could not be a router issue. If the router comes up ahead of the modem, it'll keep on trying to get an ip until the modem is ready. If the router is not doing( trying to get an ip) that, then RMA the unit. It's also possible the cable modem is not syncing from a power loss. Have you looked at the cable modem's stat after a power loss and see if it locks with the channels?

 

[dolftb]

Yes bluepoint the modem does lock channels after restore of power. Also I have confirmed this Issue on 3 different brand new Rt-AC66U's and two motorola cable modems, as my previous post reads.

I am now using a hardware AC power delay timer on the router that gives power to router after 2 minutes when the power at home goes back on. This works fine but many people will probably have the same duficulties I have had.

My previous linksys WRT300 with DD-wrt did not have this issue after powerloss

Go ahead if you have the RT-AC66, and kill the power to modem and router, then plug back in at the same time, if you dare! ..... you will see what I mean.

 

[RogerSC]

Putting your router and cable or DSL modem on a UPS really helps on this one in getting your network through most casual power outages. We do get brown outs and short power outages, and our network doesn't see them. A good UPS also provides great surge protection.

 

[bluepoint]

Wonder what would it be different with an N66 which I have, it's just a DHCP function of the router.

 

[dolftb]

Putting your router and cable or DSL modem on a UPS really helps on this one in getting your network through most casual power outages. We do get brown outs and short power outages, and our network doesn't see them. A good UPS also provides great surge protection.

I do have a UPS but it only runs a couple hours and then...guess what...

 

[RMerlin]

I did run into extended power outages myself, and never had any issue with my router properly reconnecting once the power came back. As mentionned, the router's DHCP client will simply keep resending DHCP queries until it actually gets a valid lease.

What is probably actually happening is that your ISP is blacklisting your MAC because it receives too many DHCP requests in a short period of time for some reason. I heard of at least one user having this problem with his ISP. The real solution would rather be to have the DHCP client wait longer between it's retries - something I plan on implementing at some point.

 

[dolftb]

Thanks, please let me know if you need help when you decide to change DHCP retry timing. I will happily be your Guinea Pig, to see if this helps the issue. In the meantime my $5 Ac delay timer on the router works great at a setting of 2 minutes when the power comes back on to modem and router, BUT, if I lower the AC power delay setting to say 30-60 secs then the router will still never get a WAN connection.

Seems like modem has to be completly booted and "locked in" before the Router boots up.

(Motorola SB6120 and SB6140)

 

[RogerSC]

I do have a UPS but it only runs a couple hours and then...guess what...

Very seldom get power outages over a couple of hours here, guess we're lucky. But when we have, our network just comes up, haven't had to do anything special. So the comment about an issue with your ISP may be on target.

 

[bluepoint]

Yes bluepoint the modem does lock channels after restore of power. Also I have confirmed this Issue on 3 different brand new Rt-AC66U's and two motorola cable modems, as my previous post reads.

.

At some time most cable ISP's in the US had a problem with SB6120 with firmware version 1.0.1.8. The newer Docsis 3 spec is not compatible with that firmware but it has been corrected by Motorola. I would not think yours have that version? However, the SB6141 is another story.
What shows in the log when the router does not get an ip?

 

[bluepoint]

What is probably actually happening is that your ISP is blacklisting your MAC because it receives too many DHCP requests in a short period of time for some reason. I heard of at least one user having this problem with his ISP. The real solution would rather be to have the DHCP client wait longer between it's retries - something I plan on implementing at some point.

If the ISP blacklisted the MAC, he wouldn't be able to get an IP as soon as he rebooted the modem then the router unless he clone another MAC. The requests will not be seen by the server yet until the modem is bridged and bonded, I'm thinking how would it cause excessive requests?

 

[RMerlin]

If the ISP blacklisted the MAC, he wouldn't be able to get an IP as soon as he rebooted the modem then the router unless he clone another MAC. The requests will not be seen by the server yet until the modem is bridged and bonded, I'm thinking how would it cause excessive requests?

Possibly by sending DHCP request packets before the network is fully up and operational between the ISP and the modem.

 

[italyguy01]

I experience the same issue. If power goes out, the router will not connect again. You have to unplug both. Plug the cable modem in, wait till it is fully up and running, then plug the router in.

This is the only way to get it to work.

 

[RMerlin]

I tweaked timings in DHCP so at least it should no longer get blacklisted by Charter's DHCPD.

Retries will also occur every two minutes instead of every 20 secs, which might play nicer with some other ISPs.

 

[dolftb]

I tweaked timings in DHCP so at least it should no longer get blacklisted by Charter's DHCPD.

Retries will also occur every two minutes instead of every 20 secs, which might play nicer with some other ISPs.

Darn I wish I would have has this new version you are mentioning. Last night my modem lost connection with ISP (charter) for some reason, Modem cam back online but the router did not reconnect on its own. Dang, I mentioned in previous post that I hard wired a timer delay for the router to boot after the modem at powerloss, but that's not helping me now in this situation.

I would love to try it where I haven't seen it posted yet as a new firmware version. Where can I get it Rmerlin ??

Thanks....

 

[RMerlin]

Darn I wish I would have has this new version you are mentioning. Last night my modem lost connection with ISP (charter) for some reason, Modem cam back online but the router did not reconnect on its own. Dang, I mentioned in previous post that I hard wired a timer delay for the router to boot after the modem at powerloss, but that's not helping me now in this situation.

I would love to try it where I haven't seen it posted yet as a new firmware version. Where can I get it Rmerlin ??

Thanks....

I haven't finalized build 25 yet. Currently testing it on my network.

Drop me a PM tho, along with your router model. I'd like to have a Charter user actually test this DHCP change.

 

[CaptainSTX]

Reboot Delay

Overnight I experienced a power outage that lasted longer than my UPS battery. While everything restarted when the power came back and I had LAN access this morning until I power cycled my modem this morning I had no Internet access.

If you add the delay feature I would certainly implement it to eleiminate future problems.

 

[petrmegac]

I have this problem only when I turn on the DDNS in router. Cable modem Cisco, cabel operator UPC, czech republic.

 

[dolftb]

Thanks Rmerlin you fixed it for me !!

I did run into extended power outages myself, and never had any issue with my router properly reconnecting once the power came back. As mentionned, the router's DHCP client will simply keep resending DHCP queries until it actually gets a valid lease.

What is probably actually happening is that your ISP is blacklisting your MAC because it receives too many DHCP requests in a short period of time for some reason. I heard of at least one user having this problem with his ISP. The real solution would rather be to have the DHCP client wait longer between it's retries - something I plan on implementing at some point.

Rmerlin provided me a test version of upcoming firmware for the RT-AC66U/R. I verified that he is indeed right with regards to resending too many DHCP queries. After flashing I unplugged router and modem from AC waited a while, then plugged back in and after 5 1/2 minutes I was automatically reconnected to the internet. I tested twice with success. I also had problems when ISP was down and later back up again, that router would never get a WAN connection back. So in testing, I unplugged the AC of modem, turned back on while not touching the router, and again after 5 1/2 minutes bingo, WAN connected again. Yaaay !!

Modem : SB6120
ISP: Charter Communications Los Angeles area.

 

[RMerlin]

I sent the patch to Asus. Hopefully they will integrate it in some form in a future official release as well.