[SOLVED] 25.1.10 => 25.1.11: DHCP on WAN interface fails

[JanOsch]

Hi,

since updating to 25.1.11 (coming from 25.1.10) i'm not getting an ip address on one of my WAN interfaces anymore:
(This is a cable modem connecting, running in bridge mode, worked fine for months)

2025-07-18T11:34:40    Notice    dhclient    dhclient-script: Reason FAIL on vtnet2 executing   
2025-07-18T11:28:39    Notice    dhclient    dhclient-script: Reason FAIL on vtnet2 executing   
2025-07-18T11:22:40    Notice    opnsense    /usr/local/etc/rc.newwanip: Failed to detect IP for interface opt1   
2025-07-18T11:22:40    Notice    dhclient    dhclient-script: Reason FAIL on vtnet2 executing   
2025-07-18T11:22:39    Notice    dhclient    dhclient-script: New Routers (vtnet2): 91.x.x.x   
2025-07-18T11:22:38    Notice    dhclient    dhclient-script: New Routers (vtnet2): 91.x.x.x       
2025-07-18T11:22:38    Notice    dhclient    dhclient-script: New Broadcast Address (vtnet2): 91.x.x.255       
2025-07-18T11:22:38    Notice    dhclient    dhclient-script: New Subnet Mask (vtnet2): 255.255.255.0   
2025-07-18T11:22:38    Notice    dhclient    dhclient-script: New IP Address (vtnet2): 91.x.x.x       
2025-07-18T11:22:38    Notice    dhclient    dhclient-script: Reason TIMEOUT on vtnet2 executing

Deleted the interface completely, rebooted, added it again but still no joy. Disabled DHCPv6, makes no difference.

Any hints how to solve this would be highly appreciated.

Kind regards

Jan

[NevadaTech]

Hey,

I'm not clear if you've rebooted just the router or the router and the cablemodem. For Cox in NV, you MUST power cycle the cablemodem if there is a hardware change (I'm guessing an update to the router's MAC address in the cablemodem?). Did you change any hardware or the assigned interface?

[JanOsch]

Hi,

that's the same box (router and cable modem). In bridge mode it's just assigning a public ip address directly to my opnsense wan interface. In router mode you would get a private ip and the box would act as a router with NAT. Restarted this box multiple times, and waited at least an hour between beacuse somestimes i takes an hour to work again (especially when MAC changes). Just to make clear: No hardware change on my end, the mac address of the WAN interface is the same it's been before and no piece of hardware got changed. Just installed 2.5.11 an rebooted the VM (running on TrueNAS Scale 24.04).

Eventually i got it solved with calling the ISP, they completely resetted/reconfigured the box and then it started working again. Still weired because it exactly happended when rebooting after installing 2.5.11, running this setup for 1 1/2 years and never had this when doing updates (and i did almost each when it came out).

Kind regards

Jan