[openbeosnetteam] Re: general or PPP ideas

> > AFAIK, each used protocol (IP, IPX, etc.) must be specified and
> > configured
> > for each link (Ethernet, PPP). How is this done at the moment? So,
> > there is
> > no possibility to add a protocol by just adding the driver. It must
> > be
> > configured for each device. This means that we need a good
> > configuration
> > scheme.
> > I think that it would be cool to use a structure to describe a
> > connection
> > (at least for PPP).
> >
> > The structure describes which modules should be loaded and it defines
> > substructures to configure each module. This is useful especially for
> > our
> > modular design (like I want to implement it for PPP).
> > The syntax should be the same as for driver settings. The settings
> > code
> > could be reused and with our new OBOS implementation we can even save
> > them
> > to disk or modify them easily.
>
> Alternately, we could simply assign attributes to the interfaces (ip
> address, etc.). The various protocols, in asking for all available,
> say, ethernet interfaces, could read any settings pertaining to them
> from these nodes. Global protocol/interface specific settings could be
> written to the node at run time of the net stack from a settings file,
> using something like Peter Folk's NodeMessage.

I would like to use attributes for this, but there is no API for this at the
moment and it is no problem to change PPP when we get this API. In addition
to changing PPP we should change our whole stack to use attributes then.
At first I want to get PPP running. After that I should have enough
experience with that protocol to change/rewrite/extend it to make it a good
PPP implementation

Waldemar

Other related posts: