Hi guys:
I create two vpp instance and create two ipsec tunnel, when ping 10.0.0.1 on 
vpp1, I get a ping error for p2p type interface on vpp master 
(21.01-rc0~548-g5e6d54779).
vpp0 start with vpp0.cli and vpp1 with vpp1.cli. The following is the test 
netowrk topology and vpp1 console output:

> 
> DBGvpp# show version
> vpp v21.01.0-rc0~548 built by dev on localhost.localdomain at
> 2020-12-14T06:00:38
> DBGvpp# sh int addr
> eth0 (up):
> L3 192.168.7.101/24
> ipip0 (up):
> L3 10.0.0.2/24
> local0 (dn):
> DBGvpp# sh int
> Name               Idx    State  MTU (L3/IP4/IP6/MPLS)     Counter        
> Count
> eth0                              1      up          1500/0/0/0     rx
> packets                     2
> rx bytes                     303
> tx packets                     1
> tx bytes                      42
> drops                          2
> ip4                            1
> ipip0                             2      up          1500/0/0/0
> local0                            0     down          0/0/0/0
> DBGvpp# show ipsec
> all           backends      interface     protect       protect-hash  sa  
> spd
> tunnel
> DBGvpp# show ipsec all
> [0] sa 2147483650 (0x80000002) spi 101 (0x00000065) protocol:esp flags:[]
> [1] sa 3221225474 (0xc0000002) spi 100 (0x00000064) protocol:esp
> flags:[inbound ]
> SPD Bindings:
> ipip0 flags:[none]
> output-sa:
> [0] sa 2147483650 (0x80000002) spi 101 (0x00000065) protocol:esp flags:[]
> input-sa:
> [1] sa 3221225474 (0xc0000002) spi 100 (0x00000064) protocol:esp
> flags:[inbound ]
> IPSec async mode: on
> DBGvpp# show ipsec sa 0
> [0] sa 2147483650 (0x80000002) spi 101 (0x00000065) protocol:esp flags:[]
> locks 2
> salt 0x0
> thread-indices [encrypt:-1 decrypt:-1]
> seq 0 seq-hi 0
> last-seq 0 last-seq-hi 0 window
> 0000000000000000000000000000000000000000000000000000000000000000
> crypto alg aes-cbc-128 key 6541686776336961656264656f6f6579
> integrity alg sha-256-96 key
> 6541686776336961656264656f6f65796541686776336961656264656f6f6579
> UDP:[src:0 dst:0]
> packets 0 bytes 0
> DBGvpp# show ipsec sa 1
> [1] sa 3221225474 (0xc0000002) spi 100 (0x00000064) protocol:esp
> flags:[inbound ]
> locks 2
> salt 0x0
> thread-indices [encrypt:-1 decrypt:-1]
> seq 0 seq-hi 0
> last-seq 0 last-seq-hi 0 window
> 0000000000000000000000000000000000000000000000000000000000000000
> crypto alg aes-cbc-128 key 6541686776336961656264656f6f6579
> integrity alg sha-256-96 key
> 6541686776336961656264656f6f65796541686776336961656264656f6f6579
> UDP:[src:0 dst:0]
> packets 0 bytes 0
> DBGvpp# ping 192.168.7.100
> 116 bytes from 192.168.7.100: icmp_seq=1 ttl=64 time=14.4428 ms
> 116 bytes from 192.168.7.100: icmp_seq=2 ttl=64 time=.2747 ms
> Aborted due to a keypress.
> 
> Statistics: 2 sent, 2 received, 0% packet loss
> DBGvpp# ping 192.168.7.100
> 116 bytes from 192.168.7.100: icmp_seq=1 ttl=64 time=14.4428 ms
> 116 bytes from 192.168.7.100: icmp_seq=2 ttl=64 time=.2747 ms
> Aborted due to a keypress.
> 
> Statistics: 2 sent, 2 received, 0% packet loss
> DBGvpp# ping 10.0.0.1 verbose
> Failed: no source address for egress interface
> Failed: no source address for egress interface
> Failed: no source address for egress interface
> Failed: no source address for egress interface
> Failed: no source address for egress interface
> 
> Statistics: 0 sent, 0 received, 0% packet loss
> DBGvpp#
> 

I dig into ping.c and find fib_sas4_get never dealing with p2p interface case.

Attachment: vpp0.cli
Description: Binary data

Attachment: vpp1.cli
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18323): https://lists.fd.io/g/vpp-dev/message/18323
Mute This Topic: https://lists.fd.io/mt/78945723/21656
Mute #vpp:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to