date:20191018

Re: [vpp-dev] Basic l2 bridging does not work

2019-10-18 Thread Damjan Marion via Lists.Fd.Io

What about trying to swap NIC and/or cable? 

> 
> On 18 Oct 2019, at 16:05, Chuan Han  wrote:
> 
> 
> Hi, Damjan,
> 
> It seems the bug is in vpp.
> 
> On R230, vpp shows eth0 is down.
> 
> vpp# sh hardware-interfaces eth0
>   NameIdx   Link  Hardware
> eth0   2down  eth0
>   Link speed: unknown
>   Ethernet address b4:96:91:23:1e:d6
>   Intel 82599
> carrier down
> flags: admin-up promisc pmd rx-ip4-cksum
> rx: queues 2 (max 128), desc 512 (min 32 max 4096 align 8)
> tx: queues 3 (max 64), desc 512 (min 32 max 4096 align 8)
> pci: device 8086:154d subsystem 8086:7b11 address :06:00.01 numa 0
> max rx packet len: 15872
> promiscuous: unicast on all-multicast on
> vlan offload: strip off filter off qinq off
> rx offload avail:  vlan-strip ipv4-cksum udp-cksum tcp-cksum tcp-lro
>macsec-strip vlan-filter vlan-extend jumbo-frame 
> scatter
>security keep-crc
> rx offload active: ipv4-cksum
> tx offload avail:  vlan-insert ipv4-cksum udp-cksum tcp-cksum sctp-cksum
>tcp-tso macsec-insert multi-segs security
> tx offload active: none
> rss avail: ipv4-tcp ipv4-udp ipv4 ipv6-tcp-ex ipv6-udp-ex ipv6-tcp
>ipv6-udp ipv6-ex ipv6
> rss active:none
> tx burst function: (nil)
> rx burst function: ixgbe_recv_pkts_vec
> 
> extended stats:
>   mac local errors   318
> vpp#
> 
> However, the testpmd tool shows it is up.
> 
> testpmd> show port summary 1
> Number of available ports: 2
> Port MAC Address   Name Driver Status   Link
> 1B4:96:91:23:1E:D6 :06:00.1 net_ixgbe  up   1Mbps
> testpmd> 
> 
> Does this prove something wrong on vpp side?
> 
> Thanks.
> Chuan
> 
> On Fri, Oct 18, 2019 at 3:06 PM Chuan Han  wrote:
>> I built testpmd binary on both r740 and r230, and ran the test. I did see 
>> testpmd reports some link status change on r230 server. testpmd report on 
>> r740 is stabler. no status change reported.  
>> 
>> r230 log
>> 
>> Press enter to exit
>> 
>> Port 0: link state change event
>> 
>> Port 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 AM Chuan Han via Lists.Fd.Io 
>>  wrote:
>>> So, it is a dpdk bug?
>>> 
>>> I am new to dpdk/vpp. 
>>> 
>>> How do I run dpdk testpmd? Shall I install dpdk separately on the r230 
>>> server? Are there any steps to follow? 
>>> 
>>> On Fri, Oct 18, 2019 at 10:30 AM Damjan Marion  wrote:
 In this case we are purely relying on link state provided by DPDK.
 Have you tried to check if same problem exists with DPDK testpmd app?
 
 
> On 18 Oct 2019, at 10:26, Chuan Han via Lists.Fd.Io 
>  wrote:
> 
> I cleaned up startup config a bit. I can still see eth0 down. 
> 
> See attachment for config file and log. There are some errors in log, but 
> I am not sure they are worrisome or not. 
> 
> On Thu, Oct 17, 2019 at 5:22 PM Florin Coras  
> wrote:
>> This looks like a DPDK issue, but I’ll let Damjan be the judge of that. 
>> 
>> To see if this is a config issues, could you simplify your startup 
>> config by
>> - removing “workers 0” from the two nics and adding “num-rx-queues 2” to 
>> the nics or to the default stanza, if you’re running with 2 workers
>> - comment out the cryptodev config 
>> 
>> 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 
>>>  wrote:
>>> 
>>> I tried disabling autoneg on R740 side. It is not allowed too. If vpp 
>>> cannot allow two nics to be successfully added to the same vpp 
>>> instance, it seems to be a bug. Is it something which can be easily 
>>> spotted in the code base? 
>>> 
>>> It is also not possible to enforce symmetricity on internet. The other 
>>> party can do anything as long as basic ping works. 
>>> 
>>> On Thu, Oct 17, 2019 at 3:55 PM Chuan Han  wrote:
 If I only put one phy nic, i.e., eth0, to vpp, 'sh hardware' shows it 
 is up. If I put both eth0 and eth1 in vpp, eth0 is always down. It 
 seems something is wrong with the nic or vpp does not support this 
 type of hardware? 
 
 We tried enabling autoneg on R230. It is not allowed. To avoid 
 asymmetric settings, disabling autoneg on R740 will help? 
 
 On Thu, Oct 17, 2019 at 3:46 PM Balaji Venkatraman (balajiv) 
  wrote:
> It plays a role if it is

Re: [vpp-dev] Basic l2 bridging does not work

2019-10-18 Thread Chuan Han via Lists.Fd.Io

Hi, Damjan,

It seems the bug is in vpp.

On R230, vpp shows eth0 is down.

vpp# sh hardware-interfaces eth0
  NameIdx   Link  Hardware
eth0   2down  eth0
  Link speed: unknown


*  Ethernet address b4:96:91:23:1e:d6  Intel 82599carrier down*
flags: admin-up promisc pmd rx-ip4-cksum
rx: queues 2 (max 128), desc 512 (min 32 max 4096 align 8)
tx: queues 3 (max 64), desc 512 (min 32 max 4096 align 8)
pci: device 8086:154d subsystem 8086:7b11 address :06:00.01 numa 0
max rx packet len: 15872
promiscuous: unicast on all-multicast on
vlan offload: strip off filter off qinq off
rx offload avail:  vlan-strip ipv4-cksum udp-cksum tcp-cksum tcp-lro
   macsec-strip vlan-filter vlan-extend jumbo-frame
scatter
   security keep-crc
rx offload active: ipv4-cksum
tx offload avail:  vlan-insert ipv4-cksum udp-cksum tcp-cksum sctp-cksum
   tcp-tso macsec-insert multi-segs security
tx offload active: none
rss avail: ipv4-tcp ipv4-udp ipv4 ipv6-tcp-ex ipv6-udp-ex
ipv6-tcp
   ipv6-udp ipv6-ex ipv6
rss active:none
tx burst function: (nil)
rx burst function: ixgbe_recv_pkts_vec

extended stats:
  mac local errors   318
vpp#

However, the testpmd tool shows it is up.

testpmd> show port summary 1
Number of available ports: 2
Port MAC Address   Name Driver Status   Link
*1B4:96:91:23:1E:D6 :06:00.1 net_ixgbe  up   1Mbps*
testpmd>

Does this prove something wrong on vpp side?

Thanks.
Chuan

On Fri, Oct 18, 2019 at 3:06 PM Chuan Han  wrote:

> I built testpmd binary on both r740 and r230, and ran the test. I did see
> testpmd reports some link status change on r230 server. testpmd report on
> r740 is stabler. no status change reported.
>
> r230 log
> 
> Press enter to exit
>
> Port 0: link state change event
>
> Port 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 AM Chuan Han via Lists.Fd.Io  google@lists.fd.io> wrote:
>
>> So, it is a dpdk bug?
>>
>> I am new to dpdk/vpp.
>>
>> How do I run dpdk testpmd? Shall I install dpdk separately on the r230
>> server? Are there any steps to follow?
>>
>> On Fri, Oct 18, 2019 at 10:30 AM Damjan Marion  wrote:
>>
>>> In this case we are purely relying on link state provided by DPDK.
>>> Have you 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 and log. There are some errors in log,
>>> but I am not sure they are worrisome or not.
>>>
>>> On Thu, Oct 17, 2019 at 5:22 PM Florin Coras 
>>> wrote:
>>>
 This looks like a DPDK issue, but I’ll let Damjan be the judge of that.

 To see if this is a config issues, could you simplify your startup
 config by
 - removing “workers 0” from the two nics and adding “num-rx-queues 2”
 to the nics or to the default stanza, if you’re running with 2 workers
 - comment out the cryptodev config

 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
   wrote:

 I tried disabling autoneg on R740 side. It is not allowed too. If vpp
 cannot allow two nics to be successfully added to the same vpp instance, it
 seems to be a bug. Is it something which can be easily spotted in the code
 base?

 It is also not possible to enforce symmetricity on internet. The other
 party can do anything as long as basic ping works.

 On Thu, Oct 17, 2019 at 3:55 PM Chuan Han  wrote:

> If I only put one phy nic, i.e., eth0, to vpp, 'sh hardware' shows it
> is up. If I put both eth0 and eth1 in vpp, eth0 is always down. It seems
> something is wrong with the nic or vpp does not support this type of
> hardware?
>
> We tried enabling autoneg on R230. It is not allowed. To avoid
> asymmetric settings, disabling autoneg on R740 will help?
>
> On Thu, Oct 17, 2019 at 3:46 PM Balaji Venkatraman (balajiv) <
> bala...@cisco.com> wrote:
>
>> It plays a role if it is asymmetric at both ends. You could enable it
>> at both ends and check.
>>
>> On Oct 17, 2019, at 3:15 PM, Chuan Han  wrote:
>>
>> 
>> I rebooted the r230 machine and found the phy nic corresponding to
>> eth has autoneg off.
>>
>>

Re: [vpp-dev] Basic l2 bridging does not work

2019-10-18 Thread Chuan Han via Lists.Fd.Io

I built testpmd binary on both r740 and r230, and ran the test. I did see
testpmd reports some link status change on r230 server. testpmd report on
r740 is stabler. no status change reported.

r230 log

Press enter to exit

Port 0: link state change event

Port 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 AM Chuan Han via Lists.Fd.Io  wrote:

> So, it is a dpdk bug?
>
> I am new to dpdk/vpp.
>
> How do I run dpdk testpmd? Shall I install dpdk separately on the r230
> server? Are there any steps to follow?
>
> On Fri, Oct 18, 2019 at 10:30 AM Damjan Marion  wrote:
>
>> In this case we are purely relying on link state provided by DPDK.
>> Have you 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 and log. There are some errors in log, but
>> I am not sure they are worrisome or not.
>>
>> On Thu, Oct 17, 2019 at 5:22 PM Florin Coras 
>> wrote:
>>
>>> This looks like a DPDK issue, but I’ll let Damjan be the judge of that.
>>>
>>> To see if this is a config issues, could you simplify your startup
>>> config by
>>> - removing “workers 0” from the two nics and adding “num-rx-queues 2” to
>>> the nics or to the default stanza, if you’re running with 2 workers
>>> - comment out the cryptodev config
>>>
>>> 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
>>>   wrote:
>>>
>>> I tried disabling autoneg on R740 side. It is not allowed too. If vpp
>>> cannot allow two nics to be successfully added to the same vpp instance, it
>>> seems to be a bug. Is it something which can be easily spotted in the code
>>> base?
>>>
>>> It is also not possible to enforce symmetricity on internet. The other
>>> party can do anything as long as basic ping works.
>>>
>>> On Thu, Oct 17, 2019 at 3:55 PM Chuan Han  wrote:
>>>
 If I only put one phy nic, i.e., eth0, to vpp, 'sh hardware' shows it
 is up. If I put both eth0 and eth1 in vpp, eth0 is always down. It seems
 something is wrong with the nic or vpp does not support this type of
 hardware?

 We tried enabling autoneg on R230. It is not allowed. To avoid
 asymmetric settings, disabling autoneg on R740 will help?

 On Thu, Oct 17, 2019 at 3:46 PM Balaji Venkatraman (balajiv) <
 bala...@cisco.com> wrote:

> It plays a role if it is asymmetric at both ends. You could enable it
> at both ends and check.
>
> On Oct 17, 2019, at 3:15 PM, Chuan Han  wrote:
>
> 
> I rebooted the r230 machine and found the phy nic corresponding to eth
> has autoneg off.
>
> root@esdn-relay:~/gnxi/perf_testing/r230# ethtool enp6s0f1
> Settings for enp6s0f1:
> Supported ports: [ FIBRE ]
> Supported link modes:   1baseT/Full
> Supported pause frame use: Symmetric
> Supports auto-negotiation: No
> Supported FEC modes: Not reported
> Advertised link modes:  1baseT/Full
> Advertised pause frame use: Symmetric
> Advertised auto-negotiation: No
> Advertised FEC modes: Not reported
> Speed: 1Mb/s
> Duplex: Full
> *Port: Direct Attach Copper*
> PHYAD: 0
> Transceiver: internal
> *Auto-negotiation: off*
> Supports Wake-on: d
> Wake-on: d
> Current message level: 0x0007 (7)
>drv probe link
> Link detected: yes
> root@esdn-relay:~/gnxi/perf_testing/r230#
>
> On r740, autoneg is on. It is copper.
>
> root@esdn-lab:~/gnxi/perf_testing/r740/vpp# ethtool eno3
> Settings for eno3:
> Supported ports: [ TP ]
> Supported link modes:   100baseT/Full
> 1000baseT/Full
> 1baseT/Full
> Supported pause frame use: Symmetric
> Supports auto-negotiation: Yes
> Supported FEC modes: Not reported
> Advertised link modes:  100baseT/Full
> 1000baseT/Full
> 1baseT/Full
> Advertised pause frame use: Symmetric
> Advertised auto-negotiation: Yes
> Advertised FEC modes: Not reported
> Speed: 1Mb/s
> Duplex: Full
> *Port: Twisted Pair*
> PHYAD: 0
>

Re: [vpp-dev] Basic l2 bridging does not work

2019-10-18 Thread Chuan Han via Lists.Fd.Io

So, it is a dpdk bug?

I am new to dpdk/vpp.

How do I run dpdk testpmd? Shall I install dpdk separately on the r230
server? Are there any steps to follow?

On Fri, Oct 18, 2019 at 10:30 AM Damjan Marion  wrote:

> In this case we are purely relying on link state provided by DPDK.
> Have you 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 and log. There are some errors in log, but
> I am not sure they are worrisome or not.
>
> On Thu, Oct 17, 2019 at 5:22 PM Florin Coras 
> wrote:
>
>> This looks like a DPDK issue, but I’ll let Damjan be the judge of that.
>>
>> To see if this is a config issues, could you simplify your startup config
>> by
>> - removing “workers 0” from the two nics and adding “num-rx-queues 2” to
>> the nics or to the default stanza, if you’re running with 2 workers
>> - comment out the cryptodev config
>>
>> 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
>>   wrote:
>>
>> I tried disabling autoneg on R740 side. It is not allowed too. If vpp
>> cannot allow two nics to be successfully added to the same vpp instance, it
>> seems to be a bug. Is it something which can be easily spotted in the code
>> base?
>>
>> It is also not possible to enforce symmetricity on internet. The other
>> party can do anything as long as basic ping works.
>>
>> On Thu, Oct 17, 2019 at 3:55 PM Chuan Han  wrote:
>>
>>> If I only put one phy nic, i.e., eth0, to vpp, 'sh hardware' shows it is
>>> up. If I put both eth0 and eth1 in vpp, eth0 is always down. It seems
>>> something is wrong with the nic or vpp does not support this type of
>>> hardware?
>>>
>>> We tried enabling autoneg on R230. It is not allowed. To avoid
>>> asymmetric settings, disabling autoneg on R740 will help?
>>>
>>> On Thu, Oct 17, 2019 at 3:46 PM Balaji Venkatraman (balajiv) <
>>> bala...@cisco.com> wrote:
>>>
 It plays a role if it is asymmetric at both ends. You could enable it
 at both ends and check.

 On Oct 17, 2019, at 3:15 PM, Chuan Han  wrote:

 
 I rebooted the r230 machine and found the phy nic corresponding to eth
 has autoneg off.

 root@esdn-relay:~/gnxi/perf_testing/r230# ethtool enp6s0f1
 Settings for enp6s0f1:
 Supported ports: [ FIBRE ]
 Supported link modes:   1baseT/Full
 Supported pause frame use: Symmetric
 Supports auto-negotiation: No
 Supported FEC modes: Not reported
 Advertised link modes:  1baseT/Full
 Advertised pause frame use: Symmetric
 Advertised auto-negotiation: No
 Advertised FEC modes: Not reported
 Speed: 1Mb/s
 Duplex: Full
 *Port: Direct Attach Copper*
 PHYAD: 0
 Transceiver: internal
 *Auto-negotiation: off*
 Supports Wake-on: d
 Wake-on: d
 Current message level: 0x0007 (7)
drv probe link
 Link detected: yes
 root@esdn-relay:~/gnxi/perf_testing/r230#

 On r740, autoneg is on. It is copper.

 root@esdn-lab:~/gnxi/perf_testing/r740/vpp# ethtool eno3
 Settings for eno3:
 Supported ports: [ TP ]
 Supported link modes:   100baseT/Full
 1000baseT/Full
 1baseT/Full
 Supported pause frame use: Symmetric
 Supports auto-negotiation: Yes
 Supported FEC modes: Not reported
 Advertised link modes:  100baseT/Full
 1000baseT/Full
 1baseT/Full
 Advertised pause frame use: Symmetric
 Advertised auto-negotiation: Yes
 Advertised FEC modes: Not reported
 Speed: 1Mb/s
 Duplex: Full
 *Port: Twisted Pair*
 PHYAD: 0
 Transceiver: internal
 *Auto-negotiation: on*
 MDI-X: Unknown
 Supports Wake-on: umbg
 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 Han via Lists.Fd.Io
   wrote:

> Restarting ixia controller does not help. We ended up with both ixia
> ports having '!'.
>
> We are not sure how ixia port plays a role here. eth0 interfaces are
> the interfaces connecting two servers,

[vpp-dev] Memif or vhost interface

2019-10-18 Thread Devis Reagan

Hi Team ,


I am new to VMs and containers . Planing to use VPP and on top of it wanted
to chose either memif(container based) or virtual interface(vhost based)
for my container based or VM based application. Wanted to know which of
these would give good performance (IPv6/IPv4 traffic) Is there any known
limitations among these two .


To test I am planning to put testpmd as my application on vm/container


Thanks in advance!!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14242): https://lists.fd.io/g/vpp-dev/message/14242
Mute This Topic: https://lists.fd.io/mt/35075132/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Basic l2 bridging does not work

2019-10-18 Thread Damjan Marion via Lists.Fd.Io

In this case we are purely relying on link state provided by DPDK.
Have you tried to check if same problem exists with DPDK testpmd app?


> On 18 Oct 2019, at 10:26, Chuan Han via Lists.Fd.Io 
>  wrote:
> 
> I cleaned up startup config a bit. I can still see eth0 down. 
> 
> See attachment for config file and log. There are some errors in log, but I 
> am not sure they are worrisome or not. 
> 
> On Thu, Oct 17, 2019 at 5:22 PM Florin Coras  > wrote:
> This looks like a DPDK issue, but I’ll let Damjan be the judge of that. 
> 
> To see if this is a config issues, could you simplify your startup config by
> - removing “workers 0” from the two nics and adding “num-rx-queues 2” to the 
> nics or to the default stanza, if you’re running with 2 workers
> - comment out the cryptodev config 
> 
> 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  
>> mailto:chuanhan=google@lists.fd.io>> 
>> wrote:
>> 
>> I tried disabling autoneg on R740 side. It is not allowed too. If vpp cannot 
>> allow two nics to be successfully added to the same vpp instance, it seems 
>> to be a bug. Is it something which can be easily spotted in the code base? 
>> 
>> It is also not possible to enforce symmetricity on internet. The other party 
>> can do anything as long as basic ping works. 
>> 
>> On Thu, Oct 17, 2019 at 3:55 PM Chuan Han > > wrote:
>> If I only put one phy nic, i.e., eth0, to vpp, 'sh hardware' shows it is up. 
>> If I put both eth0 and eth1 in vpp, eth0 is always down. It seems something 
>> is wrong with the nic or vpp does not support this type of hardware? 
>> 
>> We tried enabling autoneg on R230. It is not allowed. To avoid asymmetric 
>> settings, disabling autoneg on R740 will help? 
>> 
>> On Thu, Oct 17, 2019 at 3:46 PM Balaji Venkatraman (balajiv) 
>> mailto:bala...@cisco.com>> wrote:
>> It plays a role if it is asymmetric at both ends. You could enable it at 
>> both ends and check. 
>> 
>>> On Oct 17, 2019, at 3:15 PM, Chuan Han >> > wrote:
>>> 
>>> 
>>> I rebooted the r230 machine and found the phy nic corresponding to eth has 
>>> autoneg off. 
>>> 
>>> root@esdn-relay:~/gnxi/perf_testing/r230# ethtool enp6s0f1
>>> Settings for enp6s0f1:
>>> Supported ports: [ FIBRE ]
>>> Supported link modes:   1baseT/Full 
>>> Supported pause frame use: Symmetric
>>> Supports auto-negotiation: No
>>> Supported FEC modes: Not reported
>>> Advertised link modes:  1baseT/Full 
>>> Advertised pause frame use: Symmetric
>>> Advertised auto-negotiation: No
>>> Advertised FEC modes: Not reported
>>> Speed: 1Mb/s
>>> Duplex: Full
>>> Port: Direct Attach Copper
>>> PHYAD: 0
>>> Transceiver: internal
>>> Auto-negotiation: off
>>> Supports Wake-on: d
>>> Wake-on: d
>>> Current message level: 0x0007 (7)
>>>drv probe link
>>> Link detected: yes
>>> root@esdn-relay:~/gnxi/perf_testing/r230# 
>>> 
>>> On r740, autoneg is on. It is copper. 
>>> 
>>> root@esdn-lab:~/gnxi/perf_testing/r740/vpp# ethtool eno3
>>> Settings for eno3:
>>> Supported ports: [ TP ]
>>> Supported link modes:   100baseT/Full 
>>> 1000baseT/Full 
>>> 1baseT/Full 
>>> Supported pause frame use: Symmetric
>>> Supports auto-negotiation: Yes
>>> Supported FEC modes: Not reported
>>> Advertised link modes:  100baseT/Full 
>>> 1000baseT/Full 
>>> 1baseT/Full 
>>> Advertised pause frame use: Symmetric
>>> Advertised auto-negotiation: Yes
>>> Advertised FEC modes: Not reported
>>> Speed: 1Mb/s
>>> Duplex: Full
>>> Port: Twisted Pair
>>> PHYAD: 0
>>> Transceiver: internal
>>> Auto-negotiation: on
>>> MDI-X: Unknown
>>> Supports Wake-on: umbg
>>> 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 Han via Lists.Fd.Io 
>>>  >> > wrote:
>>> Restarting ixia controller does not help. We ended up with both ixia ports 
>>> having '!'. 
>>> 
>>> We are not sure how ixia port plays a role here. eth0 interfaces are the 
>>> interfaces connecting two servers, not to ixia. 
>>> 
>>> On Thu, Oct 17, 2019 at 11:26 AM Balaji Venkatraman (balajiv) 
>>> mailto:bala...@cisco.com>> wrote:
>>> Hi Chuan,
>>> 
>>>

Re: [vpp-dev] Basic l2 bridging does not work

2019-10-18 Thread Chuan Han via Lists.Fd.Io

I cleaned up startup config a bit. I can still see eth0 down.

See attachment for config file and log. There are some errors in log, but I
am not sure they are worrisome or not.

On Thu, Oct 17, 2019 at 5:22 PM Florin Coras  wrote:

> This looks like a DPDK issue, but I’ll let Damjan be the judge of that.
>
> To see if this is a config issues, could you simplify your startup config
> by
> - removing “workers 0” from the two nics and adding “num-rx-queues 2” to
> the nics or to the default stanza, if you’re running with 2 workers
> - comment out the cryptodev config
>
> 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 allowed too. If vpp
> cannot allow two nics to be successfully added to the same vpp instance, it
> seems to be a bug. Is it something which can be easily spotted in the code
> base?
>
> It is also not possible to enforce symmetricity on internet. The other
> party can do anything as long as basic ping works.
>
> On Thu, Oct 17, 2019 at 3:55 PM Chuan Han  wrote:
>
>> If I only put one phy nic, i.e., eth0, to vpp, 'sh hardware' shows it is
>> up. If I put both eth0 and eth1 in vpp, eth0 is always down. It seems
>> something is wrong with the nic or vpp does not support this type of
>> hardware?
>>
>> We tried enabling autoneg on R230. It is not allowed. To avoid asymmetric
>> settings, disabling autoneg on R740 will help?
>>
>> On Thu, Oct 17, 2019 at 3:46 PM Balaji Venkatraman (balajiv) <
>> bala...@cisco.com> wrote:
>>
>>> It plays a role if it is asymmetric at both ends. You could enable it at
>>> both ends and check.
>>>
>>> On Oct 17, 2019, at 3:15 PM, Chuan Han  wrote:
>>>
>>> 
>>> I rebooted the r230 machine and found the phy nic corresponding to eth
>>> has autoneg off.
>>>
>>> root@esdn-relay:~/gnxi/perf_testing/r230# ethtool enp6s0f1
>>> Settings for enp6s0f1:
>>> Supported ports: [ FIBRE ]
>>> Supported link modes:   1baseT/Full
>>> Supported pause frame use: Symmetric
>>> Supports auto-negotiation: No
>>> Supported FEC modes: Not reported
>>> Advertised link modes:  1baseT/Full
>>> Advertised pause frame use: Symmetric
>>> Advertised auto-negotiation: No
>>> Advertised FEC modes: Not reported
>>> Speed: 1Mb/s
>>> Duplex: Full
>>> *Port: Direct Attach Copper*
>>> PHYAD: 0
>>> Transceiver: internal
>>> *Auto-negotiation: off*
>>> Supports Wake-on: d
>>> Wake-on: d
>>> Current message level: 0x0007 (7)
>>>drv probe link
>>> Link detected: yes
>>> root@esdn-relay:~/gnxi/perf_testing/r230#
>>>
>>> On r740, autoneg is on. It is copper.
>>>
>>> root@esdn-lab:~/gnxi/perf_testing/r740/vpp# ethtool eno3
>>> Settings for eno3:
>>> Supported ports: [ TP ]
>>> Supported link modes:   100baseT/Full
>>> 1000baseT/Full
>>> 1baseT/Full
>>> Supported pause frame use: Symmetric
>>> Supports auto-negotiation: Yes
>>> Supported FEC modes: Not reported
>>> Advertised link modes:  100baseT/Full
>>> 1000baseT/Full
>>> 1baseT/Full
>>> Advertised pause frame use: Symmetric
>>> Advertised auto-negotiation: Yes
>>> Advertised FEC modes: Not reported
>>> Speed: 1Mb/s
>>> Duplex: Full
>>> *Port: Twisted Pair*
>>> PHYAD: 0
>>> Transceiver: internal
>>> *Auto-negotiation: on*
>>> MDI-X: Unknown
>>> Supports Wake-on: umbg
>>> 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 Han via Lists.Fd.Io
>>>   wrote:
>>>
 Restarting ixia controller does not help. We ended up with both ixia
 ports having '!'.

 We are not sure how ixia port plays a role here. eth0 interfaces are
 the interfaces connecting two servers, not to ixia.

 On Thu, Oct 17, 2019 at 11:26 AM Balaji Venkatraman (balajiv) <
 bala...@cisco.com> wrote:

> Hi Chuan,
>
>
>
> Could you please try to reset the ixia controller connected to port 4?
>
> I have seen issues with ‘!’ on ixia. Given the carrier on eth0 is
> down, I suspect the ixia port.
>
>
>
> --
>
> Regards,
>
> Balaji.
>
>
>
>
>
> *From: *Chuan Han 
> *Date: *Thursday, October 17, 2019 at 11:09 AM
> *To: *"Balaji Venkatraman (balajiv)"

Re: [vpp-dev] VPP IPSec failed to add SA

2019-10-18 Thread Balaji Venkatraman via Lists.Fd.Io

Perhaps this doc might be useful..

https://docs.fd.io/vpp/19.04/dpdk_crypto_ipsec_doc.html


--
Regards,
Balaji.


From: "Balaji Venkatraman (balajiv)" 
Date: Friday, October 18, 2019 at 8:58 AM
To: "Ying, Ruoyu" , "Neale Ranns (nranns)" 
, "Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at 
Cisco)" , "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

I think the vpp-plugin-core, vpp-plugin-dpdk should carry them:

sudo apt-get install vpp-plugin-core vpp-plugin-dpdk

and confirm the crypto engine is loaded :

show plugins


--
Regards,
Balaji.


From: "Ying, Ruoyu" 
Date: Friday, October 18, 2019 at 8:43 AM
To: "Neale Ranns (nranns)" , "Filip Tehlar -X (ftehlar - 
PANTHEON TECHNOLOGIES at Cisco)" , "Balaji Venkatraman 
(balajiv)" , "vpp-dev@lists.fd.io" 
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Neale,

I’m really new to VPP and can you tell me where’s the plugins you mentioned? 
Thanks a lot.


Best Regards,
Ruoyu

From: vpp-dev@lists.fd.io  On Behalf Of Neale Ranns via 
Lists.Fd.Io
Sent: Friday, October 18, 2019 4:02 PM
To: Ying, Ruoyu ; Filip Tehlar -X (ftehlar - PANTHEON 
TECHNOLOGIES at Cisco) ; Balaji Venkatraman (balajiv) 
; vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyo,

You need to load one of the crypto_* plugins that provide the engine functions.

/neale


From: "Ying, Ruoyu" mailto:ruoyu.y...@intel.com>>
Date: Friday 18 October 2019 at 09:44
To: "Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco)" 
mailto:fteh...@cisco.com>>, "Balaji Venkatraman (balajiv)" 
mailto:bala...@cisco.com>>, "Neale Ranns (nranns)" 
mailto:nra...@cisco.com>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Filip,

I tried them also, but I still get a similar error:
vpp# set crypto handler aes-128-cbc openssl
failed to set engine openssl for aes-128-cbc!
vpp# set crypto handler aes-128-cbc ia32
failed to set engine ia32 for aes-128-cbc!

And the handlers look like this:
vpp# sh crypto handlers
AlgoTypeActive  Candidates
(nil)
des-cbc encrypt
decrypt
3des-cbcencrypt
decrypt
aes-128-cbc encrypt
decrypt
aes-192-cbc encrypt
decrypt
aes-256-cbc encrypt
decrypt
aes-128-ctr encrypt
decrypt
aes-192-ctr encrypt
decrypt
aes-256-ctr encrypt
decrypt
aes-128-gcm aead-encrypt
aead-decrypt
aes-192-gcm aead-encrypt
aead-decrypt
aes-256-gcm aead-encrypt
aead-decrypt
hmac-md5hmac
hmac-sha-1  hmac
hmac-sha-224hmac
hmac-sha-256hmac
hmac-sha-384hmac
hmac-sha-512hmac

Am I setting with the correct command? Thanks a lot.


Best Regards,
Ruoyu



From: Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco) 
mailto:fteh...@cisco.com>>
Sent: Friday, October 18, 2019 3:29 PM
To: Ying, Ruoyu mailto:ruoyu.y...@intel.com>>; Balaji 
Venkatraman (balajiv) mailto:bala...@cisco.com>>; Neale 
Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyu,

Just replace „engine“ with an actual engine name, example:

DBGvpp# show crypto engines
NamePrioDescription
ia32100 Intel IA32 ISA Optimized Crypto
ipsecmb 80  Intel(R) Multi-Buffer Crypto for IPsec Library 
0.52.0
openssl 50  OpenSSL

DBGvpp# set crypto handler aes-128-cbc ia32
DBGvpp#

Filip
[cid:image001.png@01D5860D.6ADCA6C0]
Filip Tehlar
Engineer - Software
fteh...@cisco.com
Tel: +421 2 5825 5068




Cisco Systems, Inc.
Pribinova Street 10 Central 3
BRATISLAVA
81109
Slovakia
cisco.com
[cid:image002.gif@01D5860D.6ADCA6C0]
Think before you print.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here
 for Company Registration Information.


From: vpp-dev@lists.fd.io 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Ying, Ruoyu
Sent: Friday, October 18, 2019 4:29 AM
To: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>; 
Neale Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi

Re: [vpp-dev] VPP IPSec failed to add SA

