FreeLists / openbeosnetteam / [openbeosnetteam] Re: Some quick questions

[Oliver Tappe <openbeos@xxxxxxxxxxxxxxx>]

On 2006-05-30 at 17:09:54 [+0200], 
Philippe Houdoin <philippe.houdoin@xxxxxxx> wrote:
> 
> Reproductible here too. Something break as soon as you close a socket, or
> something along this path. I never find time to follow the white rabbit to 
> see
> how deep is his dark hole... hum, I mean how dark is the issue here.

I'll put my hand down that hole during the next few days >;o)

[ 8< ]

Many thanks for your guidance through the building of the userland tools, 
using that info, I now have it running here.

> Anyway:
> 
> 1) First, build the net_server_driver
> 
> $ cd src/add-ons/kernel/drivers/net/stack
> $ jam net_server_driver

This worked.

> 2) Second, build the userland net_stack_tester app and the network stack 
> modules in their userland version (aka plain add-ons, not kernel add-ons):
> 
> $ cd src/tests/add-ons/kernel/network
> $ jam

This didn't work, but now I've added the legacy (and posix) headers, it does.

> It will build the app locally (stupid me!), named net_stack_tester, and all
> major netstack components will be placed under
> generated/objects/haiku/x86/release/tests/add-ons/kernel/network/.
> 
> You should create a symlink near your net_stack_tester so the userland 
> modules emulation could find and load them:
> 
> $ mkdir add-ons
> $ cd add-ons
> $ ln -s 
> ...../generated/objects/haiku/x86/release/tests/add-ons/kernel/network
> obos_network

Yep, I manually recreated the required subfolder layout, but I'd like to 
create a new jam-rule to do that, as it's a bit tedious, otherwise...

> 3) first build libsocket.so, libbind.so & usual net userland tools.
> 
> 4) Before running them:
> - start the userland stack, by launching net_stack_tester
> - Tell libsocket.so to use the net_server_driver, not, the default
> net_stack_driver to talk with the network stack:
> 
>   $ export NET_STACK_DRIVER=/dev/net/server
> 
> - run your tool(s)

I had to create a 'lib'-folder next to each tool I tested, as otherwise, it 
would try to link to BONE's libsocket.so. After I pointed tools to the right 
lib, ifconfig and route worked, but ping didn't (missing icmp). I'll 
investigate about that tomorrow.

> 5) Come back here in hurry and yiel at me that these instructions doesn't 
> work at all.

No yelling, just praise >:o)

cheers,
        Oliver