Re: [ovs-discuss] VxLAN in Userspace

Flavio, Submitted patch link . Regarding, fdb/set, thanks for your inputs, will think more about that. Probably initiate a separate email thread later. -Vasu *Vasu Dasari* On Wed, Jun 19, 2019 at 9:53 AM Flavio Leitner wrot

Re: [ovs-discuss] VxLAN in Userspace

On Tue, Jun 18, 2019 at 03:12:51PM -0400, Vasu Dasari wrote: > On Tue, Jun 18, 2019 at 12:21 PM Flavio Leitner wrote: > > > On Tue, Jun 18, 2019 at 10:41:16AM -0400, Vasu Dasari wrote: > > > Flavio, > > > > > > The device(could be a regular interface) should have been added to OVS > > with > > >

Re: [ovs-discuss] VxLAN in Userspace

On Tue, Jun 18, 2019 at 12:21 PM Flavio Leitner wrote: > On Tue, Jun 18, 2019 at 10:41:16AM -0400, Vasu Dasari wrote: > > Flavio, > > > > The device(could be a regular interface) should have been added to OVS > with > > "add-port" and when it is removed, ARP entries learnt on it well be > removed

Re: [ovs-discuss] VxLAN in Userspace

On Tue, Jun 18, 2019 at 10:41:16AM -0400, Vasu Dasari wrote: > Flavio, > > The device(could be a regular interface) should have been added to OVS with > "add-port" and when it is removed, ARP entries learnt on it well be removed > as well. Not necessarily. You could have a regular kernel interfac

Re: [ovs-discuss] VxLAN in Userspace

Flavio, The device(could be a regular interface) should have been added to OVS with "add-port" and when it is removed, ARP entries learnt on it well be removed as well. The code is ready. Regarding, testing the code I am planning on extending already existing case where tests are performed to che

Re: [ovs-discuss] VxLAN in Userspace

On Thu, Jun 13, 2019 at 10:58:21PM -0400, Vasu Dasari wrote: > Flavio, > > tnl_neigh_cache_flush(), flushes entire tunnel ARP table. When a bridge is > removed, ARP entries learnt on that bridge alone have to be removed. > Entries from other bridges have to be in tact. > > I am thinking of doing

Re: [ovs-discuss] VxLAN in Userspace

Flavio, tnl_neigh_cache_flush(), flushes entire tunnel ARP table. When a bridge is removed, ARP entries learnt on that bridge alone have to be removed. Entries from other bridges have to be in tact. I am thinking of doing the following: 1. Write a new API in lib/tnl-neigh-cache.c: tnl_neigh_flus

Re: [ovs-discuss] VxLAN in Userspace

Yes Flavio. Looking at code to fix this. Will send fix for review soon. Vasu > On Jun 13, 2019, at 7:15 PM, Flavio Leitner wrote: > >> On Wed, Jun 12, 2019 at 07:18:27PM -0400, Vasu Dasari wrote: >> Thanks Ben. Meanwhile I think I found an bug in OVS 2.9.0 with stale ARP >> entries after a bri

Re: [ovs-discuss] VxLAN in Userspace

On Wed, Jun 12, 2019 at 07:18:27PM -0400, Vasu Dasari wrote: > 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, switc

Re: [ovs-discuss] VxLAN in Userspace

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:~#

Re: [ovs-discuss] VxLAN in Userspace

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? ___

[ovs-discuss] VxLAN in Userspace

Hi, I am running into an issue which sounds pretty basic, probably I might be missing something. Using, OVS: 2.9.0: 1. Created a mininet instance using: mn --topo single,3 2. Converted switch s1 to userspace switch and executed following commands: # Delete controller ovs-vsctl del-c