Can't access 192.168.100.1 when connected through my ASUS AX Router

[csm10495]

I think its just a modem.. It's an a Motorola MB8611

 

[ColinTaylor]

I think its just a modem.. It's an a Motorola MB8611

Looks like it.

What is your router's "WAN Connection Type" set to? Automatic IP? If so then presumably your router should also be getting a 192.168.100.x address (Network Map > WAN IP) just like the PC did.

 

[csm10495]

Set to Automatic IP... but the WAN IP in Network Map -> WAN IP is my public IP address

 

[ColinTaylor]

Set to Automatic IP... but the WAN IP in Network Map -> WAN IP is my public IP address

I'm out of ideas. Hopefully some other MB8611 owners can chime in.

 

[Tech Junky]

I was using a mb8600 and it would work intermittently for the management IP. Mostly when rebooting before it synced up and got online. Put a route to the subnet in the router with the wan interface to bypass routing rules and allow the modem to be reachable. I did this for things like Amazon prime that bitches about VPNs and no longer have the issue with Amazon and a couple of bank sites.

VPN + Amazon Prime - add some routes

So, I finally got the urge to dig into how to setup my DIY router / VPN to split tunnel off crap like Prime to make it work through the streamer box and all devices to avoid the infamous.... Anyway... I got it working on the streamer by adding some routes after messing around with trying to...

www.snbforums.com

 

[csm10495]

Do you have an example for the parameters for the route? I've tried: https://www.snbforums.com/threads/c...d-through-my-asus-ax-router.79150/post-790070

already.

When rebooting, i never seem to find a window where it works.

 

[tonymet]

Same issue with RT-AC5300 . It's not accepting the route configuration from the cable modem

SOLUTION: Add a static route​

• Network / Host IP = 192.168.100.1
• Netmask = 255.255.255.255
• Gateway = 0.0.0.0 (shows as * in system routing table once saved)
• Metric = 1 (default)
• Interface = WAN
• Add delete = click (+) to add before saving

Testing​

1. 1. : Ping from router
   1. target host = 192.168.100.1
2. Test from browser

 

[tonymet]

@csm10495 see comment above that should work for you.

 

[netmik3]

Same issue with RT-AC5300 . It's not accepting the route configuration from the cable modem

SOLUTION: Add a static route​

• Network / Host IP = 192.168.100.1
• Netmask = 255.255.255.255
• Gateway = 0.0.0.0 (shows as * in system routing table once saved)
• Metric = 1 (default)
• Interface = WAN
• Add delete = click (+) to add before saving

Testing​

1. 1. : Ping from router
   1. target host = 192.168.100.1
2. Test from browser

View attachment 45521

I tried this. It didn't work and didn't show up in my routing table. I did turn it on. I would prefer this so it doesn't stop working like the previous one that used the wan ip. I didn't try that one.

 

[tonymet]

I tried this. It didn't work and didn't show up in my routing table. I did turn it on. I would prefer this so it doesn't stop working like the previous one that used the wan ip. I didn't try that one.

Can you check the console-based routing table there? it should show up

 

[netmik3]

View attachment 45530


Can you check the console-based routing table there? it should show up

That's the screenshot I had right?

 

[tonymet]

That's the screenshot I had right?

Yours looks different than mine

 

[netmik3]

Yours looks different than mine

View attachment 45534

How weird I guess Merlin dresses it up but should be the same table. Thanks I'll try again later.

 

[netmik3]

I finally got it to show but with metric 2? I did enter 1. Anyway I still can't access my modem. I can access it fine with the computer directly plugged in.

 

[csm10495]

Yeah i made this route and it seems to work (for pings only... http doesn't work)... but next time i rebooted the router it stopped working again.

SOLUTION: Add a static route​

• Network / Host IP = 192.168.100.1
• Netmask = 255.255.255.255
• Gateway = 0.0.0.0 (shows as * in system routing table once saved)
• Metric = 1 (default)
• Interface = WAN
• Add delete = click (+) to add before saving

Testing​

1. 1. : Ping from router
   1. target host = 192.168.100.1
2. Test from browser

View attachment 45521

 

[Howard_inGA]

Try setting a static route to the external IP of the modem.

I've had the same problem accessing my CM1100's interface at 192.168.100.1 except that in my case, it started after I activated Ethernet Port Aggregation (LACP 802.3ad) in Feb 2022. After reading two dozen threads at least with regard to Port Aggregation on the CM1100, it seemed like that was a sacrifice to be made for using it. It made no sense, but no one seemed to have an answer.

Now months later, I see similar things happening across the board after a firmware update to the modem? I have an Asus AX88U, I added the static route using the router interface, saved the changes, powered the router off/on (this is a REQUIRED step since the reset always hangs the Asus web interface), and voila! I now have access to the CM1100's management interface again at 192.168.100.1

For everyone else who has a similar Asus router, here is a screenshot for reference!

This worked to regain access to the CM 1100 Modem!!
Find your IP at https://whatismyipaddress.com/
Go to the router LAN - Route page and enable static routes, then add this route info:

​

192.168.100.1

255.255.255.255

Your IP Address

1

WAN

Hit Apply button and access your modem as before!!!!!
THANKS!

 

[Howard_inGA]

Same issue with RT-AC5300 . It's not accepting the route configuration from the cable modem

SOLUTION: Add a static route​

• Network / Host IP = 192.168.100.1
• Netmask = 255.255.255.255
• Gateway = 0.0.0.0 (shows as * in system routing table once saved)
• Metric = 1 (default)
• Interface = WAN
• Add delete = click (+) to add before saving

Testing​

1. 1. : Ping from router
   1. target host = 192.168.100.1
2. Test from browser

View attachment 45521

So, the solution I'd proposed and used successfully got dropped doing modem attempted upgrades. I went back to this one, and service to modem restored, then added my solution above again. It worked like a charm as well. I prefer it, since it uses my unique IP address rather than 0.0.0.0
It is a bit of a pain, and I am clueless as to what is causing the loss of service...