Hi When vxlan is handled in the kernel, what I understand is that the vxlan driver creates a fake socket that listens on the vxlan UDP port. Then the UDP layer looks up for a socket corresponding to the port of an incoming packet, and realizes it's a socket created by a tunnel.
Then pass the vxlan packet to the vxlan driver. Then the vxlan driver decapsulates and because the interface vxlan0 is enslaved to an OVS bridge (br0)... it eventually just passes the inner packet to the OVS bridge which sees a packet arriving from vxlan0. My question is.. what is happening when I have a whole setup in userspace. What happens when I create a userspace vxlan interface in an OVS bridge ? Does the OVS code start automatically checking all packets arriving from any interface into a bridge to match if it's a VXLAN packet it has to decapsulate ? Once the packets are decapsulated, can the packets be matched with in_port= with the ofport of the vxlan0 ? regards, Nicolas _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
