DHCP Client Failure After Upgrade

Started by leestrong, April 08, 2025, 05:08:38 PM

Previous topic - Next topic
April 08, 2025, 05:08:38 PM Last Edit: April 12, 2025, 11:44:23 PM by leestrong
Hi everyone,
After upgrading from 24.1 to 24.7.12, my WAN interface stopped getting an IP address from the ISP modem. I'm seeing repeated log entries like this in the system logs:

2025-04-08T16:11:29 Notice dhclient dhclient-script: Reason FAIL on vlan0.999 executing
2025-04-08T16:10:13 Notice dhclient dhclient-script: Reason FAIL on vlan0.999 executing
2025-04-08T16:08:57 Notice dhclient dhclient-script: Reason FAIL on vlan0.999 executing
...

Context:

  • My WAN is on a VLAN interface (vlan0.999).
  • "Block private networks" and "Block bogon networks" are both enabled.
  • I'm spoofing a MAC address on the interface.
  • During the boot sequence, system would stuck on the line "Configuring igc0_VLAN_Ext interface..." for a long time. igc0_VLAN_Ext is the interface for device vlan0.999

Troubleshooting so far:
  • Tried obtaining IP from a different ethernet interface without VLAN, same error.
  • Power-cycled the OPNSense and ISP modem.
  • Tried removing/re-adding the MAC spoof, but no luck.
  • Tried booting 24.1 & 25.1 on live USB, and loading a backed up configuration file that was known to be working. Same error.

Has anyone seen this issue on 24.7.12 or have suggestions for debugging?
Any tips on where to find further details to determine the cause of dhclient failure?

Thanks in advance for any insights!

I experiencing the same issue but am on version 25.1.4_1
in my case I see the dhclient get a correct ip from the dhcp but it won't update the WAN Interface with the sme reason.

Quote from: supertorben on April 09, 2025, 12:00:15 PMI experiencing the same issue but am on version 25.1.4_1
in my case I see the dhclient get a correct ip from the dhcp but it won't update the WAN Interface with the sme reason.

Interesting, how did you find out that dhclient got a correct ip, from the log shown in GUI?

I am on 25.1.3 and have run into the same (or similar) thing yesterday. Can't get an IP from my bridged cable modem anymore, even though it appears to be offering an IP:

Date                   Severity Process         Line
2025-04-10T21:51:53 Notice opnsense /usr/local/etc/rc.newwanip: Failed to detect IP for interface wan
2025-04-10T21:51:52 Notice dhclient dhclient-script: Reason FAIL on igc1 executing
2025-04-10T21:51:51 Notice dhclient dhclient-script: New Routers (igc1): 83.252.64.1
2025-04-10T21:51:50 Notice dhclient dhclient-script: New Routers (igc1): 83.252.64.1
2025-04-10T21:51:50 Notice dhclient dhclient-script: New Broadcast Address (igc1): 83.252.95.255
2025-04-10T21:51:50 Notice dhclient dhclient-script: New Subnet Mask (igc1): 255.255.224.0
2025-04-10T21:51:50 Notice dhclient dhclient-script: New IP Address (igc1): 83.252.66.28
2025-04-10T21:51:50 Notice dhclient dhclient-script: Reason TIMEOUT on igc1 executing
2025-04-10T21:50:38 Notice opnsense /interfaces.php: plugins_configure monitor (execute task : dpinger_configure_do(,[WAN_DHCP]))
2025-04-10T21:50:38 Notice opnsense /interfaces.php: plugins_configure monitor (,[WAN_DHCP])
2025-04-10T21:50:38 Warning opnsense /interfaces.php: ROUTING: refusing to set interface route on addressless wan(igc1)
2025-04-10T21:50:38 Notice opnsense /interfaces.php: ROUTING: entering configure using wan
2025-04-10T21:50:38 Notice opnsense /interfaces.php: plugins_configure newwanip:rfc2136 (,[wan])
2025-04-10T21:50:37 Notice opnsense /interfaces.php: plugins_configure dns (execute task : unbound_configure_do())
2025-04-10T21:50:37 Notice opnsense /interfaces.php: plugins_configure dns (execute task : dnsmasq_configure_do())
2025-04-10T21:50:37 Notice opnsense /interfaces.php: plugins_configure dns ()
2025-04-10T21:50:37 Notice opnsense /usr/local/etc/rc.newwanip: Failed to detect IP for interface wan
2025-04-10T21:50:36 Notice opnsense /interfaces.php: plugins_configure dhcp (execute task : dhcpd_dhcp_configure())
2025-04-10T21:50:36 Notice opnsense /interfaces.php: plugins_configure dhcp ()
2025-04-10T21:50:36 Notice opnsense /interfaces.php: plugins_configure ipsec (execute task : ipsec_configure_do(,wan))
2025-04-10T21:50:36 Notice opnsense /interfaces.php: plugins_configure ipsec (,wan)
2025-04-10T21:50:36 Notice opnsense /interfaces.php: plugins_configure monitor (execute task : dpinger_configure_do(,[WAN_DHCP]))
2025-04-10T21:50:36 Notice opnsense /interfaces.php: plugins_configure monitor (,[WAN_DHCP])
2025-04-10T21:50:36 Warning opnsense /interfaces.php: ROUTING: refusing to set interface route on addressless wan(igc1)
2025-04-10T21:50:36 Notice opnsense /interfaces.php: ROUTING: entering configure using wan
2025-04-10T21:50:36 Notice dhclient dhclient-script: Reason FAIL on igc1 executing
2025-04-10T21:50:35 Notice dhclient dhclient-script: New Routers (igc1): 83.252.64.1
2025-04-10T21:50:34 Notice dhclient dhclient-script: New Routers (igc1): 83.252.64.1
2025-04-10T21:50:34 Notice dhclient dhclient-script: New Broadcast Address (igc1): 83.252.95.255
2025-04-10T21:50:34 Notice dhclient dhclient-script: New Subnet Mask (igc1): 255.255.224.0
2025-04-10T21:50:34 Notice dhclient dhclient-script: New IP Address (igc1): 83.252.66.28
2025-04-10T21:50:34 Notice dhclient dhclient-script: Reason TIMEOUT on igc1 executing
2025-04-10T21:49:34 Notice dhclient dhclient-script: Reason PREINIT on igc1 executing
2025-04-10T21:49:34 Notice dhclient dhclient-script: Reason EXPIRE on igc1 executing
2025-04-10T21:49:34 Notice dhclient dhclient-script: Reason PREINIT on igc1 executing

April 12, 2025, 11:48:19 PM #4 Last Edit: April 12, 2025, 11:53:55 PM by leestrong
Update: Tried booting with a USB with latest V25.1 & older V24.1 (was working) on live mode, then loaded a configuration that was known to be working. Same error "dhclient dhclient-script: Reason FAIL on vlan0.999 executing".

Also noticed that during the boot sequence, system would stuck on the line "Configuring igc0_VLAN_Ext interface..." for a long time. igc0_VLAN_Ext is the interface for device vlan0.999.

Is it possible that the upgrade 24.1 -> 24.7 has messed up the firmware of the Intel i255 NIC?