RT-BE88U won't connect to internet after reboot.

[ynnek63]

This is the 2nd BE88U I have bought that won't connect to the internet after a manual reboot. The first one I returned thinking it might just be a defective unit, but the second unit is doing the same thing. The first was bought from Best Buy and the second from Amazon. The initial setup on both went well. Everything seemed to working well until I did a manual reboot thru the webUI. On both units I did physically unplug both the cable modem and the router and then plugged in the cable modem in first, waited for it to boot up and connect and then plugged the router in and powered it up. Still no internet. I can see devices connected to my local network, but no internet connectivity. The newest unit was on the latest firmware when I did a check thru the UI.

I am coming from an RT-AX88U, which I am currently using to get internet. I have owned 4 or 5 Asus routers, most with Merlin firmware, and have never had any issues like this. I even tried swapping the ethernet cable to no avail.

My internet provider is Spectrum 1gb plan (my speeds are usually in the 650mbps range) with an Arris SB6190 cable modem which I own.
Any help or suggestions would be greatly appreciated. I wanna love this router like I have my other Asus routers.

 

[junior120872]

I've seen issues like this, but on my fibre internet. The mac address on the router is cached at the ONT and needs a considerable amount of time to be powered down for the cache to clear. I'm not sure if Spectrum or your cable modem have a similar caching policy. Have you attempted to use the RT-AX88u as a bridge to pass traffic through to the BE to see if it then connects? Or setup the BE as an aimesh node and connected a device to it and get internet?

 

[PunchCardBoss]

Any help or suggestions would be greatly appreciated. I wanna love this router like I have my other Asus routers

Have you tried adjusting router "WAN > Internet Connection > DHCP query frequency".

Router and modem must negotiat handshaking. Modems are designed to work with many routers and routers to work with many brand modems. This handshaking can take several minutes and reboots for your modem to go through many hand shaking schemes. So, my recomendation is to allow several minutes (perhaps up to 10 minutes) for hand shaking to work.

I also suggest you factory reset your modem so it is forced to go through it's handshaking algorithm when you connect your router.

ADDED....
BTW, if your Surfboard modem is 5 years or older, time for a new one. Why? Older modems don't support newer modem firmware that may accept handshaking.

I had just such a case with my old Motorola 6800. I ended up replacing it with a Netgear and had to wait several minutes as the new modem went through several handshaking algorithm before connecting to my AX-88U-PRO.

 

[ynnek63]

Have you tried adjusting router "WAN > Internet Connection > DHCP query frequency".

Router and modem must negotiat handshaking. Modems are designed to work with many routers and routers to work with many brand modems. This handshaking can take several minutes and reboots for your modem to go through many hand shaking schemes. So, my recomendation is to allow several minutes (perhaps up to 10 minutes) for hand shaking to work.

I also suggest you factory reset your modem so it is forced to go through it's handshaking algorithm when you connect your router.

ADDED....
BTW, if your Surfboard modem is 5 years or older, time for a new one. Why? Older modems don't support newer modem firmware that may accept handshaking.

I had just such a case with my old Motorola 6800. I ended up replacing it with a Netgear and had to wait several minutes as the new modem went through several handshaking algorithm before connecting to my AX-88U-PRO.

I took your advice and bought a new modem and that seems to have done the trick. Thanks for the help!

 

[ynnek63]

I've seen issues like this, but on my fibre internet. The mac address on the router is cached at the ONT and needs a considerable amount of time to be powered down for the cache to clear. I'm not sure if Spectrum or your cable modem have a similar caching policy. Have you attempted to use the RT-AX88u as a bridge to pass traffic through to the BE to see if it then connects? Or setup the BE as an aimesh node and connected a device to it and get internet?

Thank you for your response and I was going to try that but a new modem seems to have done the trick. Thank you again.

 

[HelpFriends4free]

Found this in a search for this new router of mine. After an automatic firmware update, no connection! Rolled it back as my ISP was fine, still nothing.

Ultimately i had to explicitly set which WAN port to use, auto detection was broken.

 

[Tim 23]

I just upgraded to this router and I experienced a similar issue.

I have Optimum fiber, they provide their own ONT (no other choice at this point) which also has a build in router. They must enable bridge mode which basically sets Lan 1 for my particular ONT to pass a public IP. Previously I had a AX86U, for the past 2-3 years. It just failed, which prompted the change. I had no issues caused by the AX86U in regards to establishing a WAN IP, If I had an issue It was always an issue with the ONT failing to keep bridge mode or the equipment just failing.

When I got the BE88U, at first I could not get a WAN IP through the auto detect, I was able to select the port, and eventually it established an IP. Some of my devices are on static IP, so I changed the internal IP from the default 192.168.50.1 router to 192.168.1.1. This was working fine, and then I had to manually reboot. It was then I lost the WAN IP. I kept getting there is an issue message and a prompt to unplug the ONT for at least 2 minutes and try again. I tried this for hours. Factory reset the router, and nothing. Somewhere along the lines of cycling the ONT, the ONT then stopped getting internet internally .. If you factory reset the ONT, it drops bridge and you must call or have tech come reset it.... So now Im SOL. I unplugged the ONT over night, and in the morning still no internet on their end, tech confirmed and scheduled a house call. Another over night unplugged, this morning as tech shows up, it surprisingly grabbed internet on the ONT (maybe a 20 hour unplug cleared the cache?). They replaced the modem anyway, and after a reboot and router factory reset, we have an WAN IP.

I asked Advanced Tech about a MAC address cache maxing out or w/e, said they were not aware of that. They also couldn't access the router at the time of call due to no internet. They saw the ONT, but no access beyond that.



