[Top] [All Lists]

An interface goes away while a socket is bound to it..what happens?

To: "'netdev@xxxxxxxxxxx'" <netdev@xxxxxxxxxxx>
Subject: An interface goes away while a socket is bound to it..what happens?
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Mon, 17 Jan 2005 19:28:27 -0800
Organization: Candela Technologies
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041020
I've been playing around with multi-link PPP interfaces, and
have noticed something strange (kernel 2.6.9+hacks, pppd 2.4.1b2 ).

My application binds tight to the local IP address and the
interface.  In the instance tested, I was using UDP traffic
but TCP seems to behave the same.

Suppose I am pulling the T1 interfaces to cause
a failover:   If I pull both at once for a few seconds and then
replace them, ppp0 will dissappear, and then quickly be rebuilt.

My application discovers interfaces based on their name, by
parsing /proc/net/dev every 30 seconds or so.  Often, it does not
detect that the interface ever went away (and came back), so it
cannot take any evasive action.

The interesting part to me is that I do not appearantly see any errors
while continuing to send UDP packets on the socket that was bound to the
original ppp0 interface, and yet no packets are ever routed over the new
ppp0 interface.  I would expect it to either fail the write, or to just
magically keep working.

So first:  Is this happily-write-down-a-black-hole issue a bug?

and:  What is a good way to discover the coming and going of interfaces
   as it happens?  (I looked around Netlink, but it does not appear to do


Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc

<Prev in Thread] Current Thread [Next in Thread>