[SOLVED] 23.7.4 Slow interface boot - dhclient giving up

Started by chucksense, September 18, 2023, 09:33:18 PM

Previous topic - Next topic
September 18, 2023, 09:33:18 PM Last Edit: September 18, 2023, 09:58:46 PM by chucksense
Dear all,
After the 23.7.4 update I'm having some issues after a reboot, as the WAN interface doesn't get an IP and therefore some of the services do not work properly. I've tried waiting 10+ minutes for the dhclient to get an IP but it doesn't work, need to go into the Interfaces --> Overview and force a DHCP renew, then everything starts to work as usual.
My WAN interface is VLAN 832 on a port connected to an ONT.

/usr/local/etc/rc.bootup: The command '/sbin/dhclient -c '/var/etc/dhclient_wan.conf' -p '/var/run/dhclient.vlan083.pid' 'vlan083'' returned exit code '1', the output was 'vlan083: no link .............. giving up'
/usr/local/etc/rc.reload_all: The command `/sbin/ifconfig 'igc1' mtu '9000'' failed to execute
/usr/local/etc/rc.reload_all: The command `/sbin/ifconfig 'igc2' mtu '9000'' failed to execute
/usr/local/etc/rc.reload_all: The command '/bin/kill -'TERM' '93260''(pid:/var/run/dhclient.vlan083.pid) returned exit code '1', the output was 'kill: 93260: No such process'
unknown dhcp option value 0x5a
/usr/local/etc/rc.newwanip: The command '/bin/kill -'TERM' '5274''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: 5274: No such process'


Any ideas?

Edit: Removed Certifiicate errors

Missed the Advanced Settings on the Interface for the dhclient. After some tweaking, seems the error is solved. Still seems dpinger is not fast enough for some gateways that even if working, appear as offline until I change one interface or restart the specific dpinger service for that gateway.