Re: IFF_RUNNING support for ppp interfaces?
James Carlson <carlsonj <at> workingcode.com>
2009-02-09 15:17:32 GMT
Joakim Tjernlund writes:
> James Carlson <carlsonj <at> workingcode.com> wrote on 09/02/2009 13:10:45:
> > I don't think that's a problem with the current code. If you do see a
> > problem here, then I think it'd be helpful to have the problem itself
> > described in some detail, rather than focussing on what solution you'd
> > like to see implemented.
>
> I should have been clearer. I think it is a bit rude to tear down/delete
> the ppp interface when it looses a link. Compare with ethernet, when the
> cable
> is pulled you still see the I/F but the running status is gone so you get
> a clue
> to what is wrong. For ppp the I/F is just deleted and you can only guess
> the cause,
> or start looking at logs to find out what happened.
Ah, this is a much higher-level issue, and is only slightly related to
IFF_RUNNING.
The real issue is that (a) there are at least two different "kinds" of
PPP links, (b) the identity of the IP-level object doesn't say
anything about the physical entity, and (c) a bit about pppd design
itself.
With Ethernet, you (generally) know that a "net0" interface is
connected to a single hardware instance, and that IFF_RUNNING
transitions represent changes in the status of that one instance.
With PPP, things are different. First of all, to point (a), there are
different kinds of PPP links that we have no good way of
(Continue reading)