To do that, start an xterm on h1 and then start Ostinato from inside that xterm
To generate traffic into the switch, we need to run Ostinato inside the host containers, NOT in the root namespace. TX errors 0 dropped 0 overruns 0 carrier 0 collisions ifconfig TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Mininet has several predefined topologies with option to create custom ones. I replaced Xming with VcXsrv and was able to use that successfully. However Qt5 and Xming don’t play nicely (some error about XInput not being supported). I was able to use good ol’ Putty with X11 forwarding successfully.īoth Wireshark and Ostinato are Qt based GUI apps.
UNABLE TO ACCESS WIRESHARK IN MININET THROUGH XQUARTZ WINDOWS
Ostinato is also a GUI app, so will also require X11 forwarding.īut, first a couple of notes about X11 forwarding for those using mininet VM on a Windows host.īoth the native Windows ssh client and WSL ssh client were not able to do X11 forwarding - not sure if they don’t support it or I was doing something incorrect. The VM doesn’t have a desktop environment installed and the recommendation is to use X11 forwarding to run GUI apps like Wireshark. I installed the mininet VM as recommended. I used this opportunity to try mininet out.
It does this using containers (namespaces essentially) and connects them using veth pairs.Īn Ostinato user was trying to use Ostinato with mininet and was not seeing flows on the OVS switch and so reached out to me. Mininet is a Linux based network emulator which creates a network of virtual hosts, switches, controllers, and links all on a single Linux host. I’d heard about mininet off and on, but had never really tried it myself.