OPNsense Forum
Archive => 21.7 Legacy Series => Topic started by: NetGobbler on January 08, 2022, 07:02:45 am
-
I have a TPLink modem, which is in bridge mode obviously, allowing opnsense the ability to bridge to the device and act as a router.
I _think_ (can't recall) it was set to 192.168.1.1, whereas my network behind opnsense is 192.168.0.x
Does anyone have any tips on how to check this? The main thing you lose when bridging a modem, is the sync speed and line diagnostics available on the modem itself.
-
You might have block local networks set for your wan interface. You might look into turning that off, blocking local nets in rules, but allow access to 192.168.1.1 from a few computers.
-
Set outbound NAT to hybrid, add a manual rule allowing the machine/network in your LAN to the network of the bridged modem for interface WAN and done. I have not disabled the "block private networks" on WAN, works anyway, as traffic originates from LAN.
-
@NetGobbler
Can you post a screenshot of Interfaces -> Assignments ?
-
...there have been discussions in the past
https://forum.opnsense.org/index.php?topic=12094.msg55343#msg55343
PPPoE on WAN? I have DHCP...
-
@NetGobbler
Can you post a screenshot of Interfaces -> Assignments ?
Sorry for not getting back sooner, I didn't get email notification.
https://imgur.com/a/FGRpb2D
Would it be better to set the IP to be 192.168.0.199 (unused IP, not in DHCP scope) on the modem? or should it stay on the 192.168.1.x range?
opnsense obviously does DHCP assigning.
-
I recall having real difficulty getting this working but I'm utterly baffled it's working at all.
My DSL modem in bridge mode is infact 192.168.0.254.
My opnsense box, connected to it, 192.168.0.254 .....
DHCP is still on, on the modem.. totally surprised any of this is working and surprised I left it like this.
(I connected an ethernet cable to one of the other 4 ports on the DSL modem) as what I really wanted was the DSL stats for the line which is misbehaving.
-
Not sure if this helps, but it took me while to find a config my modem and OPNSense were both happy with. My ISP uses PPPoE and bridge mode is acheived simply by setting the OPNSense WAN interface as PPPoE and entering the credentials, the modem then passes this straight through.
To get access to the modem's web GUI a second physical cat6 jumper was connected between OPNSense and the modem (which has 4 LAN ports). A MODEM interface was then created and the second physical connection assigned to it. A firewall outbound NAT rule of translation type "interface address" was added to provide access between MODEM net and LAN net.
This seems to work really well, despite being a little clunky with the two physical connections.
-
Not sure if this helps, but it took me while to find a config my modem and OPNSense were both happy with. My ISP uses PPPoE and bridge mode is acheived simply by setting the OPNSense WAN interface as PPPoE and entering the credentials, the modem then passes this straight through.
To get access to the modem's web GUI a second physical cat6 jumper was connected between OPNSense and the modem (which has 4 LAN ports). A MODEM interface was then created and the second physical connection assigned to it. A firewall outbound NAT rule of translation type "interface address" was added to provide access between MODEM net and LAN net.
This seems to work really well, despite being a little clunky with the two physical connections.
Yeah, that's the way to go since pfsense times...
-
My LAN is on 192.168.0.1/24, my modem GUI is on 192.168.2.1 and I found an esier way to access it, i.e. I've assigned the WAN physical port (OPT2) to igb0 which in my case is my WAN PPPOE0 and then I've assigned to OPT2 a static IP address in the same subnet, i.e. 192.168.2.10 - I have no NAT-Outbound rules.
-
Sure, but with the outbound NAT rule I can allow a single LAN IP to the single IP of the modem. Not more.