What's new

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

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

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.
 
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.

 
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


1668561073938.png
 
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.
 

Attachments

  • Screenshots_2022-11-15-21-40-35.png
    Screenshots_2022-11-15-21-40-35.png
    64.5 KB · Views: 103
  • Screenshots_2022-11-15-21-40-15.png
    Screenshots_2022-11-15-21-40-15.png
    92.9 KB · Views: 108
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.
1668581085885.png



Can you check the console-based routing table there? it should show up
 
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.
 

Attachments

  • Screenshots_2022-12-04-00-48-05.png
    Screenshots_2022-12-04-00-48-05.png
    21.6 KB · Views: 94
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
 
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.1255.255.255.255Your IP Address1WAN

Hit Apply button and access your modem as before!!!!!
THANKS!
 
Last edited:
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...
 
Last edited:
To a point it depends on how you have your modem connected, and even brand/model! Mostly setting:
WAN>
Get The Wan IP address Automatically = No
IP Address = 192.168.100.10
Subnet = 255.255.255.0
Gateway = 192.168.100.1

That will create an additional connection on the WAN port connecting to a modem that is at 192.168.100.1 with the router identifying itself on the WAN port to that device as 192.168.100.10. This does absolutely work in many cases (if your modem has a different address then the IP and Gateway need to be changed). Doing this should add a second gateway, not just replace the address issued to the router from the WAN DHCP.

*Historically this has worked for me with Draytek Modems and Huawei modems but not with Xzyel modems or the Netgear DM100!
 
Pfsense now blocks all private IP addresses from the firewall to the WAN side so maybe ASUS does also. I guess they only use the WAN IP. You can turn this off if you want. But it is on by default now. So, 192.168.100.1 will not pass the firewall by default.
 
Last edited:

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top