Well, Mininet provides a "virtual" network using Linux containers and network namespaces that's suitable for testing. If that's all you want, then yes, it's super easy.
If you're actually trying to network these VirtualBox VMs, then no. -- Murphy On Apr 10, 2013, at 7:32 PM, Karthik Sharma wrote: > And also will installing mininet in this situation make thing easier.I see a > lot of cases where mininet is used in conjunction with POX > > Regards, > Karthik. > > > On 11 April 2013 13:39, Karthik Sharma <[email protected]> wrote: > If I do that on the clients the all the clients are sending out dhcpdiscover > messages.But not getting any responses from > > ./pox.py misc.dhcpd:default running on vm-switch > > Regards, > Karthik. > > > On 11 April 2013 13:33, Murphy McCauley <[email protected]> wrote: > What happens if you run dhclient -v eth0 or whatever on the VMs? > > On Apr 10, 2013 6:30 PM, "Karthik Sharma" <[email protected]> wrote: > Hi > > I don't have a dchp server configured on my network.As explained above it is > 3 network segments intnet-1,intnet-2 and intnet-3 which are connected to > openvswitch.These three internal networks are created using Virtual Box. > > Then I have attached one end of each of these to vm-switch. > >> sudo ovs-vsctl add-port lan0 eth1 >> sudo ovs-vsctl add-port lan0 eth2 >> sudo ovs-vsctl add-port lan0 eth3 >> >> In this situation how does the POX dhcp server work? >> >> I did try runing >> >> ./pox.py log.level --DEBUG misc.dhcpd:default on vm-switch >> >> and tried restarting vm-1 vm-2 and vm-3. >> >> But did not get any response. >> >> As mentioned I think for the dhcp server to work I think there should be a >> common network among the 4 machines which is not true in the above case. >> >> Any thoughts? >> >> Regards, >> Karthik. > > > > > On 11 April 2013 13:01, Murphy McCauley <[email protected]> wrote: > POX doesn't currently support IPv6. (This is mostly because OpenFlow 1.0 > only supports IPv4. IPv6 is being added because Open vSwitch supports it > through an extension and because we're planning to support OpenFlow 1.2. The > first version is almost but not quite complete; it is slated for carp.) > > So this is probably at least a major component of your problem. Use IPv4. > You can either statically configure the addresses, or run dhclient or > whatever on your VMs if your OpenFlow network is connected to a DHCP server. > If it's not, you can use POX's DHCP server. > > Hope that helps. > > -- Murphy > > On Apr 10, 2013, at 4:51 PM, Karthik Sharma wrote: > >> I have 4 virtual Machine (Ubuntu 12.04) running on a host that is also >> running Ubuntu 12.04 >> The Virtual Machines are named as >> >> vm-1 >> vm-2 >> vm-3 >> vm-switch >> >> Below are the network settings on switch-vm >> >> >> Adapter 1: >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-1') >> Adapter 3: >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-2') >> Adapter 4: >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-3') >> >> Network settings on vm-1 >> >> Adapter 1: >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-1') >> >> Network settings on vm-2 >> >> Adapter 1: >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-2') >> >> >> Network settings on vm >> >> Adapter 1: >> Intel PRO/1000 MT Desktop (Bridged adapter, eth0) >> Adapter 2: >> Intel PRO/1000 MT Desktop (Internal network, 'intnet-3') >> >> >> I have installed ovs and pox controller on vm-swtich >> >> sudo ovs-vsctl show >> sudo ovs-vsctl add-br lan0 >> sudo ovs-vsctl add-port lan0 eth1 >> sudo ovs-vsctl add-port lan0 eth2 >> sudo ovs-vsctl add-port lan0 eth3 >> sudo ovs-vsctl set-controller lan0 tcp:127.0.0.1:6633 >> >> ./pox.py log.level --DEBUG forwarding.l2_learning >> >> On another terminal on the vm-switch,I run the following ping6 script. >> >> for i in {1..10} >> do >> echo "pinging vm-1 via eth1" >> ping6 -I eth1 -c 10 fe80::a00:27ff:fed1:9ced >> echo "pinging vm-2 via eth2" >> ping6 -I eth2 -c 10 fe80::a00:27ff:febe:3ae6 >> echo "pinging vm-2 via eth3" >> ping6 -I eth3 -c 10 fe80::a00:27ff:fe92:3e72 >> done >> >> >> where fe80::a00:27ff:fed1:9ced is the link local ipv6 address on (eth0) on >> vm-1 >> fe80::a00:27ff:febe:3ae6 is the link local ipv6 address on (eth0) on >> vm-2 >> fe80::a00:27ff:fe92:3e72 is the link local ipv6 address on (eth0) on >> vm-3 >> >> The ping commands work successfully with 0% packet loss.However >> >> ./pox.py log.level --DEBUG forwarding.l2_learning >> >> doesn't seem to show any output at all. >> >> Is this because I am pinging from switch-vm to vm-1 vm-2 and vm-3 >> >> Instead if I try pinging from vm-1 to vm-2 etc.It is saying destination >> unreachable. >> >> Is this the problem that the appropriate flows are not installed in the POX >> controller? >> If yes is there an easy way to do that? > > > >
