FreeLists / openbeosnetteam / [openbeosnetteam] Progress Update...

["David Reid" <dreid@xxxxxxxxxxxx>]

Well, it's Monday evening and I've been home over 24 hours, so here's an
update...

[I had a relative go into hospital with a stroke over the weekend so my mind
isn't exactly focused on adding lots of code at the moment...]

Well, I finally added the route module, so you can now have routing sockets
and issue route requests via them. This also allows you to build the route
command line app and then see output somewhat like this...

$ route show
Routing tables

Internet:
Destination      Gateway            Flags
127.0.0.1        127.0.0.1          UH
192.168.0.0      192.168.0.133      U
$ route add default 192.168.0.1
add net default: gateway 192.168.0.1
$ route show
Routing tables

Internet:
Destination      Gateway            Flags
default          192.168.0.1        UG
127.0.0.1        127.0.0.1          UH
192.168.0.0      192.168.0.133      U

$ ~/openbeos/net_kit/source/apps/ifconfig/ifconfig -a
tulip0: flags=39<UP,RUNNING,MULTICAST,BROADCAST> mtu 1500
        inet 192.168.0.133 netmask 0xffffff00 broadcast 192.168.0.255
loop0: flags=119<UP,RUNNING,MULTICAST,LOOPBACK> mtu 16384
        inet 127.0.0.1 netmask 0xff000000

There were a lot of changes required to get this working, but there it is.

So, those who build and install the kernel version now get

- a /dev/net./socket they can use
- a libnet.so that can do a lot of the things it needs to
- UDP support (basic still)
- ifconfig command line app to control the interfaces (doesn't yet do
everything)
- route app that should allow things like gateways to be set.

Not too bad, but still a long way to go!

We presently have pseudo drivers for the loopback, but I think we need
others, such as slip and ppp. However, what do people here want?

So, please respond telling us what you'd like and what hardware you have.
Also you should indicate whether you've actually got the code, tried to
build it and if you're willing to do this in order to test anything written!
yes, just like a true beta program!

We should also think about how we want to support things like ppp and dial
on demand.

Unless people object then this is a list of things we should try to do in
the next week or so...

- get some form of agreement on our preferences app and get work going on
that
- add raw sockets (gets us ping/traceroute)
 and then (- add ping/traceroute!)
- figure out how to support icmp error messages
- figure out how to use select via ioctl (Philippe???)
- start adding tcp support
- draw up a new roadmap!

Well, I'll volunteer to do some of the above, namely the tcp support and raw
sockets! Anyone else want to step up?

david