Remove bogus commands that adds a route to the new address pointing to dhcp.It seems uncertain either to be a typo of $new_ip_address and $old_ip_address my test show that either cases it does more harm than good.
For now remove it altogether since it causes strange issues and makes ipsec tunnels not work on the interface with the new address.
DHCP Renew does "too much"
Ticket #1260
Nuke old and unused code which was commented out.
Bring back hostname option since it is not leading to the short write errors
Sprinkle debugging statements throughout to try and obtain a read of where the dhclient process is going south.
Somehow the HOSTNAME code will lead to short write errors under unusual renew load. Comment out this code until we can figure out why this is happening.
Found-by: GAndreone@imapro.com
Do not set an exit status in dhclient-script.
From a post that I dug up from Brooks:
Why on earth are you exiting with $1 as the status? This is almostcertainly the problem. You should not exit from dhclient-exit-hooksat all since it occurs in the context of dhclient-script and this exit...
back out recent change.
Woops, log an error to system logs when we restart check_reload_status from dhclient-script instead of simply echoing out where someone may not even see it.
If for any reason check_reload_status is not started when dhclient fires of dhclient-script, restart it.
View revisions
Also available in: Atom