2019-10-18 Thread Balaji Venkatraman via Lists.Fd.Io

I think the vpp-plugin-core, vpp-plugin-dpdk should carry them:

sudo apt-get install vpp-plugin-core vpp-plugin-dpdk

and confirm the crypto engine is loaded :

show plugins


--
Regards,
Balaji.


From: "Ying, Ruoyu" 
Date: Friday, October 18, 2019 at 8:43 AM
To: "Neale Ranns (nranns)" , "Filip Tehlar -X (ftehlar - 
PANTHEON TECHNOLOGIES at Cisco)" , "Balaji Venkatraman 
(balajiv)" , "vpp-dev@lists.fd.io" 
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Neale,

I’m really new to VPP and can you tell me where’s the plugins you mentioned? 
Thanks a lot.


Best Regards,
Ruoyu

From: vpp-dev@lists.fd.io  On Behalf Of Neale Ranns via 
Lists.Fd.Io
Sent: Friday, October 18, 2019 4:02 PM
To: Ying, Ruoyu ; Filip Tehlar -X (ftehlar - PANTHEON 
TECHNOLOGIES at Cisco) ; Balaji Venkatraman (balajiv) 
; vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyo,

You need to load one of the crypto_* plugins that provide the engine functions.

/neale


From: "Ying, Ruoyu" mailto:ruoyu.y...@intel.com>>
Date: Friday 18 October 2019 at 09:44
To: "Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco)" 
mailto:fteh...@cisco.com>>, "Balaji Venkatraman (balajiv)" 
mailto:bala...@cisco.com>>, "Neale Ranns (nranns)" 
mailto:nra...@cisco.com>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Filip,

I tried them also, but I still get a similar error:
vpp# set crypto handler aes-128-cbc openssl
failed to set engine openssl for aes-128-cbc!
vpp# set crypto handler aes-128-cbc ia32
failed to set engine ia32 for aes-128-cbc!

And the handlers look like this:
vpp# sh crypto handlers
AlgoTypeActive  Candidates
(nil)
des-cbc encrypt
decrypt
3des-cbcencrypt
decrypt
aes-128-cbc encrypt
decrypt
aes-192-cbc encrypt
decrypt
aes-256-cbc encrypt
decrypt
aes-128-ctr encrypt
decrypt
aes-192-ctr encrypt
decrypt
aes-256-ctr encrypt
decrypt
aes-128-gcm aead-encrypt
aead-decrypt
aes-192-gcm aead-encrypt
aead-decrypt
aes-256-gcm aead-encrypt
aead-decrypt
hmac-md5hmac
hmac-sha-1  hmac
hmac-sha-224hmac
hmac-sha-256hmac
hmac-sha-384hmac
hmac-sha-512hmac

Am I setting with the correct command? Thanks a lot.


Best Regards,
Ruoyu



From: Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco) 
mailto:fteh...@cisco.com>>
Sent: Friday, October 18, 2019 3:29 PM
To: Ying, Ruoyu mailto:ruoyu.y...@intel.com>>; Balaji 
Venkatraman (balajiv) mailto:bala...@cisco.com>>; Neale 
Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyu,

Just replace „engine“ with an actual engine name, example:

DBGvpp# show crypto engines
NamePrioDescription
ia32100 Intel IA32 ISA Optimized Crypto
ipsecmb 80  Intel(R) Multi-Buffer Crypto for IPsec Library 
0.52.0
openssl 50  OpenSSL

DBGvpp# set crypto handler aes-128-cbc ia32
DBGvpp#

Filip
[cid:image001.png@01D5860D.6ADCA6C0]
Filip Tehlar
Engineer - Software
fteh...@cisco.com
Tel: +421 2 5825 5068




Cisco Systems, Inc.
Pribinova Street 10 Central 3
BRATISLAVA
81109
Slovakia
cisco.com
[cid:image002.gif@01D5860D.6ADCA6C0]
Think before you print.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here
 for Company Registration Information.


From: vpp-dev@lists.fd.io 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Ying, Ruoyu
Sent: Friday, October 18, 2019 4:29 AM
To: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>; 
Neale Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Balaji,

I checked the docs and tried to set the handler engine. Since there’s no 
example for the command, I’m not sure if I’m setting the right value for 
‘cipher’ here. I tried with different values, but it just returns error msg 
like this:
vpp# set crypto handler aes-128-cbc engine
failed to set engine engine for aes-128-cbc!

vpp# set crypto handler openssl engine
failed

Re: [vpp-dev] VPP IPSec failed to add SA

2019-10-18 Thread Ying, Ruoyu

Hi Neale,

I’m really new to VPP and can you tell me where’s the plugins you mentioned? 
Thanks a lot.


Best Regards,
Ruoyu

From: vpp-dev@lists.fd.io  On Behalf Of Neale Ranns via 
Lists.Fd.Io
Sent: Friday, October 18, 2019 4:02 PM
To: Ying, Ruoyu ; Filip Tehlar -X (ftehlar - PANTHEON 
TECHNOLOGIES at Cisco) ; Balaji Venkatraman (balajiv) 
; vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyo,

You need to load one of the crypto_* plugins that provide the engine functions.

/neale


From: "Ying, Ruoyu" mailto:ruoyu.y...@intel.com>>
Date: Friday 18 October 2019 at 09:44
To: "Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco)" 
mailto:fteh...@cisco.com>>, "Balaji Venkatraman (balajiv)" 
mailto:bala...@cisco.com>>, "Neale Ranns (nranns)" 
mailto:nra...@cisco.com>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Filip,

I tried them also, but I still get a similar error:
vpp# set crypto handler aes-128-cbc openssl
failed to set engine openssl for aes-128-cbc!
vpp# set crypto handler aes-128-cbc ia32
failed to set engine ia32 for aes-128-cbc!

And the handlers look like this:
vpp# sh crypto handlers
AlgoTypeActive  Candidates
(nil)
des-cbc encrypt
decrypt
3des-cbcencrypt
decrypt
aes-128-cbc encrypt
decrypt
aes-192-cbc encrypt
decrypt
aes-256-cbc encrypt
decrypt
aes-128-ctr encrypt
decrypt
aes-192-ctr encrypt
decrypt
aes-256-ctr encrypt
decrypt
aes-128-gcm aead-encrypt
aead-decrypt
aes-192-gcm aead-encrypt
aead-decrypt
aes-256-gcm aead-encrypt
aead-decrypt
hmac-md5hmac
hmac-sha-1  hmac
hmac-sha-224hmac
hmac-sha-256hmac
hmac-sha-384hmac
hmac-sha-512hmac

Am I setting with the correct command? Thanks a lot.


Best Regards,
Ruoyu



From: Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco) 
mailto:fteh...@cisco.com>>
Sent: Friday, October 18, 2019 3:29 PM
To: Ying, Ruoyu mailto:ruoyu.y...@intel.com>>; Balaji 
Venkatraman (balajiv) mailto:bala...@cisco.com>>; Neale 
Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyu,

Just replace „engine“ with an actual engine name, example:

DBGvpp# show crypto engines
NamePrioDescription
ia32100 Intel IA32 ISA Optimized Crypto
ipsecmb 80  Intel(R) Multi-Buffer Crypto for IPsec Library 
0.52.0
openssl 50  OpenSSL

DBGvpp# set crypto handler aes-128-cbc ia32
DBGvpp#

Filip
[cid:image001.png@01D5860D.6ADCA6C0]




Filip Tehlar
Engineer - Software
fteh...@cisco.com
Tel: +421 2 5825 5068










Cisco Systems, Inc.
Pribinova Street 10 Central 3
BRATISLAVA
81109
Slovakia
cisco.com



[cid:image002.gif@01D5860D.6ADCA6C0]

Think before you print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here
 for Company Registration Information.







From: vpp-dev@lists.fd.io 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Ying, Ruoyu
Sent: Friday, October 18, 2019 4:29 AM
To: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>; 
Neale Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Balaji,

I checked the docs and tried to set the handler engine. Since there’s no 
example for the command, I’m not sure if I’m setting the right value for 
‘cipher’ here. I tried with different values, but it just returns error msg 
like this:
vpp# set crypto handler aes-128-cbc engine
failed to set engine engine for aes-128-cbc!

vpp# set crypto handler openssl engine
failed to set engine engine for openssl!

And according to the wiki page here( https://wiki.fd.io/view/VPP/IPSec) that 
there’re three choices for the engines. But I cannot get any of them work ☹. 
Any other clues for registering the engines? Thanks a lot.


Best Regards,
Ruoyu



From: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>
Sent: Friday, October 18, 2019 9:37 AM
To: Ying, Ruoyu mailto:ruoyu.y...@intel.com>>; Neale 
Ranns (nranns)

Re: [vpp-dev] vppcom_session_connect blocking or non blocking

2019-10-18 Thread Florin Coras

Hi Max, 

I had this patch [1] that indirectly fixes the issue lying around. So, is an 
EPOLLOUT | EPOLLHUP event enough to signal a failed async connect for you?

Thanks,
Florin

[1] https://gerrit.fd.io/r/c/vpp/+/22274 

> On Oct 18, 2019, at 2:07 AM, Max A.  wrote:
> 
> Hi Florin,
>  
> vppcom_session_connect in non-blocking mode works well only if the connection 
> can be successfully established. If the connection cannot be established, 
> then no event is raised about this. How can this be fixed?
>  
> Thanks.
> 
>  
> Четверг, 5 сентября 2019, 1:04 +03:00 от Florin Coras 
> :
>  
> Hi Max, 
>  
> Here’s the patch that allows non-blocking connects [1]. 
>  
> Florin
>  
> [1] https://gerrit.fd.io/r/c/vpp/+/21610 
> 
>  
>> On Aug 15, 2019, at 7:41 AM, Florin Coras via Lists.Fd.Io 
>> > >
>>  wrote:
>>  
>> Hi Max,
>> 
>> Not at this time. It should be possible with a few changes for nonblocking 
>> sessions. I’ll add it to my list, in case nobody else beats me to it.
>> 
>> Florin
>>  
>>> 
>>> On Aug 15, 2019, at 2:47 AM, Max A. via Lists.Fd.Io 
>>> >> > 
>>> wrote:
>>> 
>>> Hello,
>>> 
>>> Can vppcom_session_connect() function run in non-blocking mode? I see that 
>>> there is a wait for the connection result in the 
>>> vppcom_wait_for_session_state_change function.  Is it possible to get the 
>>> result of the connection using vppcom_epoll_wait?
>>> 
>>> Thanks.
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> 
>>> View/Reply Online (#13745): https://lists.fd.io/g/vpp-dev/message/13745 
>>> 
>>> Mute This Topic: https://lists.fd.io/mt/32885087/675152 
>>> 
>>> Group Owner: vpp-dev+ow...@lists.fd.io 
>>> 
>>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
>>>   [fcoras.li...@gmail.com 
>>> ]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>> 
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> 
>> View/Reply Online (#13747): https://lists.fd.io/g/vpp-dev/message/13747 
>> 
>> Mute This Topic: https://lists.fd.io/mt/32885087/675152 
>> 
>> Group Owner: vpp-dev+ow...@lists.fd.io 
>> 
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
>>   [fcoras.li...@gmail.com 
>> ]
>> -=-=-=-=-=-=-=-=-=-=-=-
>  
>  
> --
> Max A.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14236): https://lists.fd.io/g/vpp-dev/message/14236
Mute This Topic: https://lists.fd.io/mt/32885087/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] A question about enable AVX512 instruction in VPP

2019-10-18 Thread Damjan Marion via Lists.Fd.Io



On 17 Oct 2019, at 20:02, Zhang Yuwei 
mailto:yuwei1.zh...@intel.com>> wrote:

Hi Dear VPP guys,
I would like to do some investigation about AVX512 instruction 
support in VPP, I saw there are already some implementations but AVX2 is still 
the default option. Could anybody tell me how to enable AVX512 in VPP? 
Appreciate for your kindly help in advance.

There is cli to switch variant for specific node on runtime:

set node function  

i.e. "set node function ethernet-input avx512"

"show node" will tell you which variants exist and which one is currently 
selected.

If you want to change all, you will need to change clib_cpu_march_priority_avx2 
in src/vppinfra/cpu.h...

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14235): https://lists.fd.io/g/vpp-dev/message/14235
Mute This Topic: https://lists.fd.io/mt/34990214/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP core dump with PPPoE

2019-10-18 Thread Neale Ranns via Lists.Fd.Io

Hi Raj,

Thanks for spending the time for further investigation. Some comments inline.

/neale

On 18/10/2019 11:27, "vpp-dev@lists.fd.io on behalf of Raj" 
 wrote:

On Thu, Oct 17, 2019 at 8:45 PM Neale Ranns (nranns)  
wrote:
> I think your analysis is spot on. Thank you!
> How you're a VPP PPPoE expert __ do you have some suggestions on a fix?

Thanks for taking a look at this Neale!

I have some ideas for a fix to this problem.

Alternative 1.

During the packet processing time, get the session information by
using the adj->rewrite_header.sw_if_index . With this approach
fixup_data need not be passed.

+  pppoe_main_t *pem = _main;
+
+  u32 sw_if_index = adj->rewrite_header.sw_if_index;
+  u32 session_id = pem->session_index_by_sw_if_index[sw_if_index];
+  t = pool_elt_at_index (pem->sessions, session_id);

Pros : Without any functin prototype change we can arrive at the solution.
Cons : While processing every pppoe packet, we have to get the session data.

As you say, this is not very D-cache friendly...

Alternative 2.

pppoe build rewrite is done based on rewrite
data(adj->rewrite_header). Here we have a
sw_if_index(adj->rewrite_header.sw_if_index). How is this is different
from the session's encap_if_index? I tried to understand this from
code, but couldn't figure out, if both are the same.

If both are same:
 Fix would be : At the time processing pppoe packet, just use the
'adj->rewrite_header.sw_if_index'.

IIUC adj->rewrite_header.sw_if_index is the index of the PPPoE sub-interface, 
the action of the fixup is to swap the TX interface to the parent Ethernet - 
which is (session)->encap_if_index.

Alternative 3.

As Neale suggested, just push the session's encap_if_index, instead of
passing the const void *.

But this requires some architectural changes, I believe. Because const
void *fixup_data is depended on the function pointer
'adj->sub_type.midchain.fixup_func'. This can bind only during the run
time.

The pointer passed as func_data must remain valid for the lifetime of the 
adjacency (which is the lifetime of the session). That's why i originally used 
the pointer to the session, but as you discovered it reallocs. I would be 
tempted to malloc the fixup data and attach it to the session, that way when 
the session itself reallocs, the fixup data is unaffected.

I have one question regarding pool memory creation:

On each pppoe session addition VPP is resizing the vector pool
pem->sessions. Is it ok if I allocate a fixed number of session
initially?
I am trying to understand the architectural rational behind adding one
element to the vector pool at a time, as opposed to allocating a bulk
number initially.
If it is ok to allocate a large pool initially (preferably taking the
max_sessions from a conf file), we can side step this issue.

Pools don't resize with each allocation, instead they grow by 3/2 times the 
current size each time they fill - this is managed by the underlying vector. 
You can alloc a large number up front, but then you have to play a balancing 
game of how many you need versus how much memory you waste. Plus if we don't 
solve this problem, then the pool can never grow and one would be limited to a 
fixed number of PPPoE sessions - which is not great.

/neale

Thanks and Regards,

Raj

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14234): https://lists.fd.io/g/vpp-dev/message/14234
Mute This Topic: https://lists.fd.io/mt/34298895/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] some questions about libmemif

2019-10-18 Thread Kevin Yan via Lists.Fd.Io

Hi all,
Recently I am reading codes of libmemlif (based on vpp19.01) ,I 
am a little bit confused about the fields of head/tail in struct memif_ring_t 
and last_head/last_tail in struct memif_queue_t.

Can anybody help to  clarify the internal mechanism  of the 
read/write operation of ring and how to move the head/tail and  
last_head/last_tail?  I'd like to better understand this and  really appreciate 
if anyone can help.

BRs,
Kevin

