Haiku Network Kit: Build & installation instructions

Although the stack isn't quite finished, you can already test some basics.
You'll have to get the code, build it, install it and run it.
There isn't yet an easier way of getting the network stack, we're far from ready to release a binary package.

So, if you accept your mission :

  1. Get familiar

    First, go to team web page.
    Have a look around and see the current status of the stack. Have a glance over the jobs, perhaps there's something that interests you?

  2. Furbish your tools

    Get the build tools suite.
    You'll need CVS, JAM, the fixed LD linker

  3. May the code be with you

    For dark reason, you should have the source code to build.
    So, you must checkout (anonymously) the full OBOS CVS:

  4. Build

    Building the whole Networking Kit stuffs was made easy by Jam rules.
    Simply run these commands from a Terminal:

    $ cd /path/to/your/local/openbeos/current
    $ ./configure
    $ jam NetworkingKit

    It should build all networking kit stuffs. If you encount any compile or link errors, report it to the network team mailing list.

  5. Install

    There are basically two ways to install the networking kit. The first way is to do it manually, as is described below. The second way is easier, as you won't have to do anything manually. If you want to use the second way, use the command jam install-networking. This way you can skip all the manual steps described below. Please note that the Haiku provided utilities like ping, are located under your local current/tests/kits/net/, where you can execute them as often as you like.

    However, if you are the manual type of person, you can find the networking kit binaries now under your local current/distro/x86.R1/*
    To install:

  6. Test, test, test

    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 OBOS ifconfig tool from Terminal to see (and start) the stack detected interface(s) Last, play with ping, arp, traceroute, etc. Also check out the details on the stack design.

This document is written by Philippe Houdoin and edited by Niels Reedijk. Last updated on July 30th, 2004