[openbeosnetteam] Re: new if_flag IFF_CONNECTED

> > the pppdial app is finished and the PPPoE module should be working in 
> > the next few days.
> 
> Nice progress!

Thank you!

> Isn't the purpose of IFF_RUNNING to say "it's running", when IFF_UP say 
> "this interface is ready to be USED" ?
> Why not use:
> - IFF_UP to say the "ppp0" interface is enable
> - IFF_RUNNING to say the "ppp0" interface is running/opened/connected 
> to some peer...
> 
> I don't see any need here to add another interface flag...

Okay, then I misunderstood how our netstack handles the connections. I will 
correct that.

> Please, interfaces creation and destruction, when this isn't managed 
> fully automaticly like with loopback and generic ethernet interfaces, 
> should be done in the same place. 
> 
> As I can't think how ifconfig could know how to create/delete correctly 
> a new PPP interface, I better like 
> that only pppdial tool deal with these tasks.

ifconfig knows how to delete the interface. It just tries to set the IFF_DOWN 
flag on the interface. The rest is done by the module.

> However, ifconfig isn't about creating/deleting interfaces but 
> configuring/monitoring them...
> So, even if a "ppp0" interface is not connected/running yet, she should 
> show up in ifconfig interfaces list, as that's a existing interface in 
> the stack...
> 
> So, sorry guys, I disagree with both of you ;-)

Maybe we can discuss that. ;)
I do not see why we need the extra code in pppdial to delete an interface as 
this can be perfectly done by the interface module. Why should we not reuse 
ifconfig for this case while creating can be done by pppdial?
Bringing an interface down is a normal action for ifconfig. That PPP interfaces 
are deleted when they are down is just a side-effect. ;)

Waldemar

Other related posts: