Candela Technologies Logo
+1 360 380 1618 [PST, GMT -8]
Network Testing and Emulation Solutions

LANforge Server Installation


  1. Internet Accessed Automated Installation or Upgrade
  2. Offline/Local Automated Installation or Upgrade
  3. Hardware Requirements
  4. Software Requirements
  5. Getting Your Linux Box Ready for LANforge
  6. Installing LANforge Server on Linux
  7. Configuring a Static IP Address
  8. Installing LANforge Server on Microsoft Windows
  9. Installing LANforge Server on Google Android Devices
  10. Upgrading LANforge Server on Linux
  11. Upgrading LANforge Server on Microsoft Windows
  12. Common Problems & Solutions


Candela Technologies typically delivers the LANforge system fully installed and configured on tested and approved hardware platforms, such as a 1U rack mounted unit. Anyone having a thorough understanding of Linux operating systems, however, should be able to install and configure a functional LANforge system on their hardware platform of choice. LANforge also supports Windows XP, Vista, and Windows 7, but LANforge works best on Linux.

Legal use of the LANforge system is based upon licensed data-generating ports and/or machines. You must own a license for every port or machine configured to generate traffic.

This document is targeted at those who wish to install the LANforge Demo software on their own hardware, and those who are re-installing software on hardware furnished by Candela Technologies.

