ut all nodes: mininet> dump The switch and the two hosts listed can be seen here. If the first character typed into the Mininet Command Line Interface is a host, switch or controller name, the command is executed on that node. Run a command on a host process: mininet> h1 ipconfig -a One can monitor the interface mechanism of the host h1-ethO and loopback(lo). Because of being specific to the network namespace of the other node process, this interface (h1-eth0) is not observed by the default Linux system when ipconfig is executed. Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Simulation on SDN and NFV Models Through Mininet In contrast, by default, the switch runs in the guest network namespace, SO executing a command on the "switch" is the same as running it from a regular/ duplicate terminal: mininet> s1 ipconfig -a This shows when the switch has an interface along with the Virtual Machine's connection out with Ethernet (eth0) for host. To emphasize the fact that the host have isolated network state, run Arp and route on both switch-s1 and host-h1. There is a possibility to place in each host, the switch and controller in its own isolated home/root network namespace, but actually there is no benefit in doing so, unless one wants to duplicate a several number of multiple-controller networks. Mininet offers sustenance for this, which can be seen using the -- -innamespace option. Only network virtualization is there, each host/node processes proof of the processes and directories e.g. display the list of processes which are running through a host process: mininet> h1 ps -a -h This should be exactly same as master network namespace: mininet> s1 ps -a -o Moreover, there is a possibility of using different process spaces with Linux containers, but at present Mininet does not do SO. Having everything run in the "root" process namespace is flexible for debugging/executing, because it allows to see all of the running processes from the console using ps, kill, etc. Test Connectivit