Managing networks with OpenFlow
Level 1: There and Back Again
Imagine two hosts connected by a switch (Figure 4). Initially, I won't define a controller and set flow entries manually. To check whether the connection has been established, host 1 uses the CLI in Mininet to ping host 2 (Listing 1). I ping host 2 from host 1:
mininet h1 ping -c 4 h2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.From 10.0.0.1 icmp_seq=1 Destination Host Unreachable[...]
Listing 1
Creating a Network in Mininet
The attempt fails because the switch initially does not forward packets without flow entries and without a controller. The absence of a controller and flow entries is revealed using the dpctl
command, a utility shipped with OpenFlow that provides access to a switch's flow table:
~$ dpctl dump-flows tcp:127.0.0.1:6634 stats_reply (xid=0x6929ef28): flags=none type=1(flow)
dpctl
then sets a flow entry that forwards the incoming packets arriving at port 1 of the switch to port 2:
~$ dpctl add-flowtcp:127.0.0.1:6634 in_port=1,actions=output:2
Again, nothing: The second ping fails because, although the switch forwards packets to host 2, host 2 is not responding.
If you now use dpctl
to create another flow entry that forwards from port 2 to port 1, the results are positive: The two hosts communicate freely through the switch, as long as the idle timeout does not interfere (Listing 2).
Listing 2
A Working Flow Table
Level 2: Where is Arp?
Scenario 2 uses a network structure identical to Scenario 1, but it sends the initial command to ensure that Open vSwitch enters the game as a built-in controller:
sudo mn --topo single,2 --switch ovsk --controller ovsc
The connection test with ping
is immediately successful; the flow table shows three flow entries (Listing 3).
Listing 3
Reading Flow Tables
In addition to the Arp reply, two ICMP requests and replies appear in Listing 3; these requests originate from the flow entry generated by the ping. What happened to the Arp request, which usually comes as a broadcast over the network? If you sniff the control channel, which connects the switch and the controller, using tcpdump or Wireshark, you can determine that the controller has the Arp requests forwarded directly, which does not require a flow entry.
If you use Wireshark with the OpenFlow dissector, which is part of the Mininet image, you can see and analyze the OpenFlow controller's entire communication. Figure 5 shows an example of the handshake between the controller and the switch: The switch uses the Features Reply
to signal to the controller which OpenFlow actions it supports.
Level 3: Tree-Like
In the third and final scenario, Mininet generates a network with a tree topology (Figure 6), in which three hosts each are connected to switches S2 through S4. Mininet then plugs the three switches into an aggregation switch (S1). This topology is typical for networks in companies or data centers. This time, the admin defines a remote controller, assigns an IP address, and sets an OpenFlow standard controller port.
sudo mn --topo tree,depth=2,fanout=3 --mac --switch ovsk--controller=remote,ip=<Controller-IP>,port=6633
The admin can select any computer on the local network and launch a controller (e.g., Floodlight) in the basic configuration:
java -jar floodlight.jar
If Mininet is online, Floodlight detects both the connections to the switches as well as the topology from the console output. Now, you can enter
http://<Controller_IP>:8080/ui/index.html
to launch the Floodlight web user interface and view the switches and hosts that have been detected – the Topology tab presents a graphical display. The graph in Figure 6 might be more functional than pretty, but it is sufficient for an overview.
« Previous 1 2 3 Next »
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Linux Servers Targeted by Akira Ransomware
A group of bad actors who have already extorted $42 million have their sights set on the Linux platform.
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.
-
Canonical Collaborates with Qualcomm on New Venture
This new joint effort is geared toward bringing Ubuntu and Ubuntu Core to Qualcomm-powered devices.
-
Kodi 21.0 Open-Source Entertainment Hub Released
After a year of development, the award-winning Kodi cross-platform, media center software is now available with many new additions and improvements.
-
Linux Usage Increases in Two Key Areas
If market share is your thing, you'll be happy to know that Linux is on the rise in two areas that, if they keep climbing, could have serious meaning for Linux's future.
-
Vulnerability Discovered in xz Libraries
An urgent alert for Fedora 40 has been posted and users should pay attention.
-
Canonical Bumps LTS Support to 12 years
If you're worried that your Ubuntu LTS release won't be supported long enough to last, Canonical has a surprise for you in the form of 12 years of security coverage.
-
Fedora 40 Beta Released Soon
With the official release of Fedora 40 coming in April, it's almost time to download the beta and see what's new.
-
New Pentesting Distribution to Compete with Kali Linux
SnoopGod is now available for your testing needs