Candela Technologies offers support packages! We want to help you get the most out of our product.

  1. Internet Accessed Automated Installation or Upgrade

    If you are installing or upgrading to LANforge 5.3.6 or higher, and are using Fedora F24 to F17 (or related OS), you may want to use the fully automated installation option. Fedora F24 is currently the suggested OS. For other OS versions, please contact Support for OS installation information.

    If you are using CentOS 6, please read the CentOS 6 Instructions below.

    The script will take a base install and add appropriate packages, install or upgrade LANforge server, GUI, kernel and supporting files and tweak the OS to run best with LANforge. We suggest you create the account lanforge on the system before running this script.

    1. Log into LANforge machine as the root user, and open a terminal window.
    2. Make sure you can reach
      $ ping
    3. Run the automated install/upgrade script. The example below assumes that you wish to install LANforge version 5.3.6 and kernel version 4.9.29+. Change the version numbers as needed by using the latest information from the release download page.

      Example showing an automated install with most options enabled:

      perl <(curl -s \
      --do_all_ct --kver 4.9.29+ --lfver 5.3.6

      Ensure the script finishes without errors before you continue.

      If perl does not exist, you can install it on Fedora systems with: yum install perl On Ubuntu, try: apt-get install perl.

      To see all available options use the following command:

      perl <(curl -s --help

      For F17 and higher systems (gnome-3 based systems), the script will tweak the desktop settings if you are logged into the graphical desktop. If you are not logged in currently, just run the tweak commands next time you do log in (as user lanforge): /usr/local/bin/ctgnome.bash

    4. For fresh installs, on Fedora 15 and higher, you may wish to edit the network device names from things like p1p2 to eth0. If so, edit the /etc/udev/rules.d/70-persistent-net.rules file. You will also need to rename and edit the corresponding /etc/sysconfig/network-scripts/ifcfg-* files to match the new names. When done, reboot to make sure the system comes back up with the specified kernel and with properly named network interfaces.
    5. For fresh installs, you probably need to reconfigure LANforge a bit to select the proper management interface:

      cd /home/lanforge; ./serverctl.bash stop; ./lfconfig --new_layout

      When done configuring, start up LANforge again if you used the text-based lfconfig option: ./serverctl.bash start. If you used the GUI, then LANforge will be restarted automatically.

    6. Reboot the LANforge machine and make sure it comes back up running the proper kernel and LANforge software.
    7. Contact Support if you have any questions or notice problems with the install script.
  2. Offline/Local Automated Installation or Upgrade

    If you are installing or upgrading to LANforge 5.2.7 or higher, and are using Fedora 24 to Fedora 19 (or related OS), you may want to use the automated installation option. For other OS versions, please contact Support for OS installation information. This is designed primarily for updating an existing system. Offline install means LANforge cannot download new Operating System packages, you may have to manually install/update those as needed.

    Change the version numbers as needed by using the latest information from the release download page.

    The following example is for upgrading a 64 bit, Fedora 20 based system to LANforge release 5.3.6:

    1. Download the install/upgrade script by saving the following link:

      Note: You may have to copy and paste the lf_kinstall.txt from a browser to a plain text document.

    2. Copy the lf_kinstall.txt file to the LANforge machine, using winscp or similar and save it in the /home/lanforge/Downloads/ directory. Perform the following commands to get a list of files to download:
      cd /home/lanforge/Downloads
      dos2unix lf_kinstall.txt
      chmod a+x lf_kinstall.txt
      ./lf_kinstall.txt --do_all_ct --print_only --kver 4.9.29+ --lfver 5.3.6

      You should see output similar to this:

      # is-ubuntu: 0 mate-installed: 1 install-mate: 0  is-arm: 0 is-fedora: 1  osveri: 20 is-64: 1
      # do-gnome: 0  uveri: 14
      # lf_kinstall offline install will need these files:
    3. Download the URLs and transfer them to the /home/lanforge/Downloads directory. If you do not have a password, you may log in as user 'guest' with password 'guest'
    4. Log into LANforge machine as the root user, and open a terminal window.
    5. Perform the following commands:
      cd /home/lanforge/Downloads
      ./lf_kinstall.txt --do_all_ct --kver 4.9.29+ --lfver 5.3.6 --source_dir /home/lanforge/Downloads
    6. Ensure the script finishes without errors before you continue.
    7. Reboot the LANforge machine and make sure it comes back up running the proper kernel and LANforge software.
    8. Contact Support if you have any questions or notice problems with the install script.
  3. Most Recent Fedora Releases

    If you are installing LANforge on the latest version of Fedora, you will probably discover that our packages are labeled one release behind the recent Fedora release. The installer has a switch for this:

    Below is an example of doing an offline installation on Fedora 25:

    ./lf_kinstall.txt --do_all_ct --force_osver F24 --lfver 5.3.6 --kver 4.9.29+ --source_dir /home/lanforge/Downloads

    LANforge Server and GUI software is tested on recent Fedora versions, but it is not always possible to keep up with the latest version. In some cases, new versions of Fedora have been inappropriate and those releases get skipped. If you get the latest version of Fedora, it will often be more recent than our validated Fedora target.

  4. CentOS 6 Installation

    CentOS 6 (6.9 as of this writing) often installs with a very minimal package set and might require preparation before they will run the script. This is very true for the CentOS 6 Minimal Installation. To prepare the system for LANforge, login as root to your system and run the following commands:

    yum install -y yum-utils
    yum-config-manager --enable centosplus > /dev/null
    yum-config-manager --enable contrib > /dev/null
    yum-config-manager --enable epel > /dev/null
    yum makecache fast
    yum install -y man bash-completion bind-utils nfs-utils perl screen rsync vim wget
    yum update -y

    After these commands are executed, you can continue with the automated installation instructions. You should not need to reboot.

    (Optional) If your system needs access to NFS shares during installation, these commands will enable NFS:

    /sbin/chkconfig rpcbind on
    /sbin/chkconfig nfs on
    /sbin/service rpcbind start
    /sbin/service nfs start
  5. Hardware Requirements

    The LANforge-FIRE Network Traffic Generator configuration typically requires at least two ethernet ports: one for network management and one for data-generation. The LANforge-ICE Network Emulator works best using a minimum of three ethernet ports. Your unit's performance will be directly related to the CPU and memory as well as the quality of the ethernet hardware and PCI(e) bus. Candela Technologies suggests a minimum of 128MB RAM and a 600Mhz processor. You may be interested to look over the LANforge Hardware Install Guide for more information.

  6. Software Requirements

    NOTE: LANforge now has limited support for the Microsoft Windows operating systems. See the Microsoft specific install section for more information.

    The LANforge product line is primarily developed and tested on Fedora Linux. However, the LANforge processes should work on any distribution based on the 2.6 or higher Linux kernel. To help guarantee success, Candela Technologies recommends that you use Fedora Linux with Candela's custom kernel. If using Fedora Core 4 or higher, be sure to disable SELinux. See below for a suggested kernel patches and .config file if you are compiling your own kernel. Specific work-arounds for Suse and other versions of Linux are found in the troubleshooting section at the end of this document.

    The installation should include the following:

    Required: Perl scripting language.
    Required: IP configuration tool, verify version with: /sbin/ip -V
    Suggested: Bridge utilities.
    Suggested: DHCP Server.

    Any modern distribution should install everything that is required by default, and optional packages can be installed with the normal package management tools (yum, apt-get, etc).

    Virtual Router OSPF support

    If you want to use Virtual Routers with OSPF or multicast routing, download the xorp package from the LANforge release directory.

    To install:

    1. Change directories to /usr/local as root:
      # cd /usr/local
    2. Unzip the download:
      $ tar -xvzf xorp*.tgz
    3. Run the install script. It will create a xorp user, add xorp to both root and xorp groups, and attempt to fix library problems if any exist.
      # cd /usr/local/xorp
      # ./xorp_install.bash

    Installing a LANforge Linux Kernel

    1. Download an appropriate pre-built kernel from the downloads page.
    2. Install the kernel as root with command similar to:
      # cd /
      # tar -xvzf /home/lanforge/ct2.6.31.6.p4s.tar.gz
      # /usr/local/bin/kinstall_ct2.6.31.6.bash

      If you are using Suse, this kinstall script will probably fail. Try making the initrd script with a command similar to:

      # mkinitrd -k ct2.6.31.6.img -i initrd-ct2.6.31.6.img
    3. Update /etc/grub.conf by adding an entry similar to the text below. You should usually copy an existing entry and change only the title, kernel image and initrd image file names.
      title Candela Technologies Linux
      root (hd0,0)
      kernel /ct2.6.31.6.img ro root=LABEL=/ rhgb quiet
      initrd /initrd-ct2.6.31.6.img

      If you are using Suse, you will edit /boot/grub/menu.lst instead.

      When using recent LANforge kernels on older distributions (Fedora 11 and earlier), you may need to enable some compatibility code in the kernel proc file system. To enable this, add: sysfs.deprecated=1 to the kernel boot arguments in the grub configuration file.

    4. The kernel installation should now be complete. Reboot and choose the Candela kernel. To make this the default option, edit the default= line in /etc/grub.conf

    Compiling Your Own Linux Kernel

    NOTE: For optimum performance, you should use one of the pre-compiled LANforge Linux kernels, or compile your own with the Candela patches applied. Pre-compiled LANforge Linux kernels can be found on the Downloads page.

    Candela now publishes its patched linux tree in a public git code repository on github.

    1. Download the kernel source respository:
      $ git clone
      More kernels are available on github:
    2. Use one of the config files in the linux-ct-4.7/configs directory as a starting point.
    3. If you are unsure how to compile kernels, consider using a pre-compiled one or contact Support.
  7. Getting Your Linux Box Ready for LANforge

    1. Install the Necessary Hardware.

      Ensure that you have at least two ethernet interfaces installed in your target platform. Ensure you have at least 64MB of RAM installed. LANforge is very flexible, so if you have hardware constraints that do not appear to be supported by LANforge, please contact Support. It is likely we have a solution!

    2. Install and Configure the Linux Operating System.

      Choose a distribution that meets the requirements above and install according to its instructions. If you are using RedHat or Fedora, choose the 'Server' or 'All' package selection, or customize to your specific needs and hope it works! (It probably will.)

      An IP address should be assigned to the management port, and the other ethernet port(s) can be left unconfigured at this time. You can use DHCP for the management port.

      It is assumed that the user will be able to correctly configure the Linux Operating system.

      In addition to installing the OS, you may want to install and configure the Network Time Protocol (NTP) tools. You can configure NTP as part of the initial login process on Fedora Core 2 and above.

    3. Install the Wireshark Packet Sniffer.

      If you would like to be able to have LANforge automatically launch the Wireshark packet sniffer, then you must install Wireshark. If you choose not to install Wireshark, however, LANforge will still function normally. The particular version to install and additional packages you have to download depends on your Linux distribution. For Fedora Core 5 and similar distributions, Wireshark is included on the install CDROMs, though it is not always installed by default. You can usually install it with this command as root user:
      # yum install wireshark-gnome

      In the end, LANforge will attempt to execute a file called /usr/sbin/wireshark. If that fails, it will attempt to execute /usr/sbin/ethereal. So as long as one of these files exists, it will work.

      To install the very latest Wireshark with LANforge support, perform the following steps on your LANforge system as root user.

      $ yum install -y shtool libtool bison flex glib2-devel gtk2-devel libpcap-devel gcc-c++.x86_64
      $ cd /home/lanforge
      $ git clone
      $ cd wireshark
      $ git checkout HEAD
      $ libtoolize --force
      $ aclocal
      $ autoheader
      $ automake --force-missing --add-missing
      $ autoconf
      $ ./configure
      $ make
      $ make install
      $ if [ -f /usr/local/bin/wireshark-gtk ]; then mv -f /usr/local/bin/wireshark-gtk /usr/local/bin/wireshark; fi
    4. Install Perl Library: Net::Telnet for use with LANforge Scripting.

      If you wish to use LANforge scripting, you will need the Net::Telnet perl library installed. The easiest way to install is to use Perl's MCPAN tool:

       $ perl -MCPAN -e shell
      ## Choose 'no' when it asks you if you want to manually configure
      ## perl.  The auto-config works just fine.
      CPAN> install Net::Telnet
      CPAN> quit
  8. Installing LANforge Server on Linux

    Now that you have the Linux Operating System installed on your box, you are ready to install the LANforge components.

    1. Become root user
      $ su - root
    2. Create LANforge Accounts

      You should create a lanforge user and install the LANforge software in that user's home directory. Use your preferred method, or use mine:
      # adduser lanforge
      # passwd lanforge

    3. Install LANforge Server

      Copy the LANforgeServer-X.X.X_Linux-XX.tar.gz file to some temporary directory and un-tar it with a command like:
      # tar -xvzf LANforgeServer-*_Linux-x86.tar.gz That command should create a LANforgeServer-X.X.X directory, in which the distribution exists. Change to that directory as root, and you will find an install.bash file.
      Run this script:

      # ./install.bash
    4. Configure LANforge Server

      NOTE 1
      The lfconfig tool often scrolls information off the screen, so you may need to scroll back to see useful information. On the console, use SHIFT-PageUp, SHIFT-PageDown.
      NOTE 2
      Make sure you enter 'config' when done with the lfconfig changes: It is the config option that creates the files needed to run the LANforge applications.
      NOTE 3
      Make sure that each resource machine has a unique identifier. This identifier is specified as 'resource', and you can find more details below.
      NOTE 4
      If you wish to run the LANforge-ICE WAN Emulator on a machine with only two ethernet ports, the management device (mgt_dev) must be 'lo', the loopback device. This means you will not be able to get network connectivity to this machine when LANforge is running as both of the ICE interfaces must have an IP address of

      After running the install script, cd to the /home/lanforge directory as root and run the lfconfig script to configure LANforge:

      $ cd /home/lanforge
      $ ./lfconfig

      It is an interactive script that allows you to set certain configuration options and then generate the start/stop scripts to control LANforge. The lfconfig script now hides some of the less often used options. You can view them with the show_all command. However, for most configurations, you will not need to change any of the hidden options.

      When you start lfconfig, you will see something like this:

      Interfaces: eth0 eth1 eth2 eth3
      Resource interface assignment:
        Resource 1:  eth0 eth1 eth2 eth3
      Specified Resource Addresses:
      Key               Acceptable Values          Value
      log_level         [0-65535]                  7
      log_dir           [directory path]           /home/lanforge
      add_resource_addr [host:port]                SEE LIST ABOVE
      rem_resource_addr [host:port]                SEE LIST ABOVE
      realm             [1-255]                    255
      resource          [1-511]                    1
      mgt_dev           [ethernet device]          eth0
      mode              [resource, manager, both]  both
      bind_mgt          [0-1]                      0
      shelf             [1-8]                      1
      dev_ignore        [eth0 eth1 ... ethN]
      first_cli_port    [1025-4199]                4001
      connect_mgr       [host:port]
      gps_dev           [device file]              NONE
      max_tx            [1-500]                    5
      wl_probe_timer    [50-2000]                  50
      Other Commands:  help, show_all
      If these values are correct, enter 'config', otherwise change
      the values by entering the key followed by the new value, for example:
      mode manager
      Your command:

      Here are the values you can manipulate, and what they mean:

      Suggested value is 7, run the btserver binary with the -h option to see what the logging level means.
      Example:  log_level 7
      GPS Device, for those wishing to integrate a GPS through the serial port using the NMEA protocol.
      Example:  gps_dev /dev/ttyS0
      Example:  gps_dev NONE
      Suggested value is /home/lanforge, specifies where the logs are to be stored.
      Example:  log_dir /tmp
      If you don't want to use some of your interfaces for LANforge, then enter them here. Otherwise, lfconfig will attempt to use them all.
      Example:  dev_ignore eth5 eth6 tr3
      Add to the list of remote LANforge addresses. These are LANforge resources that will otherwise not be discovered for various reasons. You must have TCP/IP connectivity to them of course!
      Example:  add_resource_addr
      If enabled, LANforge will only listen on the mgt-dev's IP for management traffic. If disabled, it will listen on all IPs on the local machine. Enabling this can help make LANforge more secure, but may also make it harder to access. The value 0 means disabled, 1 is enabled. NOTE: If you enable the bind_mgt option and are in mode 'both', and not using 'lo' for management device, then you will need to explicitly add a resource addr for [ip-of-mgt-port]:4004 so that the manager can communicate with the client process.
      Example:  bind_mgt 1

      Remove from the list of remote LANforge addresses. These are LANforge resources that will otherwise not be discovered for various reasons. You must have TCP/IP connectivity to them of course!
      Example:  rem_resource_addr

      Maximum number of packets to tx per 'round.' The higher this number is the better performance you may achieve. However, if you make it too high, you may increase dropped packets due to making the traffic pattern too bursty. Suggested value is between 5 and 10 for traffic patterns around 2000 packets-per-second.
      Example:  max_tx 50

      Number of milliseconds between probes of kernel-mode WanLink stats. Default is 50. Increasing this will save some processing time, at the cost of less accurate 3-second report averages and graphs. Example:  wl_probe_timer 50
      LANforge resources grouped (clustered) with the same realm value can be managed by a single LANforge-GUI. LANforge processes will ignore messages from other realms. Valid range of values is 1-255, inclusive, and the default is 255. If set to 255, it will never cluster with other LANforge systems, even if the other system is set to 255 also.
      Example:  realm 1
      This is the virtual 'shelf' that this LANforge instance should belong to. Unless you have a very large installation, you should enter 1 here. If you have more than 511 LANforge resources, then you will need to put them into a second shelf.
      Example:  shelf 1
      Every LANforge resource (data-generator) on a given shelf MUST have a unique instance (machine) identifier. Suggested values are 1 for the first data-generator machine, 2 for the second, 3 for the third, etc. This was previously called 'client'.
      Example:  resource 1
      This is the CLI (command line interface) port. If you have multiple resources configured on the same machine (unlikely), then the second will be 2 greater than the first, etc. The binary (GUI) port for a given resource will always be one more than the CLI interface port. You can usually leave this at its default: 4001
      Example:  first_cli_port 4001
      Tell resource to connect to a known manager. Normally managers connect to resources, but sometimes it's useful to connect the other way to get around firewalls and when using mobile resources that may often change their management IP address.
      Example:  connect_mgr
      Example:  connect_mgr NONE
      This is the ethernet device that the LANforge management traffic is carried over. The management devices for the LANforge manager and LANforge resources should be connected to the same ethernet broadcast domain (LAN). If you want this system to be completely self-contained, you can have mgt_dev be lo (loopback).
      Example:  mgt_dev eth0
      This determines the behavior of the LANforge software. You need exactly one LANforge manager for each network, and at least 1 LANforge resource. The basic software is the same, and its behavior is determined by the mode you enter here. Use 'both' for a single machine configuration. For multiple machine configurations, you will usually have one machine in mode 'both', and the remaining machines in mode 'resource'.
      Example:  mode resource

      Example Configurations

      • All-in-One/Stand-alone LANforge-ICE WAN Emulator & Traffic Generator
        This is the default configuration and enables a machine with 3 ports to be a fully functional WAN emulator and/or traffic generator. The LANforge-GUI can be installed on the same machine to enable easy management as well. NOTE: LANforge resources with the default realm of 255 cannot be clustered. See the clustered resources example below to enable this feature.
        mgt_dev eth0
        resource 1
        realm 255
        mode both
      • LANforge data generator (or WAN Emulator) Resource only machine
        Generally, you will have one system that is both a manager and a traffic generator (see above), and the rest will be only resources. The manager will discover the resources and will be the central point for configuring the entire system. The resource machines must have unique identifiers (resource must be unique). NOTE: LANforge resources with the default realm of 255 cannot be clustered. See the clustered resources example below to enable this feature.
        mgt_dev eth0
        resource 2
        realm 22
        mode resource
      • LANforge Manager with Clustered Resources
        Configure LANforge resources in the same realm as the manager as illustrated by the list of lfconfig key value entries in the example below:
        Manager + Resource #1 Resource #2 Resource #3 Resource #4
        mgt_dev eth0
        resource 1
        realm 22
        mode both
        mgt_dev eth0
        resource 2
        realm 22
        mode resource
        mgt_dev eth0
        resource 3
        realm 22
        mode resource
        mgt_dev eth0
        resource 4
        realm 22
        mode resource

        NOTE: Entering config creates a port configuration file called lanforge_eth_1 for resource 1 or lanforge_eth_2 for resource 2, etc., which is saved in the /home/lanforge directory. All clustered resources will now be displayed on the Status page of the LANforge-GUI and will be listed in the Port Mgr tab.

      After running the lfconfig script, you should have a box that is functionally similar to the LF1000 Series units. Now, go to the Hardware Installation Guide and proceed to install your new box into the LANforge system.

    5. Start LANforge Servers

      To start the LANforge servers, use the serverctl.bash script as root:

      # ./serverctl.bash start

      From now on, the LANforge server will be started when the machine boots.

    iSCSI Client

    Two packages must be installed to support ISCSI client. Following installation, the Level 3/5 iscsi and iscsid services must be disabled to facilitate LANforge control. LANforge can/should configure the rest of it for you by setting up file-io endpoints of type iscsi.

    • 32-bit installation as root:
      # yum install iscsi-initiator-utils.i386 scsi-target-utils.i386

    • 64-bit installation as root:
      # yum install iscsi-initiator-utils.x86_64 scsi-target-utils.x86_64

    • Disable services after installation as root:
      # chkconfig iscsi off
      # chkconfig iscsid off

  9. Configuring a Static IP Address

    For current LANforge releases, you can just use the GUI to set the preferred fixed address (or DHCP) from the Port-Mgr tab just as you would configure any other interface. For older LANforge releases, or if you prefer to do it manually, follow the steps below.

    NOTE: You should NOT change the management interface's IP address while LANforge is running. You should first stop LANforge, then change the IP, then start LANforge again. Or, you can just reboot the machine and the new settings will take affect automatically.

    • Stop LANforge as root:
      # /home/lanforge/serverctl.bash stop
    • NOTE: For Redhat, Fedora, and similar systems, you will edit the /etc/sysconfig/network-scripts/ifcfg-[device-name] file.

      These examples assume the management interface is called 'eth3'. Your system may be using a different management interface! A DHCP configuration file looks similar to:

    • To change to a fixed address, use settings similar to:
    • You may also want to configure the default gateway/router for the system by editing the /etc/sysconfig/network adding a line similar to:
    • To have the new settings take affect, you can bring the interface down and back up again with the commands (as user root):
      # ifdown eth3
      # ifup eth3
    • Or if connected via IP:
      # (ifdown eth3; ifup eth3)
    • Start LANforge as root:
      # /home/lanforge/serverctl.bash start
  10. Installing LANforge Server on Microsoft Windows

    Most LANforge traffic generation and network emulation features are available on Microsoft Windows operating systems. Click here for details on supported features. LANforge on Linux is still the most precise, featureful, and highest performing option. Please contact Candela Technologies or your sales representative if you have questions about whether a feature you need is supported on Windows. Windows managers can manage Linux data generators, and vice versa.

    Currently, only Windows XP, Vista and Windows 7 are actively tested. LANforge may work on other platforms as well.

    Install the LANforge Server Files

    1. Execute the LANforge Server-Installer.exe program. At the end of the LANforge install, you have an option to run the "Configure LANforge" tool. Please do run this tool (or re-run from the desktop) and click 'Configure' unless you are certain you do not need to do so.
    2. In the configuration tool, select the mode (you will want one machine configured to be 'Both' (Manager and Resource) in your realm). The rest of the machines should be configured in resource mode only.
    3. The text box at the top of the configuration tool shows the LANforge server startup information and the list of interfaces found on the machine. You will need to choose one of the adapters for your management interface. 'Management Network Device' from one of the 'Device ID:' fields.

      For example:

      Device ID: {20AC6D62-1D4E-49E1-982A-091CD9329CB3}
      Management Network Device | {20AC6D62-1D4E-49E1-982A-091CD9329CB3} |
    4. The 'Realm Number' can be any value between 1 and 255. By placing a machine into a certain realm, you ensure that the LANforge software will only communicate with other machines in that same realm. Realm 255 means do not cluster.
    5. Each LANforge machine in a cluster must have a unique identifier. This is the 'Resource Id Number', and it corresponds to the resource number in the LANforge GUI. Typically, you use 1 for the first system, 2 for the second, and so forth.
    6. If your management network is routed, and you are configuring a machine as Manager or Both mode, then you will need to specify the IP addresses for the other LANforge resource machines in the Clients <IP:port>. The reason is that while LANforge can automatically discover other LANforge machines on the local subnet, it cannot automatically discover LANforge machines on other subnets. The syntax for multiple resources is a space separated list of IP address and ports. The default port is 4002, unless you manually edit the start scripts.

      For example: IP#1:Port1 IP#2:Port2 IP#3:Port3

      Example input for three remote resources is:
    7. If you are configured for mode 'Both' or 'Manager', then you must install the LANforge license keys sent to you by Candela Technologies or your LANforge reseller. Install these license keys per instructions in the license file. (Typically, copy the keys to a file called license.txt in the LANforge install directory.)
    8. Configuration should now be complete. Click on the 'Configure' button to create the LANforge server start script shortcuts (LANforge Manager and LANforge Data Generator) on the desktop.

      To start the LANforge server on a 'Both' system double click both the LANforge Manager AND LANforge Data Generator shortcuts.

      Likewise, a Manager only node will only require the LANforge Manager shorcut executed while a Resource node will only require running the LANforge Data Generator shortcut.

      NOTE: Windows Vista and Windows 7 users must run the LANforge Manager, LANforge Data Generator and usually the LANforge GUI as administrator for a LANforge system to function properly.

      The shortcut properties should be modified to run as administrator: right-click on the shortcut icon, select Properties and click the Advanced button. Select 'Run as administrator' then click OK on both the Advanced Properties and LANforge Manager (or LANforge Data Generator) Properties windows.

    9. Optional packages: NTP
      If you want to keep the clocks for multiple systems in sync (to better report latencies with LANforge-FIRE, for instance), you should consider installing NTP.
      Candela suggests this page for more info and downloads:
    10. Optional packages: Wireshark
      The Wireshark tool is an excellent packet sniffer and protocol analyzer. You can dowload it from: In order for LANforge to be able to automatically launch Wireshark, it must be installed in its default install directory on the same drive as LANforge is installed. You can also launch Wireshark manually of course.
  11. Installing LANforge Server on Google Android Devices

    With the 5.2.10 release, LANforge now supports most Google Android devices. The feature set is limited to basic Layer-3, Layer-4 and VOIP traffic generation over the WiFi or cellular data networks. It will only work on systems using the ARM CPU architecture, but that will be most devices anyway. It has been tested on Nexus 4 and "HTC My Touch" phones.

    To install, search Google Play on your Android device for "LANforge Resource" from Candela Technologies Inc and install the app on your phone. The version of the app (ie, 5.2.11) must match the LANforge manager's release version.

    The app can currently only be configured as a resource, so you must be running a LANforge manager process (with proper licenses installed) on a different machine. Each Android device currently is licensed as a 100Mbps connection license.

    After launching the LANforge Resource app the first time, configure the realm, manager's IP, and the resource-ID. Then press 'Apply'. This will do internal installation and configuration and start the LANforge processes. If you are upgrading or reinstalling the app, click Remove and then Apply again. If you wish to uninstall the LANforge app, first click Stop to make sure any LANforge processes are stopped. The LANforge processes will keep running until you reboot the phone or click the Stop button in the LANforge app.

  12. Upgrading LANforge Server on Linux

    Follow these instructions to upgrade your LANforge Server from an existing Linux installation. Some Example Configurations are listed in the Installing LANforge Server on Linux section.

    1. Check the release notes for special instructions:
      Go to the Downloads Page and scroll down to the latest release notes link.
    2. Stop the LANforge server as root:
      # cd /home/lanforge
      # ./serverctl.bash stop
    3. Backup the existing installation:
      # cd /home
      # tar -cvzf lanforge_bkup.tar.gz lanforge
    4. Upgrade the LANforge kernel as root: Generally, the kernel version should be upgraded to match the LANforge software version both of which can be found on the Downloads Page.
      # uname -r # will give you your current kernel version
      # /usr/local/bin/kinstall_ct<CURRENT KERNEL>.bash
      # cd /
      # tar -xvzf ct<NEW KERNEL>.tar.gz
      # /usr/local/bin/kinstall_ct<NEW KERNEL>.bash
    5. Update GRUB configuration file with new kernel name:
      Copy/paste the default entry and modify it to have the new kernel version. Save and exit file when complete.
      # nano /etc/grub.conf # or vi /etc/grub.conf
    6. Reboot the system for the new kernel to be in use:
      # reboot
    7. Verify new kernel is running:
      # uname -a
    8. Install the new LANforge server software:
      # cd /home/lanforge
      # tar -xvzf LANforgeServer-*_Linux-x86.tar.gz
      # cd LANforgeServer-X.X.X
      # ./install.bash
    9. Regenerate the LANforge configuration as root:
      # cd .. # to /home/lanforge
      # ./lfconfig --new_layout
    10. Install your license keys:

      Follow the license installation instructions in your license key file.

    11. Start the upgraded LANforge server:
      # ./serverctl.bash start
  13. Upgrading LANforge Server on Microsoft Windows

    To upgrade your LANforge server from an existing Windows installation, follow these instructions:

    1. Check the release notes for special instructions:
      Go to the Downloads Page and scroll down to the latest release notes link.
    2. Stop the LANforge Manager and Data Generator:
      Close the DOS windows labeled LANforge Manager and LANforge Data Generator.
    3. Backup your current installation:
      Rename or copy the C:\Program Files\LANforge server directory.
      Simply run the new LANforge Server Installer.
    5. Re-run the Configure LANforge utility.
      You will be prompted after installing the new server software.
    6. Install your license keys:
      Follow the license installation instructions in your license key file.
    7. Start the LANforge server:
      For a 'Both' node, double-click the LANforge Data Generator and LANforge Manager icons.

      Otherwise, double-click the appropriate icon for the node type.

      NOTE: Windows Vista and Windows 7 users must run the LANforge Manager, LANforge Data Generator as Administrator for a LANforge system to function properly.

      The shortcut properties should be modified to run as Administrator:

      1. Right-click on the shortcut icon
      2. Select Properties→Advanced button
      3. Select Run as administrator
      4. then click OK on both the Advanced Properties and LANforge Manager (or LANforge Data Generator) Properties windows.
  14. LANforge Data Generator Installation Troubleshooting Guide

    Q. I upgraded my system to Fedora 11 and NetworkManager is causing problems.
    A. Make sure NetworkManager is OFF and Network is ON in level 3 and level 5 services. From the console, enter the # ntsysv command as root (level 3 services). Turn NetworkManager OFF and Network ON, select OK, and reboot. From a terminal window, enter the # system-config-services command as root (level 5 services). Turn NetworkManager OFF and Network ON, click Save, and select File/Quit, then reboot. To continue using PackageKit (Fedora 9 and later) without NetworkManager, edit /etc/PackageKit/PackageKit.conf and change the following value: UseNetworkManager=false

    Q. I upgraded my system to Fedora 11 and ssh (or console login) session fails.
    A. Make sure SELinux is disabled in System/Administration/SELinux Management. Select 'Disabled' for System Default Enforcing Mode and reboot.

    Q. Things kind of seem to work, but not really.
    A. Unless you specifically know otherwise, make sure the resource indentifiers are unique for every system in your LANforge realm. These numbers correspond to the 'Card Numbers' in the GUI and CLI commands. Also, make sure that all of your LANforge software is of the same version.
    Q. I'm using Suse 9.1 and having trouble.
    A. We found that removing the second 'localhost' entry in the /etc/hosts file (the one starting with ::1) made LANforge work. I think that without this change, LANforge may try to use IPv6.
    Q. I'm using Windows Vista and neither LANforge Manager or Data Generator is working.
    A. Windows Vista users must run the LANforge Manager and LANforge Data Generator as administrator to function properly. The shortcut properties should be modified to run as administrator:
    1. Right-click on the shortcut icon
    2. Select Properties→Advanced button
    3. Select Run as administrator
    4. then click OK on both the Advanced Properties and LANforge Manager (or LANforge Data Generator) Properties windows.

    If you have a problem not answered here, please contact Candela Technologies technical support at

Candela  Technologies, 2417 Main Street, Suite 201, Ferndale, WA 98248, USA | | +1.360.380.1618
Google+ | Facebook | LinkedIn | Blog