FreeLists / openbeosnetteam / [openbeosnetteam] Re: new if_flag IFF_CONNECTED

["Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>]

> > In this case, I partialy agree :-)
> > I thought you were planning to expand ifconfig code to be able to *
> > delete* the ppp interface.
> > Anyway, and once again, bring up and down an interface is more a 
> > enable
> > /disable thing than a create/delete.
> > It allow the user to disable temporaly a specific interface, without 
> > *
> > deleting* it.
> > I'm not sure the ppp interfaces should be deleted when they're 
> > turning 
> > IFF_UP off... just keep them disabled, but there.
> > 
> > Keep the add/remove "ppp<n>" interfaces into ppp interfaces manager, 
> > via pppdial, and ifconfig to allow user to disable/re-enable them as 
> > he 
> > want...

Why could a user want to do that? Did you ever do that? BONE does it like I 
suggested. Actually, all PPP implementations (I saw) do it like that and I 
think that is good.

> I think PPP should never delete itself, it also shouldn't go up 
> automatically when created (only if auto dial is enabled). It should be 
> told to go online separately by setting the IFF_UP flag (but of course, 
> pppdial should do that, too).
> But ifconfig should be able to do it as well, as it can with other 
> interfaces as well.
> I don't see why PPP is anything special in this regard.

Why should the interface not go up immediately (except for dial-on-demand)? I 
mean, we must ask ourselves what use this would have and to the user it would 
have no use at all.
IMHO, the user wants to do one of these:
1) dial automatically when needed
2) ask me before dialing
3) let me dial manually

1) and 2) are managed by dial-on-demand. Interfaces for 3) are not created at 
all. Does the user bother if the interface goes up when it is created? An app 
that wants to dial later SHOULD dial later.


Could you both please tell me: when is all that needed? I cannot think of any 
case. It will only make more work.

Waldemar