Bridged Mode (Non-routed) WanLink

1. A: Go to the Port Manager to see what ports are available. In this example, we will use eth1 and eth2. eth0 is the management port and cannot be used for WanLinks.

For more information see LANforge-GUI User Guide: Ports (Interfaces)

1. Go to the WanLinks tab
2. Create a WanLink
   1. To simulate a WAN, enter a specific amount of delay or other impairment
   2. For this example, enter 20ms of delay for Entry Point A and 30ms of delay for Entry Point B
   3. Be sure to set the correct ports and transfer rate for each Entry Point
   4. Click OK when done
3. Verify the WanLink was created
4. Go to the Status tab and click Netsmith to view the graphical representation of the WanLink
5. This is the general form of a Bridged Mode WanLink in Netsmith. It consists of two 0.0.0.0 IP addressed ports with a vertical bar between them.

For more information see LANforge-GUI User Guide: WanLinks (ICE)

1. Right-click on the WanLink and select Toggle WanLink to allow traffic to flow from a transmitting device to a receiving device
2. The transmitting/receiving devices can be just about anything that generates and receives traffic such as a web server and client or a pair of LANforge-FIRE ports.
   1. Right-click the WanLink and select Display WanLink
3. View the WanLink display

For more information see Refer to the LANforge FIRE Cookbook to run traffic.

1. Selecting a WanLink automatically selects the WanLink Endpoints on the bottom panel
2. Scroll to the right on the bottom panel to note the Serialization Delay (delay injected by LANforge to account for packet size and transfer rate). Also, the WanLink must have a high enough transfer rate to pass all the traffic. In other words, if a layer-3 connection is sending 100Mbps of traffic, the WanLink must allow at least 100Mbps transfer rate
3. In this case, SD = (1514 bytes * 8 bits/byte) / 1.544Mbps = 7.8ms
4. The total delay as experienced by the transmitting/receiving device is the sum of the WanLink configured delay and the serialization delay which in this case would be about 28ms in one direction and 38ms in the other.

For more information see LANforge FAQ: Serialization Delay