Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosnetteam] || [Date Prev] [10-2003 Date Index] [Date Next] || [Thread Prev] [10-2003 Thread Index] [Thread Next]

[openbeosnetteam] Re: new if_flag IFF_CONNECTED

  • From: "Philippe Houdoin" <philippe.houdoin@xxxxxxx>
  • To: openbeosnetteam@xxxxxxxxxxxxx
  • Date: Mon, 20 Oct 2003 22:09:23 GMT
> > 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. ;)

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...

What do you think?

- Philippe

--
Fortune Cookie Says:

There is no substitute for good manners, except, perhaps, fast
reflexes.





[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.