Topics

Hi All,

I've got an ongoing issue that I've had both with OPNsense and previously it's main rival before I switched.

Essentially the problem is that if the cable modem loses connectivity to the internet for a period of time, when it regains connectivity, the WAN IP on OPNsense is not renewed unless I reboot.

The cable modem does not shut down it's "LAN" site port when it loses connectivity so OPNsense will not see a link state change when the cable modem loses connectivity or comes back. Additionally I now run OPNsense virtually so it will certainly not see a link state change even when the cable modem is rebooted.

Would it be possible to configure OPNsense to attempt to renew the WAN IP via DHCP every minute while the WAN gateway monitor is offline?

If not, would https://forum.opnsense.org/index.php?topic=10924.0 still be applicable?

Hi All,

I suspect that this has been covered before.
I've read through a few topics but unfortunately they don't really answer my question.

I have a fairly simple network.
WAN is DHCP
LAN is static in a /30 transport link to an internal layer 3 switch where the interfaces for the internal subnets reside.

With pfSense the automatic outbound NAT allowed for the subnets behind the layer 3 switch to be NAT'd out the WAN.
However, with OPNsense I need to manually define the outbound NAT rules for these subnets.
Simply adding a firewall rule to the LAN interface to allow these subnets out isn't enough to apply NAT to them.

Is this intended behavior or a bug?

If intended I can fully understand.
I mostly come from a Cisco ASA background where you can manually define outbound NAT for a group of subnets or use ANY to allow outbound NAT for anything going in and out of the specified interfaces.