Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 4 and Version 5 of NetworkBridging


Ignore:
Timestamp:
2012-04-20T14:48:50Z (7 years ago)
Author:
Jakub Jermář
Comment:

Update the document to reflect the recent changes in HelenOS networking stack.

Legend:

Unmodified
Added
Removed
Modified
  • NetworkBridging

    v4 v5  
    11== HelenOS on a physical LAN/Internet from QEMU/KVM ==
    22
    3 This is a simple DIY checklist for running HelenOS in QEMU/KVM and connecting its TCP/IP networking stack to a real physical ethernet LAN and possibly to the public Internet via this LAN. Please note that the functionality of the HelenOS TCP/IP stack is still severely limited (especially concerning the actual usability of the UDP and TCP protocols), but the situation should improve soon.
     3This is a simple DIY checklist for running HelenOS in QEMU/KVM and connecting its TCP/IP networking stack to a real physical ethernet LAN and possibly to the public Internet via this LAN.
    44
    55This checklist should work reasonably well with any recent GNU/Linux (2.6) distribution and QEMU/KVM 0.13.x on a IA-32 or AMD64 host system with a physical ethernet network card. Without any special arrangements you also need to have a root access on the host machine. If you have a substantially different software or hardware configuration than assumed by this checklist, you have to do the proper adjustments to the checklist.
     
    184184== Configuring HelenOS networking ==
    185185
    186 HelenOS does not support dynamic network configuration (e.g. via DHCP) so far. Thus, you need to configure the IP parameters for HelenOS manually prior to running it in QEMU/KVM. Just go to the ''uspace/srv/net/cfg'' directory in the HelenOS source tree and edit the ''ne2k'' configuration file according to your network parameters (you need to reserve an IP address statically for your HelenOS virtual machine, perhaps by asking your network administration to do so). For example, in my case I have to change the configuration to the following values:
    187 
    188 {{{
    189 IP_ADDR=192.168.254.254
    190 IP_NETMASK=255.255.255.0
    191 IP_BROADCAST=192.168.254.255
    192 IP_GATEWAY=192.168.254.1
    193 }}}
    194 
    195 Compile HelenOS for IA-32 in the usual way.
     186HelenOS does not support dynamic network configuration (e.g. via DHCP) so far. Thus, you need to configure the IP parameters for HelenOS manually. After HelenOS boots up, use the `inetcfg` to configure the networking stack. For example:
     187
     188{{{
     189/ # inetcfg create 192.168.254.254/24 net/eth1 myaddr
     190/ # inetcfg add-sr 0.0.0.0/0 192.168.254.1 default
     191}}}
     192
     193See the [wiki:UsersGuide/Networking User's Guide] for more information on how to use networking in HelenOS.
    196194
    197195== Running HelenOS in QEMU/KVM ==
    198196
    199 Finally, after all has been successfully configured and HelenOS is compiled, you can run it with a command line similar to this one:
     197Start HelenOS with a command line similar to this one:
    200198
    201199{{{
     
    213211'''Note 2:''' The ''-device ne2k_isa,irq=5,vlan=0'' and ''-net tap'' options are essential for the correct functionality of the networking, you probably should not mess with them. Also please take note that the networking won't currently work in SMP virtual machines (with more than one CPU).
    214212
    215 == Starting up networking in HelenOS ==
    216 
    217 After HelenOS boots up, just run the following command from ''bdsh'':
    218 
    219 {{{
    220 net
    221 }}}
    222 
    223 You should see some output indicating whether the initialization of the whole networking stack went OK and if it is the case then HelenOS should be ''visible'' on the network.
    224 
    225213== More Info ==
    226214