Bug #656
closed
WAN on DHCP, after a link down, no renegotiate dhcp
Added by Oscar Francia about 14 years ago.
Updated about 14 years ago.
Description
WAN on DHCP, after a link down, no renegotiate ip from dhcp ( link up but no IP )
On lan interface working fine.
Please provide more information or this will not be considered.
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!
I noticed this recently, seems the hotplug event doesn't kick off dhclient like it used to.
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?
/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.
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.
- Status changed from New to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF