Added by Oscar Francia over 14 years ago. Updated over 14 years ago.
0%
Description
WAN on DHCP, after a link down, no renegotiate ip from dhcp ( link up but no IP )
On lan interface working fine.
Updated by Ermal Luçi over 14 years ago
Please provide more information or this will not be considered.
Updated by Oscar Francia over 14 years ago
New image 17-06-10 nanobsd with default configuration
WAN DHCP
LAN 192.168.1.1
If I connect WAN interface to a network with dhcp it does not request ip!
( I've removed "Block private networks" on WAN interface first )
If force the request with "dhclient" it works fine!
Updated by Chris Buechler over 14 years ago
I noticed this recently, seems the hotplug event doesn't kick off dhclient like it used to.
Updated by Ermal Luçi over 14 years ago
Can you please try a recent snapshot and report the contents or /root/check_reload_status.log and system log messages with rc.linkup in it?
Updated by Chris Buechler over 14 years ago
/tmp/check_reload_status shows "After /tmp/rc.linkup"
System log shows "Kernel: em0: link state changed to UP" and "check_reload_status: rc.linkup starting", nothing else. dhclient never is started.
The file /tmp/rc.linkup contains the correct contents ("em0 start "), but the foreach($_SERVER['argv'] as $argv) only sees one argument (/tmp/rc.linkup) when run from check_reload_status.
After my commit today, running "php /etc/rc.linkup em0 start" manually works correctly. But check_reload_status does not run it correctly as it doesn't have the "em0 start" arguments.
Updated by Ermal Luçi over 14 years ago
Committed a fix since the contents of the file were being trashed by check_reload_status before running the actual command in this case rc.linkup.