Jon,
BTW, this is caused by a patch to remove interface reuse on VXLAN tunnel
deletion. So it was definitely not from your patch which was previous to this
one. I missed it when I review the patch.
Thanks for finding this and appreciate your help,
John
From: vpp-dev@lists.fd.io
Hi Jon,
I see the problem in the delete path where the hash_unset() call is using the
tunnel instance instead of the user_instance of the tunnel starting at about
line 558 of vxlan.c:
vnet_delete_hw_interface (vnm, t->hw_if_index);
hash_unset (vxm->instance_used, instance);
Do you
John, et al,
I stumbled across this interesting behavior in VXLAN tunnels:
vpp# create vxlan tunnel src 1.2.3.4 dst 10.11.12.13 vni 1 instance 101
vxlan_tunnel101
vpp# create vxlan tunnel src 1.2.3.4 dst 10.11.12.13 vni 1 instance 101 del
vpp# create vxlan tunnel src 1.2.3.4 dst 10.11.12.13 vni
Denis, can you point to specific commands in a Cisco or Juniper Commands
Reference and/or Configuration Guide that you wish to see emulated, and
provide links to publicly available documents?
On Fri, Feb 23, 2018 at 8:13 AM, init via Lists.Fd.Io <
dlotarev=yahoo@lists.fd.io> wrote:
> I think
I think about RADIUS, because this protocol using in huge number of large
routers (such as CISCO, Juniper, etc...)
Another one question about rate-limit policer - is this already implemented to
VPP?
And yes, i dont know who can make a RADIUS plugin to VPP, im not a developer.
Thank
If you want to go in this direction: build a control-plane application. You
could use a variant of the data-plane whitelist/blacklist applet to punt / drop
/ forward traffic from a given source-IP address.
Add a policer to rate-limit punts to what the external application can handle.
Its job
Hi,
@Jdensico sorry this is the mail thread for latest problem.
I am using Latest Qemu 2.11 and since i am using Virsh i updated Libvirt to
latest 3.6.0 (Ubuntu 16.04)ubuntu@ubuntu:~$ virsh -c qemu:///system version
--daemon
setlocale: No such file or directory
Compiled against library:
