Cannot refresh/release WAN IP - requires reboot

Started by axsdenied, December 09, 2022, 03:03:01 AM

Previous topic - Next topic
December 09, 2022, 03:03:01 AM Last Edit: February 15, 2023, 04:39:56 PM by axsdenied
Before you beat me up on this topic being brought up before, in various forms; you're right.  However, in my searching, I found ZERO resolutions outside of "rebooting" which is not what I'd want to do with an enterprise class option like OPNsense.

Internet Provider Context:

  • WAN - Cox Cable - Cable Modem (Private/bogon networks blocked and Reject leases from 192.168.100.1 set
  • WAN2 - T-Mobile Home Internet
PROBLEM: After an outage or issue with the Cox Cable connection (WAN), OPNsense fails over to T-mobile (WAN2) pretty gracefully.
After diagnosing the issue with the primary WAN connection and bring it back up, I'm unable to get a valid IP from the Cox Cable modem.

ATTEMPTED STEPS TO RESOVLE: If I go to INTERFACES: OVERVIEW, and select the WAN interface (wan, igb0) I do see both "Reload" and "Release" as options for DHCP.

If I attempt either, usually one of 2 things happens:

  • I can see the gateway assigned to the interface but i'm given no IP address or DNS servers
  • It hangs and is completely blank
I can do try these options for many times and the result is always the same.

The ONLY thing that allows me to receive an IP again is rebooting OPNsense.  This tells me, given its inability to communicate properly to obtain a refreshed IP without rebooting is clearly an OS/Driver/OPNsense issue.

Anyone know why this could be?
OPNsense 24.7.7 running on:
Dell Optiplex 3050
Intel I5-7600 @ 3.5Ghz (4 Cores)
Intel I350-T4 Nic
8G DDR4
256G SSD