Tim Kientzle wrote: > > We could modify rc.network by adding a & to the dhclient row ... > > Simply running dhclient in the background is probably not a > great idea, since that will allow the boot to continue and > any network programs/daemons will try to start before the > network gets initialized. (Even if your FreesBIE distro > isn't running any network daemons, someone else will start > from your work and try to add them... )
I have to agree with this. This is actually a side effect of a design issue that no one has addresses (yet), which is that sockets get bound to IP addresses, instead of getting bound to interfaces. If they were bound to the interface, then it would not matter when the IP address changed out from under it (e.g. when it finally got a lease, or when the lease changed it's IP out from under it). Mostly, this is a problem with cached data (in this case, the IP address, but, e.g. with sendmail, also with cached information derived from the IP address -- i.e. sendmail ansers connect requests with a greeting using it's canonical name, which came from a reverse lookup of the name based on a getnamebyaddr() of the IP address of the primary interface to which the listening socket is bound). > > Can an optional flag be added (configurable in rc.conf)? > > Not to CURRENT, no. CURRENT has adopted rcNG, for which no such > easy workaround is possible. (Short of putting all the > network startup back into a single script file.... ;-( Really, we need to add an "interface" socket type, so that rather than a bind to an IP address, the bind is to the interface, and uses any IP address that happens to occur on the interface... at any point in time. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
