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

[netmik3]

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.

Yeah it started a few firmwares ago. Where do you turn it off

 

[coxhaus]

I am not sure as I don't remember. It has been at least a year since I installed Pfsense. There was a tick box when you installed Pfsense that would allow it. Looking at the firewall rules it is blocking all private IP addresses so you could add a rule above the blocking rules to allow IP 192.168.100.1.

PS
I found it. It is under the WAN interface. I might still go with allowing just 1 IP as above.

 

[netmik3]

I am not sure as I don't remember. It has been at least a year since I installed Pfsense. There was a tick box when you installed Pfsense that would allow it. Looking at the firewall rules it is blocking all private IP addresses so you could add a rule above the blocking rules to allow IP 192.168.100.1.

PS
I found it. It is under the WAN interface. I might still go with allowing just 1 IP as above.

Oh I only have Merlin

 

[coxhaus]

Oh I only have Merlin

Well look at your firewall rules. It could also be as stated above if your LAN network includes 192.168.100.1 as part of the LAN network the router will not pass it as it thinks it is inside the LAN. 192.168.100.1 needs to be classified as an unknown IP address so the router will pass it out of the WAN interface.

 

[ColinTaylor]

Oh I only have Merlin

Stock Asus and Merlin firmware doesn't block outgoing private IP addresses.

This should "just work" without the need for static routes or any other changes. The only time you might need a static route is if you're running a VPN client or some other form of custom routing on the router (e.g. PPPoE).

If your modem only accepts connections from clients with a 192.168.100.x address you'll have to change the WAN configuration.

 

[netmik3]

Stock Asus and Merlin firmware doesn't block outgoing private IP addresses.

This should "just work" without the need for static routes or any other changes. The only time you might need a static route is it you're running a VPN client or some other form of custom routing on the router (e.g. PPPoE).

If your modem only accepts connections from clients with a 192.168.100.x address you'll have to change the WAN configuration.

It stopped working for us after an Asus update not the modem

 

[ColinTaylor]

It stopped working for us after an Asus update not the modem

An update from what to what? Knowing that might point to the reason.

 

[netmik3]

An update from what to what? Knowing that might point to the reason.

Don't remember but it was around August 2022

 

[Crimliar]

So long as the LAN IP and subnet of the router are different to those on the modem it works. So:
Router 192.168.50.1/24
Modem 192.168.100.1/24
works.
Not doing this and sticking the gateway/modem on an address within the routers address space requires the gateway/modem to be connected to a LAN port on the router and a whole different configuration. It's also far less secure!
*Basic variations on this were (but no more) my setup for more than a decade - it does work, though it may require a power cycle!

 

[Crimliar]

Don't remember but it was around August 2022

There was a time, when that second control/reverse channel would be set up by the router with no user intervention, so long as the modem connected over a PPPoE rather than MPoA. I think in part this was the issue using the Netgear DM100 modem with Asus routers, it worked in bridge mode with Netgear routers but not Asus!

 

[ColinTaylor]

Don't remember but it was around August 2022

What make/model of modem do you have?
Are you using PPPoE?
Are you using a VPN?
Can you ping 192.168.100.1 from a PC?

 

[netmik3]

What make/model of modem do you have?
Are you using PPPoE?
Are you using a VPN?
Can you ping 192.168.100.1 from a PC?

ARRIS Surfboard S33
No and no
Yes it pings

 

[Ripshod]

tl;dr Have you tried connecting a pc/laptop to the second lan port for a connection? I read something about RFC1918 blocking or something on the router wan port. Don't know how relevant that last part is to asus, but still worth trying to connect directly

 

[ColinTaylor]

ARRIS Surfboard S33
No and no
Yes it pings

All the posts I've found on the internet say that you need the client device to have a 192.168.100.x address to be able to see the web interface. It also says the same here:

https://arris.my.salesforce-sites.com/consumers/articles/General_FAQs/S33-Web-Manager-Access

So try my previous suggestion from this post:

ifconfig $(nvram get wan0_ifname):0 192.168.100.2 netmask 255.255.255.0

I see that your modem has two ethernet ports. Maybe you have to use a specific port.