Ctrl-c abort of dhclient during rc.d start aborts all network configuration

From: Robert Watson (rwatson_at_FreeBSD.org)
Date: 08/31/05

  • Next message: Robert Watson: "Re: Application layer firewall on FreeBSD, is it possible ?" 
    Date: Wed, 31 Aug 2005 12:10:44 +0100 (BST)
To: current@FreeBSD.org

    I believe this is related to the new dhclient -- when I run my notebook
    disconnected from the network, the boot pauses for about 15-20 seconds
    waiting for a link on xl0. Being impatient when booting in airports just
    before my flight, I like to hit Ctrl-C and abort it, since I know that
    there will be no link. In the old world order, this was fine, dhclient
    was simply killed and all was good. In the new world order, it kills all
    of the netif startup script, and for some reason (ordering related,
    presumably), this prevents 127.0.0.1 from being configured on lo0, which
    causes a number of applications to die, since 0.0.0.0 cannot be bound. It
    sounds like a couple of things are unfortunate here:

    (1) It would be good to configure lo0 first.
    (2) If a dhclient is ctrl-c'd, it would be nice if the rest of the network
         configuration continued.

    The printing of '.'s in dhclient is also a bit excessive.

    Robert N M Watson
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Robert Watson: "Re: Application layer firewall on FreeBSD, is it possible ?"

    Relevant Pages

    • Re: dhclient and wpa_supplicant
      ... Also dhclient processes link ... > media parameters but it was complicated and still routinely failed ... > appropriate network (while dhclient had to scan once for each possible ... Drivers that bypass the net80211 layer for some or all of this ...
      (freebsd-current)
    • Re: dhclient and wpa_supplicant
      ... The ndis driver shows nothing in the log that indicates it hooks up ... layer causing applications written to the common api to not work. ... The issue with dhclient using dhclient.conf to set wireless parameters ... appropriate network (while dhclient had to scan once for each possible ...
      (freebsd-current)
    • Re: dhclient and wpa_supplicant
      ... >>My biggest outstanding complaint is when booting with a wired network ... > which interface gets the default route. ... Perhaps dhclient needs to be aware ... >>Boot once in the presence of a wireless network. ...
      (freebsd-current)
    • Re: Binding dhclient to a particular network interface
      ... The network setup on my machine is working correctly. ... network card has a fixed IP address, ... Note that dhclient generally runs as a daemon because it has to handle lease ... However, it is listening on all interfaces, ...
      (freebsd-questions)
    • Re: New User- Network Problem
      ... It had something to do with the network driver being loaded when dhclient tries to acquire an IP address from. ... I worked around this issue by inserting a 'sleep 120' at the end of /etc/init.d/networking so that the second attempt of dhclient occurs before the networking script returns. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
      (Debian-User)