[openbeosnetteam] Progress update...

Progress! Well, on my machine as I can't be bothered to go through and sync
up all of the cvs tonight, is there. We have a route module that allows us
to also have the route app (though it doesn't yet seem to work as it should)
and see a nice print of the routes we have available.

To get this far a LOT of stuff has been added to libnet and there's more
needed (though we're about 75% of the way there I'd say). We need more
testing of a lot of the stuff and some pieces require TCP before we can go
anywhere...

We're also upgrading libnet to have things like inet_pton which are designed
to work better with IPv6 and other protocols.

I'm away for a few days so will try to add some more to CVS when I get back.
There is a lot more to do yet, but we're making solid progress, especially
if Philippe or someone else can figure out how to get select actually
working and not simply calling the hooks. If we can figure out how to get
the calls working (and what return values etc are needed) then it'll take me
about 10 mins to add the functions to the core that deal with them :) Yes,
that quick! Presently the select call never times out...

It also looks like we'll need (or it'd be cool to have anyways) a
/dev/random driver. This is really needed for all sorts of things and if we
can come up with a suitable device we'll be doing a really big service for
the beos community. I'd like to think we could make it a real device as well
as this shouldn't be as hard as it first appears... Bruno has some code from
openssl that may make this possible.

Next items on my agenda...

sync up tree and add route module
netstat app
raw sockets module
tcp module

Anyone else want to jump in with anything?

We should also get back to the topic of what the preferences app should look
like and how it should work...

How about this for a crazy idea? We allow each module (ipv4, ipv6 etc etc)
to have a "configuration" module in addition to the "services" modules we
have already. This basically just provides hooks for things like displaying
a tab in the preferences app that allows control of it's details and
functions for ifconfig that allow it to configure them as well. this way
when we add a protocol we should be able to remove a lot of the dependencies
we have within core and certain other apps. I'm guessing ipv4 will be a
given so it'll be other protocols that really need this facility.
Thoughts?

Anyway, have a good easter!

david

Other related posts: