Re: Dependency between interfaces

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 10/20/05

  • Next message: Volker: "IPSec session stalls" 
    Date: Thu, 20 Oct 2005 13:25:44 -0700
To: "Wojciech A. Koszek" <dunstan@freebsd.czest.pl>

    On Thu, Oct 20, 2005 at 08:20:34PM +0000, Wojciech A. Koszek wrote:
    > Hello,
    >
    > Is EVENTHANDLER(9) proper way of notification for standalone driver about
    > network interface attach/detach operations? I've met simple problem in
    > ef(4), which causes machine freeze in following situation: load NIC driver
    > -> load if_ef -> unload NIC driver -> some activity with interface.
    > Althought driver of network interface no longer exists, if_ef does not know
    > about it and continues it's operation.
    >
    > I've seen similar situation for example in ng_fec(4): piece of code needs to
    > call some cleanup routines in order to keep pointers in valid state. I think
    > this situation is almost the same like this current in if_bridge(4). Just
    > repeat situation described above for ef(4), but with if_bridge(4).

    It looks like you could hook into the ifnet_departure_event pretty
    easily. The one gotcha is that it's called during interface renames so
    you need to consider that possibility.

    -- Brooks 

    -- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

  • Next message: Volker: "IPSec session stalls"

    Relevant Pages

    • Re: Dependency between interfaces
      ... > Is EVENTHANDLERproper way of notification for standalone driver about ... > network interface attach/detach operations? ... which causes machine freeze in following situation: load NIC driver ... > Althought driver of network interface no longer exists, ...
      (freebsd-net)
    • Dependency between interfaces
      ... Is EVENTHANDLERproper way of notification for standalone driver about ... network interface attach/detach operations? ... which causes machine freeze in following situation: ... Althought driver of network interface no longer exists, ...
      (freebsd-net)
    • Re: incorrect ping(8) interval with powerd(8)
      ... network interface uses the bgedriver. ... Jeremie Le Hen ... < jeremie at le-hen dot org>< ttz at chchile dot org> ...
      (freebsd-current)
    • Re: incorrect ping(8) interval with powerd(8)
      ... I've seen ARP take a while... ... Yes, I ran this test multiple times, and I almost get always this same ... network interface uses the bgedriver. ...
      (freebsd-current)
    • Re: 7-STABLE not seeing second em interface on supermicro mb
      ... supermicro motherboard - it works fine except that it's not seeing the second network interface - is there a magic incantation to make this work? ... The only word from the em driver is this ... ifconfig doesn't show anything other than em0 and lo0 ... Turns out to be a hardware problem - when checking the jumpers I discovered a transistor on the MB next to the failed nic that is too hot to touch - new MB is on the way from Silicon Mechanics ...
      (freebsd-stable)