Hi Tao,
Sorry, I am not familiar with details of VPP build like you have asked of.
Please wait for anyone else to reply.
Regards,
Hemant
From: Tao Wang
Sent: Wednesday, March 17, 2021 10:02 PM
To: hem...@mnkcg.com; vpp-dev@lists.fd.io
Cc: zhiyong.y...@intel.com; zhongbao@intel
Hi, Hemant
Thanks for your feedback.
It's indeed just like what you described to build vpp.
I know how to build vpp.
Why to choose vpp 20.09 not the latest version? It's just because our project
is set up based on vpp 20.09.
For our case,
1) our project ABC dir hierarchy is like this:
├── ABC
│
Sorry, I figured it out. Each of the four packets incurs a table lookup and
I can add the counter per subscriber on table hit/miss.
Hemant
From: vpp-dev@lists.fd.io On Behalf Of hemant via
lists.fd.io
Sent: Wednesday, March 17, 2021 6:28 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] per su
My VPP plugin has a subscribers table. Say, the number of subscriber in the
table are 100k. I know when the table lookup incurs a hit and I know what
subscriber it is and have uint32_t index to identify the subscriber. In the
plugin's node_inline function, the table is looked up and packets are
f
Hi Vijay,
Please ‘sh fib entry 81’ which, according to the adj on the gre tunnel, is the
FIB entry to reach the next-hop.
/neale
From: Vijay Kumar
Date: Wednesday, 17 March 2021 at 18:48
To: Neale Ranns
Cc: y...@wangsu.com , Vijay Kumar Nagaraj
, vpp-dev@lists.fd.io
Subject: Re: [vpp-dev]
Hi Neale,
I did the configuration exactly like you suggested above. But still the
ping from VPP to the overlay is failing as Blackholed packets.
In my case both gre tunnel created and the teib peer created were in
fib-idx 1. My case is always non-zero fib
Let me know if you tested mgre in non-zer
Re infra: I also pinged the provider to see what might be going on. I think
they are still moving the stuff from one DC to another one so there can be some
isolated glitches... anyway feel free to ping me or Dave if you see anything
odd infra wise.
--a
> On 17 Mar 2021, at 16:08, Ivan Shveduno
Before you start vpp, please run the following commands and show in an example
below. Any interfaces you want to use in VPP must be disabled via ifconfig.
sudo modprobe vfio-pci
sudo ifconfig ens6f0 down
sudo ifconfig ens6f1 down
Hemant
From: vpp-dev@lists.fd.io On Behalf Of
ashish.s
Great, thanks!
On Wed, Mar 17, 2021 at 6:03 PM Florin Coras wrote:
> Infra woes solved so finally merged!
>
> Florin
>
> On Mar 17, 2021, at 6:13 AM, Ivan Shvedunov wrote:
>
> I see CI keeps failing for my patch despite rebase... I have run the tests
> that are failing locally with my patch app
Infra woes solved so finally merged!
Florin
> On Mar 17, 2021, at 6:13 AM, Ivan Shvedunov wrote:
>
> I see CI keeps failing for my patch despite rebase... I have run the tests
> that are failing locally with my patch applied (test_map, test_flowprobe,
> test_memif) and they do pass there. So
Hi All,
We have deployed VPP 21.01 on centos 8.2 VM , and trying to add virtual network
devices (virtio devices) into VPP, but the devices are not accessible in vpp:
vppctl:
vpp# show int address
local0 (dn):
The devices has been removed from the kernel , and are bind with the dpdk
driver:
# dp
I see CI keeps failing for my patch despite rebase... I have run the tests
that are failing locally with my patch applied (test_map, test_flowprobe,
test_memif) and they do pass there. So indeed must be something related to
the test environment
On Tue, Mar 16, 2021 at 7:02 PM Florin Coras wrote:
Which version of vpp is involved?
A while ago, I went to considerable trouble to idiot-proof the vpp timebase
code [vlib_time_now()] against huge time jumps, particularly negative time
jumps. The ntp daemon is perfectly capable of resetting the kernel’s idea of
“now” by an hour or more in e
Can I suggest a few changes. You should consider a mgre interface much like
ethernet when assigning addresses. So it should be;
set interface state eh0 up
set interface ip addr eth0 1.1.1.1/24
create gre tunnel src 1.1.1.1 instance 1 multipoint
set interface state gre1 up
set
set interface state eh0 up
set interface ip addr eth0 1.1.1.1/24
create gre tunnel src 1.1.1.1 instance 1 multipoint
set interface state gre1 up
set interface ip addr gre1 2.1.1.2/32
create teib gre1 peer 3.3.3.3 nh 1.1.1.2
ip route add 3.3.3.3/32 via gre1
create
set interface state eh0 up
set interface ip addr eth0 1.1.1.1/24
create gre tunnel src 1.1.1.1 instance 1 multipoint
set interface state gre1 up
set interface ip addr gre1 2.1.1.2/32
create teib gre1 peer 3.3.3.3 nh 1.1.1.2
ip route add 3.3.3.3/32 via gre1
create
Hi,
I have tw implementation and its working fine for sometime and later the
timer_expired_callback function is not invoked even though the tw node is
getting scheduled.
Detals:
tw_node of type VLIB_NODE_TYPE_INPUT.
Node function calls run_timer_wheels :
run_timer_wheels(vm)
{
tw_timer_wheel_
17 matches
Mail list logo
