[openbeosnetteam] Re: general or PPP ideas

> > So, here is a short answer:
> > You must tell the IP module which ip address it should use, so you 
> > need
> > some kind of settings!
> > I do not want to use _files_. I want to use the structures. Just 
> > the
> > Nathan's attributes idea and adapt it to settings for modules. IP 
> > would
> > use the structure to save nameservers and the ip-address and the 
> > netmask.
> > I do not want to use settings to save protocol ids! 
> 
> Okay, I think I understand better now:
> A generic way to exchange "settings", or attributs, between all 
> network modules.
> By attaching them to a net packet or a protocols "stack" connection, 
> completed 
> and used by each modules who require it.

The net packet and net interface attributes ideas are separate. Packet 
attributes would contain the header information, pre-parsed. Interface 
attributes would contain settings for that interface.

> > The PPP module will know which authentication method to use
> > and which protocols to support. 
> 
> Can't it be made automaticly discovered?
> I'm not a PPP expert, even far from it even, but can't you discover 
> what 
> kind of authentification protocols (CHAP or PAP, is that them?) to 
> use or are 
> supported by PPP server? Trying first CHAP, and fall to PAP if it 
> doesn't work?

Yes. LCP tells you which to use. You don't have a choice in the matter 
(usually -- some servers allow you to reject CHAP and use PAP instead). 
*nix configures PPP the bad way... it is designed to completely auto-
configure.

> BTW, sorry if I sounds too newbie on PPP... ;-)
> Does someone around have a better PPP technical documentation than 
> just RFCs?
> URLs? PDF(s)?

The RFCs are both fairly readable and complete. You just have to look 
up all the addenda to get a complete picture.
-Nathan

Other related posts: