Thanks Ben. Meanwhile I think I found an bug in OVS 2.9.0 with stale ARP
entries after a bridge is deleted.
I ran my tunneling experiment successfully. Used mininet to simulate the
environment. After quitting the mininet, switch s1 is deleted. But, I still
see the ARP entries in OVS.
root@mn1:~# ovs-vsctl show
f6af5f1c-a11c-435f-9b03-7317f364ae48
Manager "ptcp:6640"
ovs_version: "2.9.0"
Even thought there is no s1, I still see entries here.
root@mn1:~# ovs-appctl tnl/arp/show
IP MAC Bridge
==========================================================================
172.168.1.1 02:42:ac:14:00:02 s1
172.168.1.2 02:42:ac:14:00:03 s1
10.0.0.10 82:ec:29:c0:bc:ef s1
10.0.0.1 d2:54:11:f0:95:df s1
Just for completeness, this is what I had to do to fix my configuration.
Figured out what was wrong with my configuration.
Modify my bridge s1 to be:
ovs-vsctl --may-exist add-br s1 \
-- set Bridge s1 datapath_type=netdev \
-- set bridge s1 fail-mode=standalone \
other_config:hwaddr=$(cat /sys/class/net/eth1/address)
Add the flows:
ovs-ofctl add-flow s1 "priority=1,in_port=s1-eth1 actions=vxlan"
ovs-ofctl add-flow s1 "priority=1,in_port=vxlan actions=s1-eth1"
ovs-ofctl add-flow s1 "priority=0 actions=NORMAL"
ip addr add 1.1.1.1/24 dev s1
ip link set s1 up
ip addr flush dev eth1 2>/dev/null
ip link set eth1 up
ovs-appctl tnl/arp/set s1 1.1.1.2 00:00:01:00:00:02
*Vasu Dasari*
On Tue, Jun 11, 2019 at 6:22 PM Ben Pfaff <[email protected]> wrote:
> On Tue, Jun 11, 2019 at 03:17:24PM -0400, Vasu Dasari wrote:
> > I am running into an issue which sounds pretty basic, probably I might be
> > missing something.
>
> I think you're trying to use kernel tools to configure userspace
> tunnels. Did you read Documentation/howto/userspace-tunneling.rst?
>
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
