Hi, vpp experts,
I am trying to configure l2 gre over ipsec. I followed the steps here:
https://docs.fd.io/vpp/16.12/ipsec_gre_doc.html
I hit the following error:
create ipsec: unknown input `gre tunnel src 10.10.10.10 dst...'
My vpp version is v19.08.1-release
It seems on this version the
;output-sa:
> [1] sa 30 (0x1e) spi 300 (0x012c) protocol:esp flags:[tunnel ]
>input-sa:
> [0] sa 20 (0x14) spi 200 (0x00c8) protocol:esp flags:[tunnel
> Protect ]
>
> Regards,
> neale
>
>
> From: on behalf of "Chuan Han via Lists.Fd.Io"
&
Hi, vpp experts,
I am trying to allocate more cores to a phy nic. I want to allocate cores
4,6,8,10 to eth0, and cores 12,14,16,18 to eth1.
cpu {
main-core 2
* # corelist-workers 4,6,8,10,12,14,16,18,20,22 <== This does not work.
vpp crashes when starting. *
corelist-workers
ecause the aesni_mb driver is
> pointing to socket0: vdev crypto_aesni_mb0,socket_id=0.
>
>
>
> George
>
>
>
> *From:* vpp-dev@lists.fd.io *On Behalf Of *Chuan
> Han via Lists.Fd.Io
> *Sent:* Monday, November 04, 2019 10:27 AM
> *To:* vpp-dev
> *C
-10.10.10.10
trace add dpdk-input 10
On Tue, Oct 8, 2019 at 3:23 PM Chuan Han via Lists.Fd.Io wrote:
> Hi, Neale/vpp experts,
>
> Can you help check why the receiving side drops all the incoming pkts
> because of unknown ip protocol?
>
> I looked at TestIpsecGreTebIfEsp, but had no clu
issue.
>
> Regards,
>
> Balaji.
>
>
>
>
>
> *From: * on behalf of "steven luong via Lists.Fd.Io"
>
> *Reply-To: *"Steven Luong (sluong)"
> *Date: *Friday, October 18, 2019 at 10:06 PM
> *To: *"vpp-dev@lists.fd.io"
> *Cc: *"vpp
/x86_64-linux-gnu/libvlib.so.19.08.1
On Mon, Nov 4, 2019 at 10:45 AM Chuan Han via Lists.Fd.Io wrote:
> Here is the gdb vpp core output
>
> (gdb) f
>
>
>
> #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
>
>
>
> 51 in ../sysdeps/unix/sy
; No symbol table info available.
> #11 0x00007ffe3cb01770 in ?? ()
> No symbol table info available.
> #12 0x7f811f6f586f in vlib_unix_main () from
> /usr/lib/x86_64-linux-gnu/libvlib.so.19.08.1
>
> On Mon, Nov 4, 2019 at 10:45 AM Chuan Han via Lists.Fd.Io google@lists.fd.io> w
table info available.
>> #9 0x7f811f6f4416 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libvlib.so.19.08.1
>> No symbol table info available.
>> #10 0x7f811f1cb834 in clib_calljmp () from
>> /usr/lib/x86_64-linux-gnu/libvppinfra.so.19.08.1
>> No symbol table
eback we may have better clue what is wrong…
>
> —
> Damjan
>
>
>
> On 4 Nov 2019, at 18:51, Chuan Han via Lists.Fd.Io <
> chuanhan=google@lists.fd.io> wrote:
>
> All even number cores are on numa 0, which also hosts all nics.
>
> It seems corelist-wo
eorgii
> wrote:
>
>> Hi Chuan, are cores 20 and 22 on socket0 or socket1? If they are on
>> socket1, the application is crashing because the aesni_mb driver is
>> pointing to socket0: vdev crypto_aesni_mb0,socket_id=0.
>>
>>
>>
>> George
>>
>
#4
> > > No locals.
> > > #5 0x7f811f6db793 in ?? () from
> > /usr/lib/x86_64-linux-
> > > gnu/libvlib.so.19.08.1
> > > No symbol table info available.
> > >
le info available.
> > #9 0x00007f811f6f4416 in ?? () from /usr/lib/x86_64-linux-
> > gnu/libvlib.so.19.08.1
> > No symbol table info available.
> > #10 0x7f811f1cb834 in clib_calljmp () from
> > /usr/lib/x86_64-linux-gnu/lib
Ah... I see. That explains everything!
Thanks for catching this.
It will be more helpful to let vpp print more meaningful logs or have
better documentation.
On Thu, Nov 14, 2019 at 7:17 AM Benoit Ganne (bganne)
wrote:
> Hi Chuan,
>
> I took a deeper look at your conf and actually realized
__cnt =
>> > > __set =
>> > > __cnt =
>> > > __set =
>> > > #2 0x55edb4f0ad44 in os_exit ()
>> > > N
tive stack works. it seems
> the issue is related to aes-gcm cipher support in native stack?
> Probably some integration bug between aes-gcm and native stack?
>
> On Tue, Nov 19, 2019 at 10:42 AM Chuan Han via Lists.Fd.Io
> <http://lists.fd.io/> wrote:
>
>> Hi, Damjan,
ven
>
>
>
> *From: * on behalf of "Chuan Han via Lists.Fd.Io"
>
> *Reply-To: *"chuan...@google.com"
> *Date: *Friday, October 18, 2019 at 4:05 PM
> *To: *Chuan Han
> *Cc: *"vpp-dev@lists.fd.io"
> *Subject: *Re: [vpp-dev] Basic l2 brid
Hi, vpp experts,
We are trying to make basic l2 bridge works within vpp.
We have two servers: r230 and r740, each of which has two phy nics. Two
servers are connected via cable. On each server, we bring these two nics
into the same vpp instance and put them into the same l2 bridge. We tried
> If the two nics don’t come up, check if there’s any obvious dpdk error in
> “show log”.
>
> Florin
>
> On Oct 17, 2019, at 4:56 PM, Chuan Han via Lists.Fd.Io <
> chuanhan=google@lists.fd.io> wrote:
>
> I tried disabling autoneg on R740 side. It is not allow
tried to check if same problem exists with DPDK testpmd app?
>
>
> On 18 Oct 2019, at 10:26, Chuan Han via Lists.Fd.Io <
> chuanhan=google@lists.fd.io> wrote:
>
> I cleaned up startup config a bit. I can still see eth0 down.
>
> See attachment for config file a
t 1: link state change event
>
> Port 1: link state change event
>
> r740 log
>
> Press enter to exitx0 - TX RS bit threshold=32
>
> If it is a dpdk bug, what shall I do? Report to dpdk mailing list?
>
> On Fri, Oct 18, 2019 at 11:55
: link state change event
Port 1: link state change event
r740 log
Press enter to exitx0 - TX RS bit threshold=32
If it is a dpdk bug, what shall I do? Report to dpdk mailing list?
On Fri, Oct 18, 2019 at 11:55 AM Chuan Han via Lists.Fd.Io wrote:
>
t;
>
>
> *From: * on behalf of "Damjan Marion via Lists.Fd.Io"
>
> *Reply-To: *"dmar...@me.com"
> *Date: *Wednesday, October 16, 2019 at 5:12 PM
> *To: *"chuan...@google.com"
> *Cc: *"vpp-dev@lists.fd.io"
> *Subject: *Re: [vpp-de
On R230, we have the following. Not sure why eth0 is down. I used the same
setup for L3 routing measurement. Everything worked fine.
vpp# sh hardware-interfaces eth0
NameIdx Link Hardware
eth0 2down eth0
Link speed: unknown
l3 mac mismatch <<<<
> 3 eth1-output interface is down
> 30922 eth0-output interface is down
>
>
>
>
>
> Do u see the arp getting resolved on ixia? The mac on ixia at port with
> 172.16.
metric
>> Advertised auto-negotiation: Yes
>> Advertised FEC modes: Not reported
>> Speed: 1Mb/s
>> Duplex: Full
>> *Port: Twisted Pair*
>> PHYAD: 0
>> Transceiver: internal
>> * Auto-negotia
0 down 0/0/0/0
>
>
>
> On sh error logs on R 230 we see
>
> 1 ethernet-input l3 mac mismatch <<<<
> 3 eth1-output interface is down
> 30922
000/0/0/0 rx
>> packets 30920 <<< packets are received on port 3
>> rx
>> bytes 3679480
>> t
tx
> bytes 3679361
> drops
> 30920 <<< all dropped at port 3
>
> tx-error 3
> local00 down
drops
> 30920 <<< all dropped at port 3
>
> tx-error 3
> local00 down 0/0/0/0
>
> On sh error logs on R 230 we see
>
> 1 ether
Wake-on: g
> Current message level: 0x0007 (7)
> drv probe link
> Link detected: yes
> root@esdn-lab:~/gnxi/perf_testing/r740/vpp#
>
> not clear if this plays a role or not.
>
> On Thu, Oct 17, 2019 at 2:41 PM Chuan
Hi, vpp experts,
I was told that vpp's native ipsec stack is stabler and more performant. We
can enable it by commenting out the vdev line in dpdk stanza.
However, when I did so, ipsec decryption failed.
Ex:
# commenting out this line makes decryption fail.
vdev crypto_aesni_mb0,socket_id=0
I switched cipher from aes-gcm to aes-cbc. native stack works. it seems the
issue is related to aes-gcm cipher support in native stack? Probably some
integration bug between aes-gcm and native stack?
On Tue, Nov 19, 2019 at 10:42 AM Chuan Han via Lists.Fd.Io wrote:
> Hi, Damjan,
>
orithm too.
>
> Thanks,
> Chris.
>
> > On Oct 4, 2019, at 7:23 PM, Chuan Han via Lists.Fd.Io google@lists.fd.io> wrote:
> >
> > Hi,
> >
> > I want to use 256 bit crypto algorithm in my ipsec config.
> >
> > I have something like this:
>
ip-range
> 0.0.0.0-255.255.255.255
> >
> > ipsec policy add spd 1 priority 10 inbound action protect sa 2
> local-ip-range 0.0.0.0-255.255.255.255 remote-ip-range
> 172.16.2.1-172.16.2.255
> > ipsec policy add spd 1 priority 10 outbound action protect sa 1
> local-ip-ra
et loss problems,
>> it helps us debug.
>>
>>
>>
>> For reference the setup for GRE TEB IPSec can be found in the python UT
>> TestIpsecGreTebIfEsp.
>>
>>
>>
>> Regards,
>>
>> neale
>>
>>
>>
>>
>>
d by
> Neale, irrespective of it being in teb mode or not. Neale, please correct
> me if it is not the case.
>
>
>
> Regards,
>
> John
>
>
>
> *From:* vpp-dev@lists.fd.io *On Behalf Of *Chuan
> Han via Lists.Fd.Io
> *Sent:* Wednesday, October 02, 2019 11:32
Hi,
I want to use 256 bit crypto algorithm in my ipsec config.
I have something like this:
ipsec sa add 1 spi 255128 esp tunnel-src 10.10.10.10 tunnel-dst 10.10.10.11
crypto-key 2b7e151628aed2a6abf7158809cf4f3d crypto-alg aes-cbc-256
integ-key 6867666568676665686766656867666568676669 integ-alg
why it’s not working.
>
> Please provide packet traces when you are reporting packet loss problems,
> it helps us debug.
>
>
>
> For reference the setup for GRE TEB IPSec can be found in the python UT
> TestIpsecGreTebIfEsp.
>
>
>
> Regards,
>
> neale
>
>
I am also interested in frr integration with vpp. Could you please share
detailed steps once you figure it out?
On Tue, Feb 25, 2020, 11:34 PM Ray Kinsella wrote:
>
>
> I am not sure how accurate / current the information from the wiki is.
>
> However looks like you are missing the Intel
Yes. It fixes the issue.
On Fri, May 15, 2020 at 4:28 PM Florin Coras wrote:
> Hi Chuan,
>
> Does this [1] fix the issue?
>
> Regards,
> Florin
>
> [1] https://gerrit.fd.io/r/c/vpp/+/27103
>
> On May 15, 2020, at 4:24 PM, Chuan Han via lists.fd.io <
> ch
The following patch is very suspicious.
* a58be82dd vlib: fix unix cli commands crash without session
vppctl works fine at: * 0ef915398 (HEAD) ikev2: use u32 in unformat
On Fri, May 15, 2020 at 4:07 PM Chuan Han via lists.fd.io wrote:
> Hi, vpp team,
>
> It seems vppctl
Hi, vpp team,
It seems vppctl is broken on the master head: 18a86c6e6 g2: fix the g2
build for Ubuntu 20.04
The broken functionality is vppctl single command mode: sudo vppctl
host# vppctl
srv-2-vpp# sh ver
vpp v20.09-rc0~15-g18a86c6e6 built by root on host at 2020-05-15T15:31:41
srv-2-vpp#
Hi, vpp developers,
I think someone may be interested in the following.
If you have an ideal integration of google's OSS-Fuzz with vpp, you will
get upto $20,000 for an ideal integration.
See more details, and how to get started:
Hi, vpp experts,
I was building the latest vpp code on a debian testing based system. I hit
the following errors when running: make install-ext-deps
Package libelf was not found in the pkg-config search path.
Perhaps you should add the directory containing `libelf.pc'
to the
Thanks.
The fix works.
On Thu, Jul 2, 2020 at 2:01 AM Mohsin Kazmi (sykazmi)
wrote:
> Hi Chuan,
>
>
>
> Please find the following fix for it.
>
>
>
> https://gerrit.fd.io/r/c/vpp/+/27760
>
>
>
> It seems that order is issue.
>
>
>
> -br
>
It seems this commit causes the issue.
https://gerrit.fd.io/r/c/vpp/+/27675
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16864): https://lists.fd.io/g/vpp-dev/message/16864
Mute This Topic: https://lists.fd.io/mt/75247302/21656
Group Owner:
Hi, vpp experts,
It is known that intel x710 nic in the kernel will drop lldp pkts by
default.
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e00LJEFCA4
Does anyone know it is also true on vpp? If vpp/dpdk drops, is there a
workaround to disable this feature like in
48 matches
Mail list logo