All good? Nope. I had to unplug the router to move it to where it really belongs. Got it powered up and it did grab the WAN IP.. Then I changed to the 192.168.1.1 to avoid resetting my static devices. As soon as it rebooted, I dropped the WAN and got the DHCP error.. I thought maybe since I had a Node plugged into the 2.5gb port and the WAN into the 10gb port, it was not properly managing it. Tried dropping the node with no success. I eventually decided to just do another Factory Reset on the BE88U. Did the manual mode and it picked up my WAN IP.

Now I'm afraid to reboot, but I also don't know if for some reason the 192.168.1.1 subset caused the conflict and coincidentally the first ONT failed, indicated by not getting its internal IP internet status... The ONT internal router uses the same 1.1, but with my previous router it didn't have an issue. I currently have the ONT WAN into the 2.5 gb WAN port. and the Node into one of the LAN ports. Using the default 50.1 .. I'm afraid to move anything, but at the same time if this is going to be an issue with this Router, I'll have to return it

I don't want to try anything tonight, spent too much time at this point, and it would be nice to just have internet again.

 

[Tim 23]

Just to update, I ended up rebooting. The subnet has no bearing, it just so happened that a factory reset cleared something to work. Spoke with Advanced Tech, they did a firmware update on the ONT and it instantly grabbed the WAN. I rebooted the router and it dropped the WAN - DHCP error. We factory reset the ONT, but the bridge mode would not take. Router grabbed the LAN instantly, but without being able to enable Bridge remotely, no way to get a WAN. They are going to replace the ONT, the one I have is an older model usually for the slower plans, I'll update after tech comes and give me hopefully the newer ONT.

 

[Tim 23]

Tech came, the only solution would be a factory reset, and then enabling bridge mode again... or taking it out of bridge and then back in. As a customer this needs to be performed by tech support.

They are following up with me tomm.. im sure i'll waste 2 hours doing the same steps..

Asus firmware may be an issue, but the only solution is resolved by tech and clearing the ONT

 

[jzchen]

Before it was okay to do that, have 192.168.1 on a router then the router connected to it the same 192.168.1 . For some reason the newer models do not "like" this setup. You are trying to enforce this while they are now made to resist/avoid this. Try to change the ISP router LAN IP to 192.168.50.1. Then change, (it may automatically do so,) the ASUS LAN IP to 192.168.1 as you wish...

EDIT- As FYI my AT&T gateway is set to IP Passthrough. It's LAN IP is 192.168.1.254. I would not dare try to set the LAN IP of my ASUS router to 192.168.1, and thankfully by default it is 192.168.50. My TP-LInk router defaults LAN IP to 192.168.68.1. IF it sees the router ahead is 192.168.68 it will change the 68 to something else...

 

[Tim 23]

Before it was okay to do that, have 192.168.1 on a router then the router connected to it the same 192.168.1 . For some reason the newer models do not "like" this setup. You are trying to enforce this while they are now made to resist/avoid this. Try to change the ISP router LAN IP to 192.168.50.1. Then change, (it may automatically do so,) the ASUS LAN IP to 192.168.1 as you wish...

EDIT- As FYI my AT&T gateway is set to IP Passthrough. It's LAN IP is 192.168.1.254. I would not dare try to set the LAN IP of my ASUS router to 192.168.1, and thankfully by default it is 192.168.50. My TP-LInk router defaults LAN IP to 192.168.68.1. IF it sees the router ahead is 192.168.68 it will change the 68 to something else...

So the issue with that, is if a factory reset happens on the ISP ONT it will default to 1.1 and I'll have all the conflicts, so for now I prefer to keep it 50.1 (however I currently have issues routing to the virtual host of my NVR, LTS support thought having 50.1 was very odd, a whole other problem I need to solve)

After the firmware update of the ONT, I have better results (prior to firmware I could not pull the DHCP Wan without a factory reset of the ONT).

Now, if I reboot ASUS, i'll drop WAN, only 1 out 20 times did it grab the WAN

If I reboot ASUS and power cycle the ONT, it grabs most of the time.

If I reboot ASUS and unplug the ethernet cable, it will then grab the WAN most of the time (prior to the ONT firmware update, it would not do this)

If I unplug the ASUS, and power cycle, it will not grab the WAN without one of the other solutions.


The ONT firmware helped, so this is a 2 sided issue, Asus needs to update the firmware to disconnect the WAN port during a reboot. If I turn off WAN in the settings it does not work, my thought is it defaults that port to something else, and the ONT needs to see a real disconnect. I've had better luck using the 2.5 WAN port, so I'll leave it as that. I've tried a lot of the other solutions like MAC cloning etc..

My current solution is I added a network switch between my modem and router (nothing else on it). I have a Wi-Fi outlet connected to the Wi-Fi of the ONT. ONT by default has WIFI, I cant use a wifi switch on the modem as nothing runs local, so once off command is given, no way to power back. To be honest, I have not tried this. I have to run out of town for a bit, and need things up for my family while away, but I think this should work.

MY backup backup, is I should be able to factory reset my router remotely (or call ISP to cycle the ONT). This will then assign my network the 192.168.1.X. (I can factory reset remote, but not reboot remote) After the factory reboot I'll just have to hope I can access the port forwarding to allow access to my network.

When I get back into town, Optimum did reach out and wanted to move forward with testing with their engineering side, but if the addition of a switch works, it will be easy enough fix. Fingers crossed : things work out when the lease expires, Bad timing to not be around.