Access GPON ONT behind WiFi router through WAN port
Hi :)
I am trying to setup access to my GPON ONT web GUI from my router LAN but with no success.
The GPON ONT is set up in bridge mode and connected to my router through the WAN port.
The ONT has a default IP address 192.168.100.1
The AX72 has a default IP address 192.168.0.1
I know I can access the ONT when connecting it directly to my PC's Ethernet port and setting up the network IP and Gateway, but I would like to have access to it without needing the direct connection.
I saw some threads online explaining how to do it but on different routers and through running some commands on it through SSH. Not sure it is possible to do this on the tp link routers and prefer not to do it.
Tried applying a similar change through the routing setting by applying a static routing record that gets reflected on the routing table, but couldn't get it to work.
Main things I tried where to define a static routing rule for the 192.168.100.1 (or 192.168.100.0/24 subnet) with the gateway being either 192.168.100.1 or the Internet IP address as it appears on the router's page.
Any ideas if this is possible to achieve?
TP-Link home grade routers don't support SSH commands.
If you open your AX72 Advanced=>Network=>Routing you should see the default route:
Destination Network Mask Gateway Interface
0.0.0.0 0.0.0.0 <your Internet IP address> WAN
This is the default route and it should include the destination 192.168.100.1.
If you can't ping 192.168.100.1 from your PC you may try setting a static route:
or if that doesn't work change the Default Gateway to 0.0.0.0 and try again.
If you still can't access the ONT delete the static route, try addig a second IP address to your PC network card - for example 192.168.100.254 and test again.
Thanks! unfortunately it is still not working, but there is some progress, so I guess we might be able to tweak it somehow.
Indeed I was unable to ping the ONT initially, and when adding the static route (same result with both default gateway options), I am still unable to ping it, but I do get a response back and it is from a 169.254.x.x IP address now that the destination is unreachable.
I think this has something to do with DHCP issues, right?
Any clue how we might be able to fix that?
P.S. adding a secondary IP didn't help :(
Here's how the routing table looks like after adding the static route
