VNUML Installation Guide
version 1.5

Authors:
Fermin Galan (galan@dit.upm.es)
David Fernández (david@dit.upm.es)

March 21st, 2005

VNUML 1.5 package includes an easy to use installer thanks to Tony Prug contributions. The old tedious step-by-step installing way isn't needed anymore.

The most of the case, all you need to install VNUML is untar the package in your GNU/Linux box (the package is quite distribution agnostic, but specific issues for SuSE and Mandrake can be found later in this document) and perform the following operations. A Internet connection is needed, in order the installation scripts connect to CPAN (and other places) to get Perl modules and other libraries.

Note that UML simulations generally consume a lot of physical host resources (CPU, disk storage, RAM, etc). As a minimum, you need a standard Pentium III 500 Mhz with 128 Mb RAM to perform the tutorial included in the documentation. However, at least 256 Mb (better 512 Mb) and a faster CPU are recomended to execute more complex scenarios.

./configure
make
make install

(The lastest command needs root privileges in the host)

Several options can be configured using configure script (for example, the installation prefix). The ./configure --help give the list of the available options.

Host kernel needs include tun and loop support in order to work properly. Skas support is also very desirable. 8012q is also required if you plan to use the VLAN features of VNUML.

Please read the INSTALL file that comes with the package in order to get futher information and details.

1.1. Perl modules manual installation

In the case of you are installing in a host without Internet connection or when CPAN autoinstallation fails (some users have reported this problem), you may find useful installing Perl Modules manually, as was done in old pre-packaged VNUML versions.

The required Perl modules can be found here (note that the VNUML local storage may be old of date, we recommend you to find always the newest stable version of this modules in CPAN):

• XML-Parser-2.31
• XML-RegExp-0.03
• libxml-perl-0.07
• XML-DOM-1.42
• XML-Checker-0.13
• TermReadKey-2.21
• Math-Base85-0.2
• Net-IPv4Addr-0.10
• Net-IPv6Addr-0.2
• Exception-Class-1.20

Perl modules are distributed as .tar.gz files. The standarized way to install them is the following:

1. Uncompress file.
2. Execute 'perl Makefile.PL'. This checks dependencies and tell you if another required module have to be installed previously.
3. Execute 'make'.
4. Execute 'make test'. Note that (curiously!) not getting 100% success doesn't mean always that the module is not going to work.
5. Install the module with 'make install' (root privilegies are needed).

If you find some required module is missing in the list before, please, tell us in order to add it.

SuSE releases seems to have a (yet strange) bug that imposes to change -eth0 network interface names to -ethX in order to work. Anyway, you don't have to worry if installing VNUML in a SuSE box, because of the installing scripts are cleaver enough to detect the situation and patch the program.

In the case of using VNUML in a SuSE box, you should see the "SuSE" string appended to the version number when getting the vnumlparser version:

kastrup# vnulmparser.pl -V
This is vnumlpaser.pl version: 1.5.0-rc2.SuSE (01/12/2004)
Fermín Galán Márquez. galan@dit.upm.es

From https://lists.dit.upm.es/pipermail/vnuml-users/2004-November/000115.html.

• The usual './configure ; make ; make install' may fail in the last step if the perl-devel RPM package is not installed (it seems not being installed in the default Mandrake 10.0 installation). In particular, the problem seems not finding the /usr/lib/perl5/5.8.3/i386-linux-thread-multi/CORE/config.h file, that is included in that package.
• The libreadline4-devel RPM package seems to be needed in order to compile the tools (it seems not being installed in the default Mandrake 10.0 installation).
• The /dev/net/tun device file only seems to exist when tun module is loaded. So, you need to 'modprobe tun' before running vnumparser.pl in order to avoid the '/dev/net/tun is not a valid character device file' error message.