OpenBeOS Network Kit

• Overview
• Implementation:
  • The shared libraries
    • libnet.so
      • POSIX/BSD sockets support
      • DNS resolver
      • Misc functions
    • libnetapi.so
  • The stack driver
  • The network stack
    • Core module
    • Interfaces modules
    • Protocols modules
  • Network apps
    • The Network GUI preference app
    • ping
    • ifconfig
    • route
    • traceroute
    • arp

• a modular, add-ons based network stack
• two shared libraries, libnet.so and libnetapi.so
• a stack driver, acting as interface between the network stack and libnet.so
• basic network utilities
• a modular GUI preflet

Let's picture(s) talk

The following image shows the overall network design:

Implementation

• The network stack

  Location: src/add-ons/kernel/network

  Todo...

• The stack driver

  Location: src/add-ons/kernel/drivers/net/stack

  The stack driver is the interface between libnet and the real stack behind him, host by the network stack kernel modules.

  His purpose is multiple:
  1. Provide the sockets == file descriptors support
  2. Provide a support for select() on sockets
  3. Load the network stack at first access, and keep it that way then...

• The libnet.so shared library

  Location: src/kits/net/libnet

  This shared library is the way BeOS R5 provide the sockets POSIX/BSD API to apps. Being binary compatible with R5 make this library implementation tedious.

• The libnetapi.so shared library

  Location: src/kits/net/libnetapi

  This shared library contains thin C++ classes wrapping the C sockets POSIX/BSD API into these BNet* classes we're used under BeOS: look at them in your BeBook

• Basic network utilities

  • ping
    Location: src/apps/bin/ping
  • ifconfig
    Location: src/apps/bin/ifconfig
  • route
    Location: src/apps/bin/route
  • traceroute
    Location: src/apps/bin/traceroute
  • arp
    Location: src/apps/bin/arp