FreeLists / openbeosnetteam / [openbeosnetteam] Re: libbind.so status

["Brennan Cleveland" <warriorspot@xxxxxxxxxxxxx>]

Waldemar,

>Hi,
>libbind.so works now as far as I can see. Our UDP module did not set
>the address family for the sockaddr passed to recvfrom(). Our old
>BIND seems to not care about that value. :)

Cool.

>Unfortunately, there are more problems to solve:

No there aren't! ;)

>Ping resolved the host name correctly, but then it tries to send an
>IP packet with most values set to zero (version and header length are
>both zero, for example, although they should be 4 and 5,
>respectively).

What problem is this causing?  Does it send one successful ping and
then die? I tested ping fairly thoroughly, I will have to do a CVS
update and re-test. 

>I'd bet we have some places in our source that use immediate values
>instead of constants and after I changed our headers to be more
>BONE-like (for example: our shutdown() constants were different from
>ours) they are wrong, too. The route bin command used shutdown(sock,
>0), although it should have been shutdown(sock, SHUTDOWN_RECV).

>Mozilla wants to set SO_NONBLOCK on the HTTP socket. It does not work
>because we do not have support for it. :(
>Any volunteers to add this sockopt? No, don't count on me until PPP
>is finished and documented (which is not too soon ;).
>The BSD netstack could help us here (since we have a BSD port).

I would love to do it, but I'm unsure I can honestly commit that time
:(...

>Let's make our netstack a complete BONE replacement until Waltercon
>(stability does not matter, only functionality-wise).

Do you mean make it a BONE replacement BY WalterCon?  I think it's a
good idea to establish deadlines... 

>Every time I put such a cool task up you run away like Philippe. ;)
>Come on, get your hands dirty! ;) It is just a matter of running bdb
>with a debug version of our netstack and libsocket.so and finding out
>where something wrong happens.

Maybe you could write up a simple doc to get people started?  How to
compile the stack w/debug symbols, how to use the simple bdb
commands, and so on.  Also, I'm assuming you are testing against the
user-space stack?

>Some kind of simple tcpdump would be useful...but you can learn
>reading hex dumps of IP packets very quickly. ;)

tcpdump is good, I also use Ethereal on my Linux box to capture
packets real time.

>Here are some testing tasks. Brennen, could you please do some of
>that?
>- Does a BONE ftp client work now?
>- A list of client and server BONE apps that run would be useful. If
>we can get the source for those apps it would help us to locate our
>bugs more easily.

I will procure BONE, and do this testing.  Maybe someone can point me
to a good place to get it?

>Philippe, where are you? I thought you have time now. This team needs
>some more active people who test and fix.
>And are we not still waiting for a working BNetEndpoint (but it is
>not a high-priority task)?
>Do we need some more docs? 

I've got a few docs I haven't released to the wild yet, maybe I'll
polish them up and post them on my site.

>Are there any lurkers on this list that
>could do something, but don't know how to get started? If our docs
>are not good enough or missing just tell us what problems you have.
>We will help you.

So, here's what I will do in the next few days:

Install FreeBSD on one of my test boxes
Obtain and install BONE on another of my test boxes
Update CVS, recompile
re-run tests on all OBOS net utilities
Try running various BONE apps 
* drink coffee
Try to figure out what is up with 'route show' (this has me stumped)
* discover the meaning of life


>Bye,
>Waldemar

Brennan