Re: STEP 2, fixing dhclient behaviour with multiple interfaces

From: Robert Watson (rwatson_at_freebsd.org)
Date: 07/30/03

  • Next message: Tobias Roth: "sh coredump through rc.subr" 
    Date: Wed, 30 Jul 2003 09:49:08 -0400 (EDT)
To: Terry Lambert <tlambert2@mindspring.com>

    On Tue, 29 Jul 2003, Terry Lambert wrote:

    > This is part of the problem. The other parts are that this is really
    > networking code, and should be a separate thing, if possible, and, as
    > Martin just pointed out, the OMAPI stuff is not really cooked yet.

    Hence the notion of a neteventd -- I don't really mind what container it's
    in, as long as its structured around the network-centric pieces.

    > It's really a lot easier the process a small list of events in dhacpd as
    > a result of a kqueue or kqueue/select combo, if you want to avoid
    > rewriting as much code as humanly possible, and still be able to pull
    > this feature out of the project.

    Absolutely agreed. If OMAPI is working well, that may well provide a lot
    of what we want. One benefit to central management of the network
    configuration would be that we'd get things like GUI control and profiles
    a lot more easily.

    > I still haven't been able to repeat your test; are you sure you are
    > listening on a routing socket for the configuration change events?
    > Maybe I'm doing something silly with my dumb little test program that
    > you aren't doing with yours? I'm not seeing my Linksys my 3COM
    > interfaces showing up and disappearing as kevents, but they are
    > definitely still being seen by the laptop. Maybe it's my local hacks to
    > make it work at all (it's an older Sony VAIO PCG-XG29).

    I can't speak to your configuration, but I can describe mine :-). I've
    tested two different situations with "route monitor" creation and removal
    of virtual interfaces (in this case, vlan interfaces), and physical
    interfaces (in this case, my wi0 card in my notebook). Both appear to be
    generating proper notifications during arrival and departure. The only
    events that I expected to see, but didn't, were IPv6 link layer address
    arrival and departure. I ran these tests with 5.0-CURRENT from around
    July 3, but I seem to recall seeing this work properly previously. I
    don't have any RELENG_4 boxes with removable physical interfaces at this
    point.

    Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
    robert@fledge.watson.org Network Associates Laboratories

    _______________________________________________
    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: Tobias Roth: "sh coredump through rc.subr"

    Relevant Pages

    • Re: Part 2; COM issues
      ... The COM configuration defines how the object ... It is that composition of behavior that I ... The fact that a networking service is ... another spin on this lies in the nature of interfaces. ...
      (comp.object)
    • Re: Problem with Realtek 8139(It sends ARP but the reply is lost)
      ... Dynamic Configuration of IPv4 Link-Local Addresses ... To participate in wide-area IP networking, ... configured with IP addresses for its interfaces, ... Dynamic Host Configuration Protocol server. ...
      (comp.os.linux.networking)
    • Re: [PATCH 0/1] IPN: Inter Process Networking
      ... exiting tap interfaces would seem to do everything you are looking for. ... So, you say, it's a networking issue and we could live with tun/tap. ... virtualization, but that's another topic). ... in doing this you started by duplicating the kernel networking functionality into userspace and are running into performance problems so trying to push this into the kernel to reduce context switches. ...
      (Linux-Kernel)
    • [BUG][debian-2.6.20-1-686] bridging + vlans + "vconfig rem" == stuck kernel
      ... I've managed to fairly reliably trigger a deadlock in some portion of the linux networking code on my Debian test box. ... I'm pretty sure that it's a race condition of some sort as it doesn't trigger if I ifdown the interfaces one by one, but if I run "ifdown -a" then it triggers halfway through reliably. ... Just for a bit of background on why this is so complex: When I get this networking problem sorted out I'm going to set up heartbeat and a dummy "world1" interface with a shared MAC which is added to the "world" bridge when the current system is the DHCP-client master. ...
      (Linux-Kernel)
    • Re: [PATCH 0/1] IPN: Inter Process Networking
      ... exiting tap interfaces would seem to do everything you are looking for. ... So, you say, it's a networking issue and we could live with tun/tap. ... at present, dealing with tun/tap, bridges, ... virtualization, but that's another topic). ...
      (Linux-Kernel)