Create IPV6 Based Small Computer Network Using A Simulator.: I. Practical Significance
Create IPV6 Based Small Computer Network Using A Simulator.: I. Practical Significance
Proposition 1.
Stateless autoconfiguration: The ability for nodes to determine their own address
Jumbograms: The ability to have very large packet payloads for greater efficiency
Quality of service (QoS) capabilities: QoS markings of packets and flow labels that help identify priority
traffic
To make the network diagram easier to read, use the View → Show menu command to hide all information except
node names (to clean up the display). Also, you can click on Selection Tool and grab the text that represents each
node name and move it to a spot where it is not hidden by the link. Then, use the Configure right-click menu
command on each node to change the node name so that the network look like the following image:
In the Configure dailogue box, after clearing the IP addresses on both of the router’s interfaces, click on
the Services… button, then clear the OSPFv2 and OSPFv3 services. Also clear the radvd service (because we will
explore stateless address auto configuration in a later post). Then press the Apply button.
After we start the network simulation we created, we expect to observe that the interfaces on each simulated router
and on each simulated host have link-local IPv6 addresses automatically configured.
We will also run some simple network tests and observe the results. With the current configuration, nodes on the
same link should be able to communicate with each other but nodes that are separated by the router should not be
able to communicate with each other1. For example, host h1 should be able to ping host h2, but not host h4.
Link-local unicast IPv6 address, defined
When an IPv6 interface starts up, it is required to automatically configure itself with a link-localunicast IPv6
address2. Link-local IPv6 addresses consist of a specific 64-bit IPv6 prefix, fe80::/64, and a unique 64-bit interface
identifier derived from the MAC address of the interface3.
Link-Local unicast IPv6 addresses are created for purposes such as auto-address configuration and neighbor
discovery on a single link. A link may be a point-to-point connection between two interfaces or a switched layer-2
domain such as an Ethernet network.
Link-local unicast addresses only work on the link on which they are configured because IPv6 routers are required to
not forward any packets with link-local source or destination addresses to other links.
Using the ifconfig Observer Widget
We can use the Core Network Emulator’s Observer Widget tool to view the interface configuration on each node and
take note of the IPv6 address on each interface. Click on the Observer Widget tool (the magnifying glass icon in the
toolbar) and select the ifconfig widget. Then, hover the mouse pointer over each node to see the displayed interface
configuration.
Alternatively, we can open up a terminal window on each node running in the simulated network and use normal Linux
commands to view the configuration
Double-click on any node to open a terminal window (for example, host h1). Then, execute the command.
Record all IPv6 addresses
Write down the IP addresses and MAC addresses on each node in a table for future reference. This will be useful
when we are running programs like ping where we need to know the IPv6 address of the destination node. Knowing
the MAC addresses is useful when we are analyzing packets in the Wireshark protocol analyzer.
In our example, the CORE Network Emulator assigns MAC addresses, in numerical order4, starting with
00:00:00:aa:00:00 and incrementing by one for every other interface attached to a link.
After inspecting each node using either the Observer Widget or the Linux ip command, we generate the following
table: