On Apr 9, 2013, at 3:11 PM, Karthik Sharma wrote: > #Next we create tap devices on the host machine so we can bind them to > the guests VM's later. > for tap in `seq 1 5`; do > sudo ip tuntap add mode tap lan0-p$tap > done;
I wouldn't necessarily expect tap devices to work. What is on the other end of the tap interface (the userspace end)? (The answer is "nothing".) I *would* expect it to work if you created veth pairs, and added one end to OVS and the other end as a "bridged" adapter to a VirtualBox VM. I haven't actually tested this, though. Usually I'll create a "switch" VM that runs OVS and wire it to the other VMs over VirtualBox "Internal Network" adapters, but this is because I usually use VirtualBox on a Mac (and so can't run OVS in the host environment). > I have installed pox controller running on my HOST pc.I run pox controller to > connect to my host PC as follows. > > ./pox.py log.level --DEBUG forwarding.l2_learning > > The output that I get is as follows > POX 0.1.0 (betta) / Copyright 2011-2013 James McCauley, et al. > DEBUG:core:POX 0.1.0 (betta) going up... > DEBUG:core:Running on CPython (2.7.3/Aug 1 2012 05:14:39) > DEBUG:core:Platform is Linux-3.2.0-38-generic-x86_64-with-Ubuntu-12.04-precise > INFO:core:POX 0.1.0 (betta) is up. > DEBUG:openflow.of_01:Listening on 0.0.0.0:6633 > > It shows listening on 0.0.0.0:6633 ? What is 0.0.0.0 ? 0.0.0.0 means POX is listening for switches to connect on all interfaces, which is how switches usually communicate with controllers. I may have missed it, but I didn't see you mention configuring Open vSwitch to do this. You need something like... ovs-vsctl set-controller lan0 tcp:127.0.0.1:6633 You can use the loopback address because you've got POX running on the same machine as OVS. You could also configure POX to only listen on the loopback address, in which case it'd say "Listening on 127.0.0.1:6633", but listening on all interfaces (the default) should also work. -- Murphy
