[openbeosnetteam] Re: libbind.so status
- From: "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>
- To: "OpenBeOS Networking" <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Thu, 15 Apr 2004 19:57:56 +0200
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. :)
Unfortunately, there are more problems to solve:
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).
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).
Let's make our netstack a complete BONE replacement until Waltercon (stability
does not matter, only functionality-wise).
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.
Some kind of simple tcpdump would be useful...but you can learn reading hex
dumps of IP packets very quickly. ;)
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.
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? 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.
Bye,
Waldemar
- Follow-Ups:
- [openbeosnetteam] Re: libbind.so status
- From: Philippe Houdoin
- References:
- [openbeosnetteam] Re: libbind.so status
- From: Axel Dörfler
- [openbeosnetteam] Re: libbind.so status
- From: Waldemar Kornewald
- [openbeosnetteam] Re: libbind.so status
- From: Waldemar Kornewald
Other related posts:
- » [openbeosnetteam] libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- » [openbeosnetteam] Re: libbind.so status
- [openbeosnetteam] Re: libbind.so status
- From: Philippe Houdoin
- [openbeosnetteam] Re: libbind.so status
- From: Axel Dörfler
- [openbeosnetteam] Re: libbind.so status
- From: Waldemar Kornewald
- [openbeosnetteam] Re: libbind.so status
- From: Waldemar Kornewald