[openbeosnetteam] Re: Testing the stack

Hi Brennan,

> As I stated earlier today, I've been away from OpenBeOS since June. 
> I am now going about setting up my test environment (again) for our
> stack.  I have a few questions:
> 
> 1.  Are these manual instructions still a valid way to install the
> stack (w/o using jam install-networking)

You can use jam install-networking.
The net_stack_driver will not be installed anymore. Philippe, I forgot why you 
did that.

The bin files will be copied into current/tests/kit/net (in your OBOS CVS tree) 
and the libraries into the subfolder lib. You can copy other apps into that 
folder and they will automatically use our netstack.
There is no need to install it manually.
Do not forget to disable the bone_api_driver (renaming the network modules 
folder into network.bone should work, too).

There was a problem with the network adapter drivers (RTL8139, etc.) as they 
were installed automatically, too. This conflicted with the already installed 
drivers. I think it is solved now, but better you make sure that this is no 
problem anymore.

The userland test stack did not work very well (at least for me).

> f) Test the stack
> 
> You should free one of your /dev/net/*/0 network card (by disable in 
> BONEyard, or by disabling in Network for net_server)
> Then, run the ifconfig tool from Terminal to see (and start) the
> stack 
> detected interface(s)
> Last, play with ping, arp, traceroute, etc...
> </cut>

I think that BONEyard can stay enabled if you disable bone_api_driver.

> I also properly copied our lib*.so files into a ./lib directory in
> the same directory that I have our binaries (ping and so on)
> 
> The above seems to work on one box and not on another. 

Probably it is the problem mentioned in (2)...

> 2)  Does my test machine have to use an RTL8139 based nic?
> I am testing on a machine w/a BeOS support 3COM 3C509 nic, and the
> other machine has an RTL8139.  The 3COM machine fails every command
> with some variation of "icmp: unknown protocol" while the 8139
> machine is able to ping other hosts using our stack.  They were set
> up using the instructons above.

Oh, there is a problem with your /etc/protocols file. Philippe wrote this some 
time ago on the mailing list:

Check you have a /etc/protocols file on your system. 
It should contains this line: 

icmp    1       ICMP    # internet control message protocol 

If you don't have any /etc/protocols file, then grab one from a Unix 
system, or 
save this text into a new /etc/protocols file on your system: 

# 
# Internet (IP) protocols 
# 
ip      0       IP      # internet protocol, pseudo protocol number 
icmp    1       ICMP    # internet control message protocol 
ggp     3       GGP     # gateway-gateway protocol 
tcp     6       TCP     # transmission control protocol 
pup     12      PUP     # PARC universal packet protocol 
udp     17      UDP     # user datagram protocol 


That did it for me.

> 3)  Does the jam install-networking script set up everything needed
> to test our stack?  It doesn't copy the net_stack_driver and
> net_server_driver to ../config/add-ons/kernel/drivers/bin or create
> the symlinks to those files from
> ../config/add-ons/kernel/drivers/dev/net as indicated needs to be
> done in the manual instructions above...

The install-networking rule is commented out in the Jamfile. You can install it 
manually or uncomment the needed lines.

> P.S.  Its good to be back up and running on the project!

It is great to have some more people here.
Good luck with our netstack! You will need it. ;)

Waldemar

Other related posts: