On Tue, Aug 5, 2014 at 6:11 PM, Suresh Krishnan <[email protected]> wrote: > Hi all, > I am trying to run Open vSwitch in userspace and use the VXLAN features. > > I used the following commands to create the bridge and add ports to the > bridge > > /system# ovs-vsctl add-br ovs-br0 > /system# ovs-vsctl set bridge ovs-br0 datapath_type=netdev > /system# ovs-vsctl add-port ovs-br0 eth2 > /system# ovs-vsctl add-port ovs-br0 eth3 > /system# ovs-vsctl add-port ovs-br0 eth4 > /system# ovs-vsctl add-port ovs-br0 eth0 > > Until this point everything seems to be working fine. After this I added a > couple of VXLAN interfaces. > > /system# ovs-vsctl add-port ovs-br0 vxlan1 -- set interface vxlan1 > type=vxlan options:remote_ip=10.121.58.215 options:key=42 > options:dst_port=8472 > > /system# ovs-vsctl add-port ovs-br0 vxlan2 -- set interface vxlan2 > type=vxlan options:remote_ip=10.121.58.216 options:key=44 > options:dst_port=8472 > > Everything seems to be normal in ovs-vsctl but ovs-ofctl does not seem to > show the vxlan ports (ovs-vsctl output and ocs-ofctl output below). > > Looking at the log file (ovs-vswitchd.log below), it seems that Open vSwitch > is looking for the kernel module to be loaded. Does this mean that userspace > open vSwitch does not support VXLAN functionality?
Yes, that's correct. Only the Linux kernel datapath supports tunneling. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
