[ovs-dev] Q on ovs-dpdk + Vxlan user space tunneling
danielbenliye at gmail.com
Sun Oct 14 13:19:45 UTC 2018
Let me try to answer your question.
(1) For the first one: I believe NORMAL action can lead the packet to tunnel port.
(2) For how packets flow from br-phy to br-int, You can search code “terminate_native_tunnel()” in ofproto-dpif-xlate.c.
When it generates datapath flow for an incoming tunnel packet, a OVS_ACTION_ATTR_TUNNEL_POP is inserted in the actions.
When the encapsulated packet hit OVS_ACTION_ATTR_TUNNEL_POP action, it will be handled to tunnel port on br-int as a re-injected packet.
Then tunnel headers can be split and delivered to corresponding interface in br-int. When packet sent out from br-int to br-phy, it will hit the tnl_push action which
is added when computing output action (see native_tunnel_output()), then it will use the route you added to send the encapsulated packet from br-phy interface.
(3) That’s a historic issue as it copied from an original guide. I believe your assumption is right.
(4) I don’t try this command, I think more log information in /var/log/openvswitch may be helpful. Hope someone have this answer.
Daniel Benli Ye
> On Oct 14, 2018, at 8:55 PM, Ravi Kerur <rkerur at gmail.com> wrote:
> I am going through following link and setting up the testbed
> and it is very confusing to me at least. Can someone please clarify
> following questions?
> (1) I believe flows needs to be programmed on br-int bridge with
> in_port=vm_port0, out_port=vxlan0, vice-versa. When bridge is created it
> has a default flow with NORMAL action, i don't think this suffices?
> (2) How do packets flow from br-int to br-phy and br-phy to br-int?
> (3) Link says add following route
> "ovs-appctl ovs/route/add 188.8.131.52/24 br-eth1"
> What is br-eth1? I don't see anything about it in the link?
> (4) Assuming br-eth1 is br-phy, I tried to add route on the testbed I
> am configuring I get
> ovs-appctl ovs/route/add 184.108.40.206/32 br1-phy
> Error while inserting route.
> ovs-appctl: ovs-vswitchd: server returned an error
> dev mailing list
> dev at openvswitch.org
More information about the dev