User Tools

Site Tools


networkingconfiguration

Networking Configuration

Note about debugging your network configuration under virtualization

Most virtualization software offer many types of network virtualization. For example, the QEMU default network configuration supports for example http but not ICMP. Therefore testing your network connection with ping doesn't work.

The a good way to determine if your network connection is working or not is invoking “pkgin up”. If you get no errors, your connection works AND you have updated the pkgin repo.

Changing selected network card

The netconf utility allows one to change the networking configuration from the options you selected when installing. It allows disable networking, select a different network card (PCI cards are detected, if you have a non-PCI card you should find out what type of card you have first) and allows one to enable or disable DHCP.

Using a Static IP

Add the following lines to /etc/rc.net:

ifconfig -I /dev/ip0 -n <netmask> -h <ip_address>
add_route -g <gateway>

Then add the following lines to /etc/hosts:

your.name.server <name_server>

Supported Network Cards

The follow list is displayed by netconf of version Minix 3.1.7 (2010-07)

The drivers name is found after configuration in file /etc/inet.conf

NIC Selection Corresponding Driver Name
0. No Ethernet card (no networking) (n/a)
1. Intel Pro/100 fxp
2. 3Com 501 or 3Com 509 based card dpeth
3. Realtek 8139 based card (also emulated by KVM) rtl8139
4. Realtek 8169 based card rtl8169
5. Realtek 8029 based card (also emulated by Qemu) dp8390
6. NE2000, 3com 503 or WD based card (also emulated by Bochs) dp8390
7. AMD LANCE (also emulated by VMWare and VirtualBox) lance
8. Intel PRO/1000 Gigabit e1000
9. Attansic/Atheros L2 FastEthernetatl2
10. DEC Tulip 21140A in VirtualPC dec21140A
11. Different Ethernet card (no networking) (n/a)

LwIP

An alternative to the inet server is represented by the lwip server. This server is based on the lwip stack. The stack is separated in the liblwip. The server itself is an implementation of the VFS-INET protocol, the sockets.

To use the lwip instead of inet, lwip=yes must be set in the boot monitor. You can edit the boot parameters by creating a local boot.cfg file and adding lwip=yes to the end of the menu= lines in that file. The update_bootcfg tool will apply your changes. Then, simply reboot to start using lwip.

cp /etc/boot.cfg.default /etc/boot.cfg.local
vi /etc/boot.cfg.local
/bin/update_bootcfg
reboot

It is preferable to use lwip with static network configuration only as there are some problems with the current dhcp client as it uses some very inet-specific non-standard features. DHCP is likely to get the configuration, sometimes the local name server does not get the DNS configuration though. A good configuration for KVM is :

ip      : 10.0.2.15
mask    : 255.255.255.0
gateway : 10.0.2.2
DNS     : 10.0.2.3

Be aware that it is necessary to use -I option with add_route if you are using lwip.

networkingconfiguration.txt · Last modified: 2014/11/11 09:11 by lionelsambuc