access web gui of bridge mode modem with static routes? :)

[cola-untamed]

Hi all 

I'd like to be able to access my modem, which is in bridge mode, from a LAN client.
Can this be achieved using the guide below?
If so how do I assign a local ip (192.168.2.1) to the wan interface? Will this help me access my modem?

# Detail
I was trying to use the instructions linked below which state the following:
https://support.aa.net.uk/Router_-_EchoLife_HG612#Access_over_the_LAN1.2FWAN_cable

In your router, configure the WAN interface with a private (RFC1918) address in a different subnet to your main LAN. e.g. if your main LAN is 192.168.1.0/24 then configure the WAN interface with the address 192.168.2.1/24
Change the HG612's IP address (under "Basic -> "LAN" in the web interface) to be any address in that second subnet - e.g. 192.168.2.2/24
Under "Basic -> WAN" on the HG612, ensure both "Port binding:" checkboxes are unticked and press the Submit button to save the change. This step enables LAN access via LAN1.
At this point, your router knows where to send packets from devices on your main LAN to the HG612, but the HG612 doesn't know where to route responses (it can't be configured to have a default route via your router). To fix this, do the following:

Add a static route ("Advanced -> Routing" in the HG612's web interface) from the HG612 back to your main LAN. e.g. if your LAN is 192.168.1.0/24 and the router's WAN interface is 192.168.2.1 then you would create the following route:
Destination network address: 192.168.1.0
Subnet mask: 255.255.255.0
Default gateway: 192.168.2.1 (remember to also tick the checkbox)
Interface: LAN/br0
You should now be able to access the HG612's web and telnet interfaces from any device on your LAN, over the WAN/LAN1 cable. Note that access (with the new IP address) remains possible over LAN2.


Here's my setup https://postimg.cc/4KHhTQT7

• THE INTERNET>
• HG612 modem in bridge mode (192.168.2.2) >
• PCengines opnsense router (192.168.1.1) >
• switch >
• LAN clients (192.168.1.0/24)

I've tried the following:
https://i.postimg.cc/L5dQ6Zpj/1.jpg
https://i.postimg.cc/0Q9VY60Y/2.jpg
https://i.postimg.cc/4368HvV4/3.jpg

• assign a local ip (192.168.2.1) to the wan interface on the same subnet as my modem (192.168.2.2), under Interface > WAN > advanced (click here) > Local IP ( igb1 ). This setting doesn't seem to be retained after clicking save.
  
• add a static route under system > routes > configuration (192.168.2.0/24 > WAN_PPPOE)
  

This marquee option seems wonderfully obnoxious.
Thanks!

[chemlud]

The static route has to be assigned to the underlying physical interface, not the PPPoE interface imho... And don't forget to disable "Block private networks" on the WAN interfacce.

[cola-untamed]

Thanks for the suggestions

Unfortunately I can't see a way to create a static route for the interface as the dropdown only gives WAN PPPOE and Null.
https://i.postimg.cc/mcWkhSjv/brave-jp-JIg-O871g.png
https://i.postimg.cc/QBgt7WnH/brave-Mnz6-AYK2-CS.png

I've disabled "Block private networks" on the WAN interface. It was enabled before however.
https://i.postimg.cc/629Qf5Dz/brave-UTs-BSIb-VBF.png


I get ERR_CONNECTION_TIMED_OUT when trying to access the webgui (1912.168.2.2) of the modem from a lan client at the moment. I can access the web gui if wired straight into the modem with a laptop with a static IP of 192.168.2.3.

[chemlud]

Assign an interface "modemaccess" or something to the physical interface of WAN with "fixed IP" in the range of the LAN of your modem and use this interface for the outbound NAT...