On Thu, Apr 30, 2020 at 08:42:04AM -0400, Vasu Dasari wrote: > Hi, > > I am trying to implement a functionality, where in if user specifies port > through which a VxLAN encapsulated packet can be sent out, then use that > port rather than going through routing procedure. > > ovs-vsctl add-port br0 at_vxlan_fp1 -- \ > set int at_vxlan_fp1 type=vxlan \ > options:remote_ip=172.32.2.1 options:local_ip=172.32.2.100 \ > options:dst_mac=00:00:00:00:01:02 options:src_mac=00:00:00:00:01:01 > \ > options:out_port=1 > Why do you need to add dst_mac and src_mac? Usually in the OVS kernel datapath case, OVS will consult the Linux kernel's arp table and get the src/dst mac address. What if the manually set dst_mac here is different than the entry in kernel?
> This would create a fully specified tunnel port, it includes all L2 and L3 > parameters needed to create encapsulated frame. This kind of syntax would > mimic what is supported by off the shelf hardware like Broadcom. I also > noticed that pica8's Openflow switch supports this kind of syntax as > well (Configuring > VXLAN <https://docs.pica8.com/display/PICOS2111cg/Configuring+VXLAN>) > > And the user could create flows of this sort to transport user packets with > VxLAN payload: > > ovs-ofctl add-flow br0 priority=1,in_port=ovs-ap0,actions=at_vxlan_fp1 > ovs-ofctl add-flow br0 priority=1,in_port=at_vxlan_fp1,actions=ovs-ap0 > > > I have initiated a discussion for this kind of request in June, 2019 > at, ovs-discuss > thread > <https://mail.openvswitch.org/pipermail/ovs-discuss/2019-June/048754.html>. > And would like to use this thread for design and any other comments. > > > Please let me know what you think. > > > Thanks > > -Vasu > > > *Vasu Dasari* > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
