Losing Default Gateway when Release/Renew of DHCP based port

[stormy]

Is a known issue or something bad on my setup/steps? 

Using OPNsense 17.7.11-amd64 with PPPOE, I'm able to click RELEASE followed by RENEW on the INTERFACES:OVERVIEW page on the specific port and all works as expected after that.

However, when doing that RELEASE / RENEW on a DHCP connection (not pppoe), the link comes up, gets an IP, but no surfing is possible!

Comparing netstat -rn, before/after, shows that a single line is missing..... for the default gateway!

default x.y.z.q   UGS   igb1

The solution is to ssh into the opnsense box, and add a default gateway, e.g:

route add default x.y.z.q

and boom immediately all works fine..

Any thoughts welcomed..

Stormy.

[mimugmail]

Is this a Multi WAN setup?

[eugenezv]

Hello.

Same problem. No multi WAN. After upgrading 16.7->17.1->17.7 (two routers) all PCs in both LANs have lost access to the Internet.

In network adapters properties no default gateway address appears.

As temporary workaround used static addressing of PCs.

[stormy]

My setup is sort of Multi-WAN, the second NIC/port is not enabled.

I had this port:  3WANC interface (wan, pppoe0)

but, i've stopped using pppoe for the time, and that port is DOWN.

Instead i got:  4WANH interface (opt2, igb1)

and that is setup as DHCP, it can surf the net, however, clicking RELEASE/renew on that port, causes the above effect, in that default gateway is missing.  I must ssh into the opnsense, and add a default gateway, then all connected devices can surf the internet.

Thanks.

[seph04]

Same issue here. OPNsense 17.7, fresh VMWare install

Dual-wan setup with load balancing

WAN port -> Static IPv4
OPT1 -> DHCP

Gateway on WAN port configured as default gateway
Gateway on OPT1 port configured as dynamic


Sometimes DHCP internet connection goes down and DHCP release/renew fails to obtain an IP address.
When this happens system loses internet access and checking for updates fails, 1:1 nat to virtual IPs fails too.

In system -> routes you can see "default" destination route changes its gateway from the ip address of the default gateway on WAN interface to "link #3" (OPT1 interface).

To "fix" this I go to Interfaces -> Overview -> OPT1 release
Then System -> Gateways -> All and edit gateway on WAN interface.

Untick/save/apply/tick/save/apply on "default gateway" checkbox and system can check for updates again.
To restore 1:1 nat mappings I have to delete virtual IPs entries and recreate them again.

In system -> routes you can see "default" destination route changes back to the gateway on WAN interface.