d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
013cb2e961
freebsd-nq/etc/rc.d/dhclient

65 lines
1.2 KiB
Plaintext
Raw Normal View History

Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names.
2001-06-16 07:16:14 +00:00
#!/bin/sh
#
Merge in all the changes that Mike Makonnen has been maintaining for a while. This is only the script pieces, the glue for the build comes next. Submitted by: Mike Makonnen <makonnen@pacbell.net> Reviewed by: silence on -current and -hackers Prodded by: rwatson
2002-06-13 22:14:37 +00:00
# $FreeBSD$
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names.
2001-06-16 07:16:14 +00:00
#
# PROVIDE: dhclient
Support code for the OpenBSD dhclient. This significantly changes the way interfaces are configured. Some key points: - At startup, all interfaces are configured through /etc/rc.d/netif. - ifconfig_<if> variables my now mix real ifconfig commands the with DHCP and WPA directives. For example, this allows media configuration prior to running dhclient. - /etc/rc.d/dhclient is not run at startup except by netif to start dhclient on specific interfaces. - /etc/pccard_ether calls "/etc/rc.d/netif start <if>" to do most of it's work. - /etc/pccard_ether no longer takes additional arguments to pass to ifconfig. Instead, ifconfig_<if> variables are now honored in favor of pccard_ifconfig when available. - /etc/pccard_ether will only run on interfaces specified in removable_interfaces, even if pccard_ifconfig is set.
2005-06-07 04:49:12 +00:00
# KEYWORD: nojail nostart
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names.
2001-06-16 07:16:14 +00:00
. /etc/rc.subr
Make use of the dhclient script. This will bring up/down dhcp interfaces. Approved by: markm (mentor)
2003-04-18 17:53:02 +00:00
. /etc/network.subr
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names.
2001-06-16 07:16:14 +00:00
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
ifn="$2"
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names.
2001-06-16 07:16:14 +00:00
name="dhclient"
Luke Mewburn has indicated that they (NetBSD) are not interested in keeping the scripts under rc.d in sync with us. So, remove NetBSD specific stuff (which made our scripts more complicated than necessary). The NetBSD ident string will be left intact, both for history and also incase we wish to pull in future versions.
2004-01-17 10:40:45 +00:00
rcvar=
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
pidfile="/var/run/${name}.${ifn}.pid"
start_precmd="dhclient_prestart"
Fix handling of rc_force in /etc/rc.d/dhclient Variable 'rc_force' is accessible only at the time of rc_run_command, so it can't be examined from the script's main code. Spotted by: hrs Reviewed by: hrs, des Approved by: des MFC after: 2 weeks
2011-10-28 06:03:38 +00:00
stop_precmd="dhclient_pre_check"
# rc_force check can only be done at the run_rc_command
# time, so we're testing it in the pre* hooks.
dhclient_pre_check()
{
if [ -z "${rc_force}" ] && ! dhcpif $ifn; then
rc.d: document 'quiet' prefix and fix dhclient/devd interaction Document the current semantics of the 'quiet' command prefix in the rc.subr(8). Fix dhclient rc.d script: it should not call err() for non-DHCP-enabled interface when it is called from devd, because the latter just blindly calls 'service dhclient quietstart' on each "link up" event. Since the 'quietstart' will silence the message "Cannot 'start' <foo>. Set <foo>_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'." and running dhclient on the non-DHCP-enabled interface is the same thing as running the service <foo> without <foo>_enable set, such modification is in sync with the current semantics of the 'quiet' prefix. Approved by: glebius Reviewed by: freebsd-rc list MFC after: 2 weeks
2012-01-12 06:48:11 +00:00
local msg
msg="'$ifn' is not a DHCP-enabled interface"
if [ -z "${rc_quiet}" ]; then
dhclient: don't use syslog for logging non-DHCP interface errors We should show the error to user, but it doesn't deserve syslog. Approved by: jhb
2012-01-20 17:19:50 +00:00
echo "$msg"
rc.d: document 'quiet' prefix and fix dhclient/devd interaction Document the current semantics of the 'quiet' command prefix in the rc.subr(8). Fix dhclient rc.d script: it should not call err() for non-DHCP-enabled interface when it is called from devd, because the latter just blindly calls 'service dhclient quietstart' on each "link up" event. Since the 'quietstart' will silence the message "Cannot 'start' <foo>. Set <foo>_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'." and running dhclient on the non-DHCP-enabled interface is the same thing as running the service <foo> without <foo>_enable set, such modification is in sync with the current semantics of the 'quiet' prefix. Approved by: glebius Reviewed by: freebsd-rc list MFC after: 2 weeks
2012-01-12 06:48:11 +00:00
else
debug "$msg"
fi
dhclient: don't use syslog for logging non-DHCP interface errors We should show the error to user, but it doesn't deserve syslog. Approved by: jhb
2012-01-20 17:19:50 +00:00
exit 1
Fix handling of rc_force in /etc/rc.d/dhclient Variable 'rc_force' is accessible only at the time of rc_run_command, so it can't be examined from the script's main code. Spotted by: hrs Reviewed by: hrs, des Approved by: des MFC after: 2 weeks
2011-10-28 06:03:38 +00:00
fi
}
Make use of the dhclient script. This will bring up/down dhcp interfaces. Approved by: markm (mentor)
2003-04-18 17:53:02 +00:00
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
dhclient_prestart()
Make use of the dhclient script. This will bring up/down dhcp interfaces. Approved by: markm (mentor)
2003-04-18 17:53:02 +00:00
{
Fix handling of rc_force in /etc/rc.d/dhclient Variable 'rc_force' is accessible only at the time of rc_run_command, so it can't be examined from the script's main code. Spotted by: hrs Reviewed by: hrs, des Approved by: des MFC after: 2 weeks
2011-10-28 06:03:38 +00:00
dhclient_pre_check
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
# Interface-specific flags (see rc.subr for $flags setting)
specific=$(get_if_var $ifn dhclient_flags_IF)
Add a -p switch to dhclient. The switch tells dhclient to persist despite the interface link status. Add dhclient_flags_iface and background_dhclient_iface rc.conf options. (where iface is a specific interface). These can be used to give interface specific flags to dhclient. Reviewed by: brooks@
2006-08-17 17:12:27 +00:00
if [ -z "$flags" -a -n "$specific" ]; then
rc_flags=$specific
fi
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
background_dhclient=$(get_if_var $ifn background_dhclient_IF $background_dhclient)
Having gone to the trouble of setting up a variable, we should use it.
2007-03-25 19:45:20 +00:00
if checkyesno background_dhclient; then
Support code for the OpenBSD dhclient. This significantly changes the way interfaces are configured. Some key points: - At startup, all interfaces are configured through /etc/rc.d/netif. - ifconfig_<if> variables my now mix real ifconfig commands the with DHCP and WPA directives. For example, this allows media configuration prior to running dhclient. - /etc/rc.d/dhclient is not run at startup except by netif to start dhclient on specific interfaces. - /etc/pccard_ether calls "/etc/rc.d/netif start <if>" to do most of it's work. - /etc/pccard_ether no longer takes additional arguments to pass to ifconfig. Instead, ifconfig_<if> variables are now honored in favor of pccard_ifconfig when available. - /etc/pccard_ether will only run on interfaces specified in removable_interfaces, even if pccard_ifconfig is set.
2005-06-07 04:49:12 +00:00
rc_flags="${rc_flags} -b"
Always start dhclient in the background. Reviewed by: mtm
2003-07-28 08:15:52 +00:00
fi
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
rc_flags="${rc_flags} ${ifn}"
Make use of the dhclient script. This will bring up/down dhcp interfaces. Approved by: markm (mentor)
2003-04-18 17:53:02 +00:00
}
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names.
2001-06-16 07:16:14 +00:00
Support code for the OpenBSD dhclient. This significantly changes the way interfaces are configured. Some key points: - At startup, all interfaces are configured through /etc/rc.d/netif. - ifconfig_<if> variables my now mix real ifconfig commands the with DHCP and WPA directives. For example, this allows media configuration prior to running dhclient. - /etc/rc.d/dhclient is not run at startup except by netif to start dhclient on specific interfaces. - /etc/pccard_ether calls "/etc/rc.d/netif start <if>" to do most of it's work. - /etc/pccard_ether no longer takes additional arguments to pass to ifconfig. Instead, ifconfig_<if> variables are now honored in favor of pccard_ifconfig when available. - /etc/pccard_ether will only run on interfaces specified in removable_interfaces, even if pccard_ifconfig is set.
2005-06-07 04:49:12 +00:00
load_rc_config $name
Pull in /etc/rc.conf.d/network so that ifconfig_<if> variables can be set there. This is required for consistency with /etc/rc.d/netif. PR: conf/103893 Submitted by: Nick Hibma <nick at anywi.com> MFC after: 3 days
2006-10-02 18:50:58 +00:00
load_rc_config network
Implement individual operations on static and dhcp interfaces. Previously network interfaces could only be turned on and off as a group (all static interfaces or all dhcp interfaces). When used to start the interface a 'long form' ifconfig output is used to show the status of the interface, but when stopping an interface the script will simply output the name of the interface. This is simply my personal preference. Hopefully as this functionality matures we can stabilize on a prefered form of output for these scripts. A stop command to the dhclient script now explicitly releases the dhcp lease. Behaviour at system shutdown; however, is unchanged since dhclient is not, by default, run at that time. The client will not release its lease at shutdown.
2003-06-29 05:34:41 +00:00
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
if [ -z $ifn ] ; then
# only complain if a command was specified but no interface
if [ -n "$1" ] ; then
Fix handling of rc_force in /etc/rc.d/dhclient Variable 'rc_force' is accessible only at the time of rc_run_command, so it can't be examined from the script's main code. Spotted by: hrs Reviewed by: hrs, des Approved by: des MFC after: 2 weeks
2011-10-28 06:03:38 +00:00
err 1 "$0: no interface specified"
Make dhclient use a pid file. Modify the rc script accordingly; while there, clean it up and add some error checks. Glanced at by: brooks@ MFC after: 3 weeks
2011-10-13 17:20:45 +00:00
fi
Implement individual operations on static and dhcp interfaces. Previously network interfaces could only be turned on and off as a group (all static interfaces or all dhcp interfaces). When used to start the interface a 'long form' ifconfig output is used to show the status of the interface, but when stopping an interface the script will simply output the name of the interface. This is simply my personal preference. Hopefully as this functionality matures we can stabilize on a prefered form of output for these scripts. A stop command to the dhclient script now explicitly releases the dhcp lease. Behaviour at system shutdown; however, is unchanged since dhclient is not, by default, run at that time. The client will not release its lease at shutdown.
2003-06-29 05:34:41 +00:00
fi
Import the NetBSD 1.5 RC system. Note that `rc' and `rc.shutdown' could not be imported because we already have files with those names.
2001-06-16 07:16:14 +00:00
run_rc_command "$1"
Reference in New Issue Copy Permalink