Date: Thu, 30 Sep 2010 09:57:52 -0400 From: Ed Maste <emaste@freebsd.org> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Doug Barton <dougb@FreeBSD.org>, freebsd-rc@freebsd.org Subject: Re: Wait for carrier in /etc/rc.d/defaultroute Message-ID: <20100930135752.GA81590@sandvine.com> In-Reply-To: <20100929100100.GA83642@icarus.home.lan> References: <20100925000435.GA62501@sandvine.com> <4CA15FC8.8010106@FreeBSD.org> <20100929074628.GA83194@icarus.home.lan> <20100929100100.GA83642@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 29, 2010 at 03:01:00AM -0700, Jeremy Chadwick wrote: > > Ack, I forgot all about this (and despite recommending the script to > > someone on the lists a couple weeks ago)! The script Doug's referring > > to is available below, and should be placed into /usr/local/etc/rc.d (be > > sure to chmod 755/555 it as well): > > > > http://jdc.parodius.com/freebsd/netwait > > > > Example usage in /etc/rc.conf: > > > > netwait_enable="yes" > > netwait_ip="4.2.2.1 4.2.2.2" > > netwait_if="em0" > > netwait_timeout="15" I think the approach in this script is overall reasonable, but one thing I prefer about the current /etc/rc.d/defaultroute is that it doesn't need to be configured with a specific IP address, so it can "just work" out of the box. Jeremy, was your primary motivation for netwait DHCP, or are there other bootup issues you had to address with it as well? What do you think about combining the two, so that we'd have the current functionality if DHCP is in use and netwait_ip is not set, and the ping check if netwait_ip is set (regardless of the DHCP setting)? I think "netwait" is a more descriptive name than "defaultroute." -Ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100930135752.GA81590>