This e-mail message may contain confidential or proprietary information of 
Mavenir Systems, Inc. or its affiliates and is intended solely for the use of 
the intended recipient(s). If you are not the intended recipient of this 
message, you are hereby notified that any review, use or distribution of this 
information is absolutely prohibited and we request that you delete all copies 
in your control and contact us by e-mailing to secur...@mavenir.com. This 
message contains the views of its author and may not necessarily reflect the 
views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor 
email messages, but make no representation that such messages are authorized, 
secure, uncompromised, or free from computer viruses, malware, or other 
defects. Thank You
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14233): https://lists.fd.io/g/vpp-dev/message/14233
Mute This Topic: https://lists.fd.io/mt/35012940/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP core dump with PPPoE

2019-10-18 Thread Raj

On Thu, Oct 17, 2019 at 8:45 PM Neale Ranns (nranns)  wrote:
> I think your analysis is spot on. Thank you!
> How you're a VPP PPPoE expert __ do you have some suggestions on a fix?

Thanks for taking a look at this Neale!

I have some ideas for a fix to this problem.

Alternative 1.

During the packet processing time, get the session information by
using the adj->rewrite_header.sw_if_index . With this approach
fixup_data need not be passed.

+  pppoe_main_t *pem = _main;
+
+  u32 sw_if_index = adj->rewrite_header.sw_if_index;
+  u32 session_id = pem->session_index_by_sw_if_index[sw_if_index];
+  t = pool_elt_at_index (pem->sessions, session_id);

Pros : Without any functin prototype change we can arrive at the solution.
Cons : While processing every pppoe packet, we have to get the session data.

Alternative 2.

pppoe build rewrite is done based on rewrite
data(adj->rewrite_header). Here we have a
sw_if_index(adj->rewrite_header.sw_if_index). How is this is different
from the session's encap_if_index? I tried to understand this from
code, but couldn't figure out, if both are the same.

If both are same:
 Fix would be : At the time processing pppoe packet, just use the
'adj->rewrite_header.sw_if_index'.

Alternative 3.

As Neale suggested, just push the session's encap_if_index, instead of
passing the const void *.

But this requires some architectural changes, I believe. Because const
void *fixup_data is depended on the function pointer
'adj->sub_type.midchain.fixup_func'. This can bind only during the run
time.

I have one question regarding pool memory creation:

On each pppoe session addition VPP is resizing the vector pool
pem->sessions. Is it ok if I allocate a fixed number of session
initially?
I am trying to understand the architectural rational behind adding one
element to the vector pool at a time, as opposed to allocating a bulk
number initially.
If it is ok to allocate a large pool initially (preferably taking the
max_sessions from a conf file), we can side step this issue.

Thanks and Regards,

Raj
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14232): https://lists.fd.io/g/vpp-dev/message/14232
Mute This Topic: https://lists.fd.io/mt/34298895/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] vppcom_session_connect blocking or non blocking

2019-10-18 Thread Max A. via Lists.Fd.Io


Hi Florin,
 
vppcom_session_connect in non-blocking mode works well only if the connection 
can be successfully established. If the connection cannot be established, then 
no event is raised about this. How can this be fixed?
 
Thanks.

  
>Четверг, 5 сентября 2019, 1:04 +03:00 от Florin Coras :
> 
>Hi Max, 
> 
>Here’s the patch that allows non-blocking connects [1]. 
> 
>Florin
> 
>[1]  https://gerrit.fd.io/r/c/vpp/+/21610
> 
>>On Aug 15, 2019, at 7:41 AM, Florin Coras via Lists.Fd.Io < 
>>fcoras.lists=gmail@lists.fd.io > wrote:  
>>Hi Max,
>>
>>Not at this time. It should be possible with a few changes for nonblocking 
>>sessions. I’ll add it to my list, in case nobody else beats me to it.
>>
>>Florin
>>  
>>>On Aug 15, 2019, at 2:47 AM, Max A. via Lists.Fd.Io < 
>>>max1976=mail...@lists.fd.io > wrote:
>>>
>>>Hello,
>>>
>>>Can vppcom_session_connect() function run in non-blocking mode? I see that 
>>>there is a wait for the connection result in the 
>>>vppcom_wait_for_session_state_change function.  Is it possible to get the 
>>>result of the connection using vppcom_epoll_wait?
>>>
>>>Thanks.
>>>-=-=-=-=-=-=-=-=-=-=-=-
>>>Links: You receive all messages sent to this group.
>>>
>>>View/Reply Online (#13745):  https://lists.fd.io/g/vpp-dev/message/13745
>>>Mute This Topic:  https://lists.fd.io/mt/32885087/675152
>>>Group Owner:  vpp-dev+ow...@lists.fd.io
>>>Unsubscribe:  https://lists.fd.io/g/vpp-dev/unsub  [ fcoras.li...@gmail.com ]
>>>-=-=-=-=-=-=-=-=-=-=-=-
>>-=-=-=-=-=-=-=-=-=-=-=-
>>Links: You receive all messages sent to this group.
>>
>>View/Reply Online (#13747):  https://lists.fd.io/g/vpp-dev/message/13747
>>Mute This Topic:  https://lists.fd.io/mt/32885087/675152
>>Group Owner:  vpp-dev+ow...@lists.fd.io
>>Unsubscribe:  https://lists.fd.io/g/vpp-dev/unsub  [ fcoras.li...@gmail.com ]
>>-=-=-=-=-=-=-=-=-=-=-=- 
 
 
--
Max A.
 -=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14231): https://lists.fd.io/g/vpp-dev/message/14231
Mute This Topic: https://lists.fd.io/mt/32885087/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP IPSec failed to add SA

2019-10-18 Thread Neale Ranns via Lists.Fd.Io

Hi Ruoyo,

You need to load one of the crypto_* plugins that provide the engine functions.

/neale

From: "Ying, Ruoyu" 
Date: Friday 18 October 2019 at 09:44
To: "Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco)" 
, "Balaji Venkatraman (balajiv)" , "Neale 
Ranns (nranns)" , "vpp-dev@lists.fd.io" 
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Filip,

I tried them also, but I still get a similar error:
vpp# set crypto handler aes-128-cbc openssl
failed to set engine openssl for aes-128-cbc!
vpp# set crypto handler aes-128-cbc ia32
failed to set engine ia32 for aes-128-cbc!

And the handlers look like this:
vpp# sh crypto handlers
AlgoTypeActive  Candidates
(nil)
des-cbc encrypt
decrypt
3des-cbcencrypt
decrypt
aes-128-cbc encrypt
decrypt
aes-192-cbc encrypt
decrypt
aes-256-cbc encrypt
decrypt
aes-128-ctr encrypt
decrypt
aes-192-ctr encrypt
decrypt
aes-256-ctr encrypt
decrypt
aes-128-gcm aead-encrypt
aead-decrypt
aes-192-gcm aead-encrypt
aead-decrypt
aes-256-gcm aead-encrypt
aead-decrypt
hmac-md5hmac
hmac-sha-1  hmac
hmac-sha-224hmac
hmac-sha-256hmac
hmac-sha-384hmac
hmac-sha-512hmac

Am I setting with the correct command? Thanks a lot.

Best Regards,
Ruoyu

From: Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco) 

Sent: Friday, October 18, 2019 3:29 PM
To: Ying, Ruoyu ; Balaji Venkatraman (balajiv) 
; Neale Ranns (nranns) ; 
vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyu,

Just replace „engine“ with an actual engine name, example:

DBGvpp# show crypto engines
NamePrioDescription
ia32100 Intel IA32 ISA Optimized Crypto
ipsecmb 80  Intel(R) Multi-Buffer Crypto for IPsec Library 
0.52.0
openssl 50  OpenSSL

DBGvpp# set crypto handler aes-128-cbc ia32
DBGvpp#

Filip
[cid:image001.png@01D5859B.228ED9F0]
Filip Tehlar
Engineer - Software
fteh...@cisco.com
Tel: +421 2 5825 5068

Cisco Systems, Inc.
Pribinova Street 10 Central 3
BRATISLAVA
81109
Slovakia
cisco.com
[cid:image002.gif@01D5859B.228ED9F0]
Think before you print.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here
 for Company Registration Information.

From: vpp-dev@lists.fd.io 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Ying, Ruoyu
Sent: Friday, October 18, 2019 4:29 AM
To: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>; 
Neale Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Balaji,

I checked the docs and tried to set the handler engine. Since there’s no 
example for the command, I’m not sure if I’m setting the right value for 
‘cipher’ here. I tried with different values, but it just returns error msg 
like this:
vpp# set crypto handler aes-128-cbc engine
failed to set engine engine for aes-128-cbc!

vpp# set crypto handler openssl engine
failed to set engine engine for openssl!

And according to the wiki page here( https://wiki.fd.io/view/VPP/IPSec) that 
there’re three choices for the engines. But I cannot get any of them work ☹. 
Any other clues for registering the engines? Thanks a lot.

Best Regards,
Ruoyu

From: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>
Sent: Friday, October 18, 2019 9:37 AM
To: Ying, Ruoyu mailto:ruoyu.y...@intel.com>>; Neale 
Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Looking at the docs, I think you need to set one using the:

set crypto handler cipher [cipher2 cipher3 …] engine

Not sure, what’s the default behavior.
--
Regards,
Balaji.

From: mailto:vpp-dev@lists.fd.io>> on behalf of "Ying, 
Ruoyu" mailto:ruoyu.y...@intel.com>>
Date: Thursday, October 17, 2019 at 6:03 PM
To: "Neale Ranns (nranns)" mailto:nra...@cisco.com>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Neale,

Thanks for replying. I think you’ve pointed out the root cause. The cmds 
provides the response like this:
vpp# show crypto

Re: [vpp-dev] VPP IPSec failed to add SA

2019-10-18 Thread Ying, Ruoyu

Hi Filip,

I tried them also, but I still get a similar error:
vpp# set crypto handler aes-128-cbc openssl
failed to set engine openssl for aes-128-cbc!
vpp# set crypto handler aes-128-cbc ia32
failed to set engine ia32 for aes-128-cbc!

And the handlers look like this:
vpp# sh crypto handlers
AlgoTypeActive  Candidates
(nil)
des-cbc encrypt
decrypt
3des-cbcencrypt
decrypt
aes-128-cbc encrypt
decrypt
aes-192-cbc encrypt
decrypt
aes-256-cbc encrypt
decrypt
aes-128-ctr encrypt
decrypt
aes-192-ctr encrypt
decrypt
aes-256-ctr encrypt
decrypt
aes-128-gcm aead-encrypt
aead-decrypt
aes-192-gcm aead-encrypt
aead-decrypt
aes-256-gcm aead-encrypt
aead-decrypt
hmac-md5hmac
hmac-sha-1  hmac
hmac-sha-224hmac
hmac-sha-256hmac
hmac-sha-384hmac
hmac-sha-512hmac

Am I setting with the correct command? Thanks a lot.


Best Regards,
Ruoyu



From: Filip Tehlar -X (ftehlar - PANTHEON TECHNOLOGIES at Cisco) 

Sent: Friday, October 18, 2019 3:29 PM
To: Ying, Ruoyu ; Balaji Venkatraman (balajiv) 
; Neale Ranns (nranns) ; 
vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] VPP IPSec failed to add SA

Hi Ruoyu,

Just replace „engine“ with an actual engine name, example:

DBGvpp# show crypto engines
NamePrioDescription
ia32100 Intel IA32 ISA Optimized Crypto
ipsecmb 80  Intel(R) Multi-Buffer Crypto for IPsec Library 
0.52.0
openssl 50  OpenSSL

DBGvpp# set crypto handler aes-128-cbc ia32
DBGvpp#

Filip
[https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/10_standard_graphic.png]




Filip Tehlar
Engineer - Software
fteh...@cisco.com
Tel: +421 2 5825 5068










Cisco Systems, Inc.
Pribinova Street 10 Central 3
BRATISLAVA
81109
Slovakia
cisco.com



[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]

Think before you print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here
 for Company Registration Information.







From: vpp-dev@lists.fd.io 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Ying, Ruoyu
Sent: Friday, October 18, 2019 4:29 AM
To: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>; 
Neale Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Balaji,

I checked the docs and tried to set the handler engine. Since there’s no 
example for the command, I’m not sure if I’m setting the right value for 
‘cipher’ here. I tried with different values, but it just returns error msg 
like this:
vpp# set crypto handler aes-128-cbc engine
failed to set engine engine for aes-128-cbc!

vpp# set crypto handler openssl engine
failed to set engine engine for openssl!

And according to the wiki page here( https://wiki.fd.io/view/VPP/IPSec) that 
there’re three choices for the engines. But I cannot get any of them work ☹. 
Any other clues for registering the engines? Thanks a lot.


Best Regards,
Ruoyu



From: Balaji Venkatraman (balajiv) mailto:bala...@cisco.com>>
Sent: Friday, October 18, 2019 9:37 AM
To: Ying, Ruoyu mailto:ruoyu.y...@intel.com>>; Neale 
Ranns (nranns) mailto:nra...@cisco.com>>; 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Looking at the docs, I think you need to set one using the:

set crypto handler cipher [cipher2 cipher3 …] engine

Not sure, what’s the default behavior.
--
Regards,
Balaji.


From: mailto:vpp-dev@lists.fd.io>> on behalf of "Ying, 
Ruoyu" mailto:ruoyu.y...@intel.com>>
Date: Thursday, October 17, 2019 at 6:03 PM
To: "Neale Ranns (nranns)" mailto:nra...@cisco.com>>, 
"vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] VPP IPSec failed to add SA

Hi Neale,

Thanks for replying. I think you’ve pointed out the root cause. The cmds 
provides the response like this:
vpp# show crypto engine
No crypto engines registered
vpp# show ipsec backend
IPsec AH backends available:
   Name Index Active
  crypto engine backend   0 yes
IPsec ESP backends available:

Re: [vpp-dev] VPP crash while creating nsh map #vpp #nsh #vxlan-gpe

2019-10-18 Thread Cipher Chen

I tried to run VPP in frontend, and got a little more stack info, not sure if 
that help:

/usr/bin/vpp[10048]: received signal SIGSEGV, PC 0x7f6d686bdb62, faulting 
address 0x7f716924487c
/usr/bin/vpp[10048]: #0  0x7f6d6818ae6a 0x7f6d6818ae6a
/usr/bin/vpp[10048]: #1  0x7f6d67ecd890 0x7f6d67ecd890
/usr/bin/vpp[10048]: #2  0x7f6d686bdb62 l2input_node_fn_avx2 + 0x5e2
/usr/bin/vpp[10048]: #3  0x7f6d68149506 0x7f6d68149506
/usr/bin/vpp[10048]: #4  0x7f6d6814cdbc vlib_main + 0xedc
/usr/bin/vpp[10048]: #5  0x7f6d68189f66 0x7f6d68189f66
/usr/bin/vpp[10048]: #6  0x7f6d67c61834 0x7f6d67c61834
/usr/bin/vpp[10048]: vl_msg_api_trace_save:252: Message table length 36210
Aborted (core dumped)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#14227): https://lists.fd.io/g/vpp-dev/message/14227
Mute This Topic: https://lists.fd.io/mt/34696238/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #nsh: https://lists.fd.io/mk?hashtag=nsh=1480452
Mute #vxlan-gpe: https://lists.fd.io/mk?hashtag=vxlan-gpe=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Basic l2 bridging does not work

Re: [vpp-dev] Basic l2 bridging does not work

Re: [vpp-dev] Basic l2 bridging does not work

Re: [vpp-dev] Basic l2 bridging does not work

[vpp-dev] Memif or vhost interface

Re: [vpp-dev] Basic l2 bridging does not work

Re: [vpp-dev] Basic l2 bridging does not work

Re: [vpp-dev] VPP IPSec failed to add SA

Re: [vpp-dev] VPP IPSec failed to add SA

Re: [vpp-dev] VPP IPSec failed to add SA

Re: [vpp-dev] vppcom_session_connect blocking or non blocking

Re: [vpp-dev] A question about enable AVX512 instruction in VPP

Re: [vpp-dev] VPP core dump with PPPoE

[vpp-dev] some questions about libmemif

Re: [vpp-dev] VPP core dump with PPPoE

Re: [vpp-dev] vppcom_session_connect blocking or non blocking

Re: [vpp-dev] VPP IPSec failed to add SA

Re: [vpp-dev] VPP IPSec failed to add SA

Re: [vpp-dev] VPP crash while creating nsh map #vpp #nsh #vxlan-gpe

19 matches

Site Navigation

Mail list logo

Footer information