[vpp-dev] IKEV2 Negotiation Failed
Hi guys, We are testing IKEV2. Something run unsuccessfully.The configuration and the information is shown below: configuration: create host-interface name eth0 hw-addr 02:fe:a0:d5:26:62 create host-interface name eth1 hw-addr 02:fe:63:d4:c1:df set interface ip addr host-eth0 192.168.155.11/24 set interface ip addr host-eth1 14.1.1.1/24 set interface state host-eth0 up set interface state host-eth1 up ikev2 profile add pr1 ikev2 profile set pr1 auth shared-key-mic string Vpp123 ikev2 profile set pr1 id local fqdn vpp.home ikev2 profile set pr1 id remote fqdn roadwarrior.vpn.example.com ikev2 profile set pr1 traffic-selector local ip-range 14.1.1.0 - 14.1.1.255 port-range 0 - 65535 protocol 0 ikev2 profile set pr1 traffic-selector remote ip-range 21.1.1.0 - 21.1.1.255 port-range 0 - 65535 protocol 0 Is there anything wrong in my configuration? Failed information: DBGvpp# 0: ikev2_process_sa_init_req:566: ispi 18ee23578923e6c1 rspi 0 nextpayload 21 version 20 exchange 22 flags 8 msgid 0 length 456 0: ikev2_parse_sa_payload:364: proposal num 1 len 44 last_or_more 0 id 1 spi_size 0 num_transforms 4 0: ikev2_parse_sa_payload:406: transform num 0 len 12 last_or_more 3 type encr:aes-cbc-256 id 12 attrs 800e0100 0: ikev2_parse_sa_payload:406: transform num 1 len 8 last_or_more 3 type integ:sha1-96 id 2 0: ikev2_parse_sa_payload:406: transform num 2 len 8 last_or_more 3 type prf:hmac-sha1 id 2 0: ikev2_parse_sa_payload:406: transform num 3 len 8 last_or_more 0 type dh-group:modp-2048 id 14 0: ikev2_parse_notify_payload:464: msg_type NAT_DETECTION_SOURCE_IP len 28 data 60123943d9d1f5645386b64452702ac2c38eab1b 0: ikev2_parse_notify_payload:464: msg_type NAT_DETECTION_DESTINATION_IP len 28 data 36f531a2cf407b56600a5707b42179300aab3660 0: ikev2_parse_notify_payload:464: msg_type SIGNATURE_HASH_ALGORITHMS len 16 data 0001000200030004 0: ikev2_parse_notify_payload:464: msg_type REDIRECT_SUPPORTED len 8 0: ikev2_process_sa_init_req:624: sa state changed to IKEV2_STATE_SA_INIT 0: ikev2_select_proposal:167: bitmap is 1e mandatory is 1e optional is 1e Aborted CAll stack: Program received signal SIGFPE, Arithmetic exception. 0x2b4e9f80 in bn_div_words () from /lib/libcrypto.so.1.0.0 (gdb) bt #0 0x2b4e9f80 in bn_div_words () from /lib/libcrypto.so.1.0.0 #1 0x2b4d8d24 in BN_div () from /lib/libcrypto.so.1.0.0 #2 0x2b4dfd18 in BN_nnmod () from /lib/libcrypto.so.1.0.0 #3 0x2b4e4770 in BN_mod_inverse () from /lib/libcrypto.so.1.0.0 #4 0x2b4eab60 in BN_MONT_CTX_set () from /lib/libcrypto.so.1.0.0 #5 0x2b4eae98 in BN_MONT_CTX_set_locked () from /lib/libcrypto.so.1.0.0 #6 0x2b5191ac in generate_key () from /lib/libcrypto.so.1.0.0 #7 0x2ae26674 in ikev2_generate_dh (sa=0x2b82bb94, t=0x2be390a8) at /home/vpp/build-data/../src/vnet/ipsec/ikev2_crypto.c:410 #8 0x2ae10268 in ikev2_generate_sa_init_data (sa=0x2b82bb94) at /home/vpp/build-data/../src/vnet/ipsec/ikev2.c:368 #9 0x2ae1a28c in ikev2_node_fn (vm=0x2aba0e40, node=0x2bc75340, frame=0x2bf1a500) at /home/vpp/build-data/../src/vnet/ipsec/ikev2.c:2128 #10 0x2ab1d554 in dispatch_node (vm=0x2aba0e40, node=0x2bc75340, type=VLIB_NODE_TYPE_INTERNAL, dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x2bf1a500, last_time_stamp=1320020664777) at /home/vpp/build-data/../src/vlib/main.c:1016 #11 0x2ab1cfa4 in dispatch_pending_node (vm=0x2aba0e40, p=0x2bea84b4, last_time_stamp=1320020664777) at /home/vpp/build-data/../src/vlib/main.c:1162 #12 0x2ab20a94 in vlib_main_or_worker_loop (vm=0x2aba0e40, is_main=1) at /home/vpp/build-data/../src/vlib/main.c:1618 #13 0x2ab1f8cc in vlib_main_loop (vm=0x2aba0e40) at /home/vpp/build-data/../src/vlib/main.c:1638 #14 0x2ab21fc8 in vlib_main (vm=0x2aba0e40, input=0x2b82bfdc) at /home/vpp/build-data/../src/vlib/main.c:1774 #15 0x2ab71688 in thread0 (arg=716836416) at /home/vpp/build-data/../src/vlib/unix/main.c:507 #16 0x2b2c7e18 in clib_calljmp (func=0x2ab7161c , func_arg=716836416, stack=0x2b82c000) at /home/vpp/build-data/../src/vppinfra/mips32_clib_jump.c:24 Backtrace stopped: frame did not save the PC (gdb) In addtion,my vpp version: DBGvpp# show version vpp v17.07-rc0~226-gb5c13fd built by root on ubuntu at Fri May 26 18:07:52 PDT 2017 What should I do to solve the problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale,
These patches you upload have something conflict with the master branch.I
can't add all the patches.
Can I use' git clone https://gerrit.fd.io/r/vpp 'to get the vpp code with your
pathes?
Thanks,
xyxue
From: Neale Ranns (nranns)
Date: 2017-05-31 18:09
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
The MPLS config works for me with:
DBGvpp# sh version
vpp v17.07-rc0~314-g79ea7ec built by vagrant on localhost at Wed May 31
00:46:42 PDT 2017
which is master branch from a few hours ago.
Regards,
neale
Packet 1
00:09:02:603978: af-packet-input
af_packet: hw_if_index 1 next-index 4
tpacket2_hdr:
status 0x2001 len 98 snaplen 98 mac 66 net 80
sec 0x592e95b3 nsec 0x8466a6e vlan 0 vlan_tpid 0
00:09:02:604038: ethernet-input
IP4: 3a:4c:48:ed:59:c3 -> 02:fe:1a:e1:c5:4c
00:09:02:604054: ip4-input
ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
ICMP echo_request checksum 0x1c3e
00:09:02:604062: ip4-lookup
fib 1 dpo-idx 3 flow hash: 0x
ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
ICMP echo_request checksum 0x1c3e
00:09:02:604072: ip4-mpls-label-imposition
mpls-header:[33:63:0:eos]
00:09:02:604081: mpls-midchain
adj-idx 5 : mpls via 0.0.0.0 mpls-tunnel0:
stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0]
via:[43:3784]]
[0] [@6]: mpls-label:[1]:[34:255:0:neos]
[@1]: mpls via 2.1.1.2 host-vcore-link-1:
02feb30a3b6f02fe4eafc6638847 flow hash: 0x
00:09:02:604088: adj-midchain-tx
adj-midchain:[5]:mpls via 0.0.0.0 mpls-tunnel0:
stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0]
via:[43:3784]]
[0] [@6]: mpls-label:[1]:[34:255:0:neos]
[@1]: mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847
00:09:02:604096: mpls-label-imposition
mpls-header:[34:255:0:neos]
00:09:02:604100: mpls-output
adj-idx 4 : mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847
flow hash: 0x
:
0020:
00:09:02:604102: host-vcore-link-1-output
host-vcore-link-1
MPLS: 02:fe:4e:af:c6:63 -> 02:fe:b3:0a:3b:6f
label 34 exp 0, s 0, ttl 255
Packet 2
00:09:02:604968: af-packet-input
af_packet: hw_if_index 2 next-index 4
tpacket2_hdr:
status 0x2001 len 106 snaplen 106 mac 66 net 80
sec 0x592e95b3 nsec 0x84c97da vlan 0 vlan_tpid 0
00:09:02:604978: ethernet-input
MPLS: 02:fe:b3:0a:3b:6f -> 02:fe:4e:af:c6:63
00:09:02:604987: mpls-input
MPLS: next mpls-lookup[1] label 1024 ttl 255
00:09:02:604993: mpls-lookup
MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0
00:09:02:605000: lookup-mpls-dst
fib-index:0 hdr:[1023:63:0:eos] load-balance:33
00:09:02:605005: ip4-mpls-label-disposition
disp:0
00:09:02:605008: lookup-ip4-dst
fib-index:1 addr:192.168.2.20 load-balance:35
00:09:02:605014: ip4-rewrite
tx_sw_if_index 1 dpo-idx 6 : ipv4 via 192.168.2.20 host-vce-link-1:
3a4c48ed59c302fe1ae1c54c0800 flow hash: 0x
: 3a4c48ed59c302fe1ae1c54c08004554e9fd3e010c33c0a80314c0a8
0020: 0214243e07d20010b3952e59311e02001011
00:09:02:605018: host-vce-link-1-output
host-vce-link-1
IP4: 02:fe:1a:e1:c5:4c -> 3a:4c:48:ed:59:c3
ICMP: 192.168.3.20 -> 192.168.2.20
tos 0x00, ttl 62, length 84, checksum 0x0c33
fragment id 0xe9fd
ICMP echo_reply checksum 0x243e
From: 薛欣颖
Date: Wednesday, 31 May 2017 at 08:40
To: "Neale Ranns (nranns)" , vpp-dev
Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale,
The configuration without MPLS:
###VPP1
create host-interface name eth0
create host-interface name eth1
set interface ip table host-eth1 0
set interface ip table host-eth0 1
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set int ip address host-eth0 192.168.3.1/24
set int ip address host-eth1 2.1.1.1/24
ip route add 192.168.2.0/24 via 2.1.1.2
VPP2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface mac address host-eth0 00:50:43:00:02:02
set interface mac address host-eth1 0E:1A:0D:00:50:43
set int ip address host-eth0 192.168.2.1/24
set int ip address host-eth1 2.1.1.2/24
ip route add 192.168.3.0/24 via 2.1.1.1
The configuration with MPLS:
PE1
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-
[vpp-dev] question about mfib
Hi guys,
In the mfib one ingress interface Correspond to multiple egress interface. Then
how can I configure this.
In addtion, a multicast message next hop will be 'next0 =
IP4_INPUT_NEXT_LOOKUP_MULTICAST' and lookup in mfib:
if (PREDICT_FALSE (ip4_address_is_multicast (&ip0->dst_address))) //This
multicast message include 224.0.0.0/8
{
arc0 = lm->mcast_feature_arc_index;
next0 = IP4_INPUT_NEXT_LOOKUP_MULTICAST;
}
else
{
arc0 = lm->ucast_feature_arc_index;
next0 = IP4_INPUT_NEXT_LOOKUP;
if (PREDICT_FALSE (ip0->ttl < 1))
error0 = IP4_ERROR_TIME_EXPIRED;
}
In the fib I can configure a route about 224.0.0.0/8 .In the mfib I can also
configure a route about 224.0.0.5/32 .
When I configure a route about 224.0.0.5/32 in mfib. The multicast message
start with 224 will lookup in mfib. But it will be dropped.
Is that a mistake?
DBGvpp# show ip fib
ipv4-VRF:0, fib_index 0, flow hash: src dst sport dport proto
0.0.0.0/0
unicast-ip4-chain
[@0]: dpo-load-balance: [index:0 buckets:1 uRPF:0 to:[0:0]]
[0] [@0]: dpo-drop ip4
0.0.0.0/32
unicast-ip4-chain
[@0]: dpo-load-balance: [index:1 buckets:1 uRPF:1 to:[0:0]]
[0] [@0]: dpo-drop ip4
1.1.1.0/24
unicast-ip4-chain
[@0]: dpo-load-balance: [index:12 buckets:1 uRPF:11 to:[0:0]]
[0] [@4]: ipv4-glean: host-eth2
1.1.1.1/32
unicast-ip4-chain
[@0]: dpo-load-balance: [index:13 buckets:1 uRPF:12 to:[0:0]]
[0] [@2]: dpo-receive: 1.1.1.1 on host-eth2
224.0.0.0/8
unicast-ip4-chain
[@0]: dpo-load-balance: [index:3 buckets:1 uRPF:3 to:[0:0]]
[0] [@0]: dpo-drop ip4
240.0.0.0/8
unicast-ip4-chain
[@0]: dpo-load-balance: [index:2 buckets:1 uRPF:2 to:[0:0]]
[0] [@0]: dpo-drop ip4
255.255.255.255/32
unicast-ip4-chain
[@0]: dpo-load-balance: [index:4 buckets:1 uRPF:4 to:[0:0]]
[0] [@0]: dpo-drop ip4
In my opinion ,the multicast message which start with 224 is usually the
porotocol message, should not have the same process with the multicast message
start with 225-239.
Please help me point out the problem of my idea.
Thanks,
xyxue
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Questions about IKEV2
Hi guys, I'm testing IKEV2. When I set VPP up as an active negotiation. There is no actively initiate negotiation after command configuration. Has anyone ever seen this appearance? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] some questions about ipsec
Hi guys, I am testing ipsec in vpp. Does VPP support configuring the 16 mask in tunnel mode? When I set the protect range with mask 16 in tunnel mode ，the memory out of bounds will occure。 I've found two places that cause memory out of bounds： 1. the place Evp encryption fill alignment (EVP_EncryptFinal_ex) in esp_encrypt_aes_cbc; 2. the place hmac info is added to the trailing of the message in esp_encrypt_node_fn; Is that a mistake? My configuration is shown below: ipsec sa add 10 spi 1001 esp crypto-alg aes-cbc-128 crypto-key 4a506a794f574265564551694d653768 integ-alg sha1-96 integ-key 4339314b55523947594d6d3547666b45764e6a58 tunnel-src 192.168.153.134 tunnel-dst 192.168.190.141 ipsec sa add 20 spi 1002 esp crypto-alg aes-cbc-128 crypto-key 5a506a794f574265564551694d653768 integ-alg sha1-96 integ-key 5339314b55523947594d6d3547666b45764e6a58 tunnel-src 192.168.190.141 tunnel-dst 192.168.153.134 ipsec spd add 1 set interface ipsec spd host-eth1 1 ipsec policy add spd 1 priority 10 inbound action protect sa 10 local-ip-range 192.168.0.0 - 192.168.255.255 remote-ip-range 192.168.0.0 - 192.168.255.255 ipsec policy add spd 1 priority 10 outbound action protect sa 20 local-ip-range 192.168.0.0 - 192.168.255.255 remote-ip-range 192.168.0.0 - 192.168.255.255 ipsec policy add spd 1 priority 5 inbound action bypass ipsec policy add spd 1 priority 5 outbound action bypass Is there anything wrong with my configuration? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] some information loss in 32-bit system
Hi, The hash_create and hash_get use u64 as key in 64-bit system. In 32-bit system the key will be casting to uword, the high 32 bits of information will be dropped. gm->tunnel_by_key4 = hash_create (0, sizeof (uword)); hash_set (gm->tunnel_by_key4, key4, t - gm->tunnels); p = hash_get (gm->tunnel_by_key4, key4); How should we prevent the loss of information? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] VPLS VPWS problem
Hi Neale, I got the code of master branch. It's a bit different from the patch you uploaded earlier. Does the code of master branch support VPWS and VPLS? Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-05-31 21:02 To: 薛欣颖; vpp-dev Subject: Re: VPLS VPWS problem Hi Xyxue, Works for me with: DBGvpp# sh ver vpp v17.07-rc0~312-g2062ca5 built by vagrant on localhost at Wed May 31 03:29:47 PDT 2017 configs and setup attached. Regards, neale From: 薛欣颖 Date: Wednesday, 31 May 2017 at 10:08 To: "Neale Ranns (nranns)" , vpp-dev Subject: VPLS VPWS problem Hi Neale, We tested VPLS and VPWS ,the result :In VPLS the flow was dropped in L2. In VPWS unable to send and receive messages continuously.Sometimes there is no flow receive/send. MPLS L2VPN VPLS The configuration and trace is shown below: PE1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 PE2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 Is the configuration correctly? DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:04:36:289191: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x9 len 76 snaplen 76 mac 66 net 80 sec 0x2736 nsec 0xb5544e1 vlan 0 00:04:36:291446: ethernet-input IP4: 00:50:43:00:02:02 -> 2c:53:4a:02:91:db 00:04:36:291525: l2-input l2-input: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 00:04:36:291582: l2-learn l2-learn: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291643: l2-fwd l2-fwd: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291673: error-drop l2-fwd: Reflection Drop VPWS The configuration and trace is shown below: VPP1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 VPP2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 show trace VPP1 Packet 3 00:03:05:985952: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 124 snaplen 124 mac 66 net 80 sec 0x5b1f nsec 0x35349da1 vlan 0 00:03:05:986527: ethernet-input IP4: 00:10:94:00:00:04 -> 00:03:7f:ff:ff:ff 00:03:05:986683: l2-input l2-input: sw_if_index 1 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 00:03:05:986805: l2-output l2-output: sw_if_index 3 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 data 08 00 45 c0 00 6e 01 10 00 00 ff fd 00:03:05:986932: mpls-tunnel0-output mpls-tunnel0 : 00037fff00109404080045c0006e0110fffd324ac0a80314c0a8 0020: 021400
[vpp-dev] With SNAT configured, ACL will not work
Hi guys, When I configure SNAT first and then configure ACL, ip4-inacl node doesn't appear , ACl not work. When I configure ACL first and then configure SNAT, ip4-inacl node appear but not work. My configuration about snat is shown below: create host-interface name eth0 hw-addr 00:50:43:00:02:02 create host-interface name eth1 hw-addr 0E:1A:0D:00:50:43 set interface state host-eth0 up set interface state host-eth1 up set dhcp client intfc host-eth1 hostname vppgate set interface snat in host-eth0 out host-eth1 snat add interface address host-eth1 set interface ip addr host-eth0 192.168.2.1/24 classify table mask l3 ip4 dst classify session acl-hit-next deny table-index 0 match l3 ip4 dst 172.16.36.129 set interface input acl intfc host-eth1 ip4-table 0 The trace : Packet 3 00:12:29:629116: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 83 snaplen 83 mac 66 net 80 sec 0x31b nsec 0x1adb20 vlan 0 00:12:29:629397: ethernet-input IP4: 84:b2:61:dc:69:d5 -> 0e:1a:0d:00:50:43 00:12:29:629456: ip4-input UDP: 10.19.8.15 -> 172.16.36.129 tos 0x00, ttl 126, length 69, checksum 0xe79f fragment id 0x7255 UDP: 53 -> 39248 length 49, checksum 0x1e02 00:12:29:629517: snat-out2in SNAT_OUT2IN: sw_if_index 2, next index 1, session index 87 00:12:29:629593: ip4-lookup fib 0 dpo-idx 8 flow hash: 0x UDP: 10.19.8.15 -> 192.168.2.50 tos 0x00, ttl 126, length 69, checksum 0xf556 fragment id 0x7255 UDP: 53 -> 61590 length 49, checksum 0x 00:12:29:629654: ip4-rewrite tx_sw_if_index 3 dpo-idx 8 : ipv4 via 0.0.0.0 pppoe0: 2c534a039342005043000202886411010021 flow hash: 0x : 2c534a039342005043000202886411010021454572557d11 0020: f6560a13080fc0a802320035f0960031acfe81820001 00:12:29:629688: pppoe0-output pppoe0 PPPOE 0x0050, version 0x02, type 0x0c 00:12:29:629744: pppoe0-tx PPPOE: session 1 len 71 tx_sw_index 1 00:12:29:629784: host-eth0-output host-eth0 PPPOE_SESSION: 00:50:43:00:02:02 -> 2c:53:4a:03:93:42 PPPOE ip4 How can I solve the problem? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] VPLS VPWS problem
Hi Neale, About https://gerrit.fd.io/r/#/c/6861/. What will you do with it later? Thanks, Xyxue From: xyxue Date: 2017-06-26 19:32 To: nranns; vpp-dev Subject: Re: Re: VPLS VPWS problem Hi Neale, I got the code of master branch. It's a bit different from the patch you uploaded earlier. Does the code of master branch support VPWS and VPLS? Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-05-31 21:02 To: 薛欣颖; vpp-dev Subject: Re: VPLS VPWS problem Hi Xyxue, Works for me with: DBGvpp# sh ver vpp v17.07-rc0~312-g2062ca5 built by vagrant on localhost at Wed May 31 03:29:47 PDT 2017 configs and setup attached. Regards, neale From: 薛欣颖 Date: Wednesday, 31 May 2017 at 10:08 To: "Neale Ranns (nranns)" , vpp-dev Subject: VPLS VPWS problem Hi Neale, We tested VPLS and VPWS ,the result :In VPLS the flow was dropped in L2. In VPWS unable to send and receive messages continuously.Sometimes there is no flow receive/send. MPLS L2VPN VPLS The configuration and trace is shown below: PE1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 PE2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 Is the configuration correctly? DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:04:36:289191: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x9 len 76 snaplen 76 mac 66 net 80 sec 0x2736 nsec 0xb5544e1 vlan 0 00:04:36:291446: ethernet-input IP4: 00:50:43:00:02:02 -> 2c:53:4a:02:91:db 00:04:36:291525: l2-input l2-input: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 00:04:36:291582: l2-learn l2-learn: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291643: l2-fwd l2-fwd: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291673: error-drop l2-fwd: Reflection Drop VPWS The configuration and trace is shown below: VPP1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 VPP2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 show trace VPP1 Packet 3 00:03:05:985952: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 124 snaplen 124 mac 66 net 80 sec 0x5b1f nsec 0x35349da1 vlan 0 00:03:05:986527: ethernet-input IP4: 00:10:94:00:00:04 -> 00:03:7f:ff:ff:ff 00:03:05:986683: l2-input l2-input: sw_if_index 1 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 00:03:05:986805: l2-output l2-output: sw_if_index 3 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 data 08 00 45 c0 00 6e 01 10 00 00 ff fd 00:03:05:986932: mpls-tunnel0-
[vpp-dev] test command
Hi， Can these two commands(test http server 、 test tcp server) be configured together? When I configure the two commands at the same time, there is a multiple registrations shown below： DBGvpp# test tcp server DBGvpp# test http server 0: vl_msg_api_config:682: BUG: multiple registrations of 'vl_api_memclnt_create_reply_t_handler' What should I do to slove it? Thanks， Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] memmove fault
Hi, When I failed to configure a command, then click the up key , there is a Segmentation fault(not every time): Program received signal SIGSEGV, Segmentation fault. __memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664 1664../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S: No such file or directory. (gdb) bt #0 __memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664 #1 0x77966f56 in unix_cli_line_process_one (cm=0x77ba4960 , um=0x77ba7dc0 , cf=0x7fffb5de5b3c, uf=0x7fffb5de5ae0, input=102 'f', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2063 #2 0x77967548 in unix_cli_line_edit (cm=0x77ba4960 , um=0x77ba7dc0 , cf=0x7fffb5de5b3c) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2152 #3 0x77967880 in unix_cli_process_input (cm=0x77ba4960 , cli_file_index=0) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2192 #4 0x7796844b in unix_cli_process (vm=0x77ba7560 , rt=0x7fffb5e7, f=0x0) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2318 #5 0x7792a320 in vlib_process_bootstrap (_a=140736239921232) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1274 #6 0x7696fd4c in clib_calljmp () at /home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/longjmp.S:128 #7 0x7fffb5966820 in ?? () #8 0x7792a455 in vlib_process_startup (vm=0x7795e1e9 , p=0x7fffb5966880, f=0xedcb4a35d968b00) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1299 Backtrace stopped: previous frame inner to this frame (corrupt stack?) How should we solve this problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Compile error
Hi， I got code by ： git clone https://gerrit.fd.io/r/vpp. input ‘make dpdk-install-dev’ the error infomation is shown below： Building IPSec-MB 0.46 library make[5]: Entering directory `/home/vpp_communication/vpp/dpdk' mkdir -p /home/vpp_communication/vpp/dpdk/deb/debian/tmp/usr/lib/ # Do not build GCM stuff if we are building ISA_L make -C /home/vpp_communication/vpp/dpdk/deb/_build/intel-ipsec-mb-0.46 -j NO_GCM=n make: Entering an unknown directory make: *** /home/vpp_communication/vpp/dpdk/deb/_build/intel-ipsec-mb-0.46: No such file or directory. Stop. make: Leaving an unknown directory make[5]: *** [build-ipsec-mb] Error 2 make[5]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[4]: *** [override_dh_install] Error 2 make[4]: Leaving directory `/home/vpp_communication/vpp/dpdk/deb' make[3]: *** [binary] Error 2 make[3]: Leaving directory `/home/vpp_communication/vpp/dpdk/deb' dpkg-buildpackage: error: debian/rules binary gave error exit status 2 make[2]: *** [vpp-dpdk-dev_17.08-vpp1_amd64.deb] Error 2 make[2]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[1]: *** [install-deb] Error 2 make[1]: Leaving directory `/home/vpp_communication/vpp/dpdk' make: *** [dpdk-install-dev] Error 2 input ‘make build-release’，the error information is shown below： Making object file obj/mb_mgr_hmac_sha_224_submit_avx.o nasm -o obj/mb_mgr_hmac_sha_224_submit_avx.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ avx/mb_mgr_hmac_sha_224_submit_avx.asm Making object file obj/mb_mgr_hmac_sha_224_submit_avx2.o Making object file obj/mb_mgr_hmac_sha_224_submit_avx512.o nasm -o obj/mb_mgr_hmac_sha_224_submit_avx2.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ avx2/mb_mgr_hmac_sha_224_submit_avx2.asm nasm -o obj/mb_mgr_hmac_sha_224_submit_avx512.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ avx512/mb_mgr_hmac_sha_224_submit_avx512.asm mb_mgr_hmac_sha_256_submit_avx512.asm:170: error: parser: instruction expected mb_mgr_hmac_sha_256_submit_avx512.asm:171: error: symbol `vmovdqu32' redefined mb_mgr_hmac_sha_256_submit_avx512.asm:171: error: parser: instruction expected Making object file obj/mb_mgr_hmac_sha_224_submit_sse.o nasm -o obj/mb_mgr_hmac_sha_224_submit_sse.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ sse/mb_mgr_hmac_sha_224_submit_sse.asm -- make[4]: *** [obj/mb_mgr_hmac_sha_224_submit_avx512.o] Error 1 make[4]: *** Waiting for unfinished jobs -- -- -- make[4]: Leaving directory `/home/vpp_communication/vpp/build-root/build-vpp-native/dpdk/intel-ipsec-mb-0.46' make[3]: *** [build-ipsec-mb] Error 2 make[3]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[2]: *** [ebuild-install] Error 2 make[2]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[1]: *** [dpdk-install] Error 2 make[1]: Leaving directory `/home/vpp_communication/vpp/build-root' make: *** [build-release] Error 2 root@ubuntu:/home/vpp_communication/vpp# Is this a problem ? How can I solve it? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Compile error
Hi Sergio, I have run 'make install-dep'. The nasm version is 2.10.09. Thanks, xyxue From: Sergio Gonzalez Monroy Date: 2017-09-05 16:24 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] Compile error Hi, Have you run 'make install-dep' ? Which nasm version do you have in your system? Thanks, Sergio On 04/09/2017 11:59, 薛欣颖 wrote: Hi， I got code by ： git clone https://gerrit.fd.io/r/vpp. input ‘make dpdk-install-dev’ the error infomation is shown below： Building IPSec-MB 0.46 library make[5]: Entering directory `/home/vpp_communication/vpp/dpdk' mkdir -p /home/vpp_communication/vpp/dpdk/deb/debian/tmp/usr/lib/ # Do not build GCM stuff if we are building ISA_L make -C /home/vpp_communication/vpp/dpdk/deb/_build/intel-ipsec-mb-0.46 -j NO_GCM=n make: Entering an unknown directory make: *** /home/vpp_communication/vpp/dpdk/deb/_build/intel-ipsec-mb-0.46: No such file or directory. Stop. make: Leaving an unknown directory make[5]: *** [build-ipsec-mb] Error 2 make[5]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[4]: *** [override_dh_install] Error 2 make[4]: Leaving directory `/home/vpp_communication/vpp/dpdk/deb' make[3]: *** [binary] Error 2 make[3]: Leaving directory `/home/vpp_communication/vpp/dpdk/deb' dpkg-buildpackage: error: debian/rules binary gave error exit status 2 make[2]: *** [vpp-dpdk-dev_17.08-vpp1_amd64.deb] Error 2 make[2]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[1]: *** [install-deb] Error 2 make[1]: Leaving directory `/home/vpp_communication/vpp/dpdk' make: *** [dpdk-install-dev] Error 2 input ‘make build-release’，the error information is shown below： Making object file obj/mb_mgr_hmac_sha_224_submit_avx.o nasm -o obj/mb_mgr_hmac_sha_224_submit_avx.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ avx/mb_mgr_hmac_sha_224_submit_avx.asm Making object file obj/mb_mgr_hmac_sha_224_submit_avx2.o Making object file obj/mb_mgr_hmac_sha_224_submit_avx512.o nasm -o obj/mb_mgr_hmac_sha_224_submit_avx2.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ avx2/mb_mgr_hmac_sha_224_submit_avx2.asm nasm -o obj/mb_mgr_hmac_sha_224_submit_avx512.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ avx512/mb_mgr_hmac_sha_224_submit_avx512.asm mb_mgr_hmac_sha_256_submit_avx512.asm:170: error: parser: instruction expected mb_mgr_hmac_sha_256_submit_avx512.asm:171: error: symbol `vmovdqu32' redefined mb_mgr_hmac_sha_256_submit_avx512.asm:171: error: parser: instruction expected Making object file obj/mb_mgr_hmac_sha_224_submit_sse.o nasm -o obj/mb_mgr_hmac_sha_224_submit_sse.o -felf64 -Xgnu -gdwarf -DLINUX -D__linux__ -Iinclude/ -I./ -Iavx/ -Iavx2/ -Iavx512/ -Isse/ sse/mb_mgr_hmac_sha_224_submit_sse.asm -- make[4]: *** [obj/mb_mgr_hmac_sha_224_submit_avx512.o] Error 1 make[4]: *** Waiting for unfinished jobs -- -- -- make[4]: Leaving directory `/home/vpp_communication/vpp/build-root/build-vpp-native/dpdk/intel-ipsec-mb-0.46' make[3]: *** [build-ipsec-mb] Error 2 make[3]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[2]: *** [ebuild-install] Error 2 make[2]: Leaving directory `/home/vpp_communication/vpp/dpdk' make[1]: *** [dpdk-install] Error 2 make[1]: Leaving directory `/home/vpp_communication/vpp/build-root' make: *** [build-release] Error 2 root@ubuntu:/home/vpp_communication/vpp# Is this a problem ? How can I solve it? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Failed to use vcl_test_client
Hi, When I test vcl ,there is some error : root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# ./vcl_test_client -U 1.1.1.2 22000 CLIENT: Connecting to server... msg_handler_internal:429: no handler for msg id 424 .. ... ... ERROR in main(): Bad file descriptor ERROR: connect failed (errno = 9)! Segmentation fault The msg id 424 is VL_API_CONNECT_URI_REPLY .The VL_API_CONNECT_URI_REPLY is registed in vat. Is there anything wrong in my test? The gdb information is shown below: (gdb) bt #0 vl_msg_api_send_shmem (q=q@entry=0x302891c0, elem=elem@entry=0x7faafab32cc8 "\344o\006\060") at /home/vpp_communication/vpp/build-data/../src/vlibmemory/memory_shared.c:584 #1 0x7fab3c053b55 in send_session_connected_callback (app_index=, api_context=3472551422, s=0x0, is_fail=) at /home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:186 #2 0x7fab3c03cc44 in stream_session_connect_notify (tc=0x7faafa776bd8, is_fail=, is_fail@entry=1 '\001') at /home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489 #3 0x7fab3bf0f642 in tcp_connection_reset (tc=tc@entry=0x7faafa776bd8) at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:257 #4 0x7fab3bee4077 in tcp46_syn_sent_inline (is_ip4=1, from_frame=, node=, vm=) at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:1938 #5 tcp4_syn_sent (vm=, node=, from_frame=) at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2091 #6 0x7fab3c4159e4 in dispatch_node (last_time_stamp=1926897640132334, frame=0x7faafb34a000, dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, node=0x7faafa86a600, vm=0x7fab3c668320 ) at /home/vpp_communication/vpp/build-data/../src/vlib/main.c:1011 #7 dispatch_pending_node (vm=vm@entry=0x7fab3c668320 , pending_frame_index=pending_frame_index@entry=5, last_time_stamp=last_time_stamp@entry=1926897640132334) at /home/vpp_communication/vpp/build-data/../src/vlib/main.c:1161 #8 0x7fab3c4177a5 in vlib_main_or_worker_loop (is_main=1, vm=0x7fab3c668320 ) at /home/vpp_communication/vpp/build-data/../src/vlib/main.c:1622 #9 vlib_main_loop (vm=0x7fab3c668320 ) at /home/vpp_communication/vpp/build-data/../src/vlib/main.c:1641 #10 vlib_main (vm=vm@entry=0x7fab3c668320 , input=input@entry=0x7faafab32fa0) at /home/vpp_communication/vpp/build-data/../src/vlib/main.c:1799 #11 0x7fab3c44f433 in thread0 (arg=140373429486368) at /home/vpp_communication/vpp/build-data/../src/vlib/unix/main.c:534 #12 0x7fab3ba4dbf8 in clib_calljmp () at /home/vpp_communication/vpp/build-data/../src/vppinfra/longjmp.S:110 #13 0x7ffe9df58600 in ?? () #14 0x7fab3c44ffb5 in vlib_unix_main (argc=, argv=) at /home/vpp_communication/vpp/build-data/../src/vlib/unix/main.c:597 #15 0x in ?? () Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Failed to use vcl_test_client
Hi ,
There are still problems:
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
./vcl_test_client -U 1.1.1.2 22000
CLIENT: Connecting to server...
vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session
failed to connect (-115)
Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0,
s=0x0, is_fail=1 '\001')
at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
157 {
(gdb) bt
#0 send_session_connected_callback (app_index=1, api_context=0, s=0x0,
is_fail=1 '\001')
at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
#1 0x7f35c658459c in stream_session_connect_notify (tc=0x7f358585e3f8,
is_fail=,
is_fail@entry=1 '\001') at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
#2 0x7f35c6456972 in tcp_connection_reset (tc=tc@entry=0x7f358585e3f8)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:258
#3 0x7f35c6429977 in tcp46_syn_sent_inline (is_ip4=1,
from_frame=, node=,
vm=) at
/home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2023
#4 tcp4_syn_sent (vm=, node=,
from_frame=)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2184
#5 0x7f35c6962d14 in dispatch_node (last_time_stamp=204974335045786,
frame=0x7f35858596c0,
dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL,
node=0x7f3584da06c0,
code segment：
int
send_session_connected_callback (u32 app_index, u32 api_context,
stream_session_t * s, u8 is_fail)
{
vl_api_connect_session_reply_t *mp;
unix_shared_memory_queue_t *q;
application_t *app;
unix_shared_memory_queue_t *vpp_queue;
app = application_get (app_index);
q = vl_api_client_index_to_input_queue (app->api_client_index);
if (!q)
return -1;
mp = vl_msg_api_alloc (sizeof (*mp));
mp->_vl_msg_id = clib_host_to_net_u16 (VL_API_CONNECT_SESSION_REPLY);
mp->context = api_context;
if (!is_fail)
{
vpp_queue = session_manager_get_vpp_event_queue (s->thread_index);
mp->server_rx_fifo = pointer_to_uword (s->server_rx_fifo);
mp->server_tx_fifo = pointer_to_uword (s->server_tx_fifo);
mp->handle = stream_session_handle (s);
mp->vpp_event_queue_address = pointer_to_uword (vpp_queue);
mp->retval = 0;
}
else
{
mp->retval = clib_host_to_net_u32 (VNET_API_ERROR_SESSION_CONNECT_FAIL);
}
vl_msg_api_send_shmem (q, (u8 *) & mp);
return 0;
}
ruturn message to VCL， connect failed: Session failed to connect
I have two question :
1. there are two function "vl_api_connect_sock_t_handler", one in
session_api.c, another in vppcom.c,
How to work ?
2. How to VCL and VPP communication ?
3. Why the message of VPP to VCL is "send_session_connected_callback" function
send ?
thanks,
xyxue
From: Dave Wallace
Date: 2017-09-19 01:29
To: 薛欣颖; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi Xyeue,
I believe this patch fixes this issue: https://gerrit.fd.io/r/#/c/8315/
Can you please pull the latest source code and try again?
Thanks,
-daw-
On 9/18/2017 2:43 AM, 薛欣颖 wrote:
Hi,
When I test vcl ,there is some error :
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
./vcl_test_client -U 1.1.1.2 22000
CLIENT: Connecting to server...
msg_handler_internal:429: no handler for msg id 424
..
...
...
ERROR in main(): Bad file descriptor
ERROR: connect failed (errno = 9)!
Segmentation fault
The msg id 424 is VL_API_CONNECT_URI_REPLY .The VL_API_CONNECT_URI_REPLY is
registed in vat.
Is there anything wrong in my test?
The gdb information is shown below:
(gdb) bt
#0 vl_msg_api_send_shmem (q=q@entry=0x302891c0, elem=elem@entry=0x7faafab32cc8
"\344o\006\060")
at
/home/vpp_communication/vpp/build-data/../src/vlibmemory/memory_shared.c:584
#1 0x7fab3c053b55 in send_session_connected_callback (app_index=, api_context=3472551422,
s=0x0, is_fail=) at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:186
#2 0x7fab3c03cc44 in stream_session_connect_notify (tc=0x7faafa776bd8,
is_fail=,
is_fail@entry=1 '\001') at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
#3 0x7fab3bf0f642 in tcp_connection_reset (tc=tc@entry=0x7faafa776bd8)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:257
#4 0x7fab3bee4077 in tcp46_syn_sent_inline (is_ip4=1,
from_frame=, node=,
vm=) at
/home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:1938
#5 tcp4_syn_sent (vm=, node=,
from_frame=)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2091
#6 0x7fab3c4159e4 in dispatch_node (last_time_stamp=1926897640132334,
frame=0x7faafb34
Re: [vpp-dev] Failed to use vcl_test_client
Hi Florin,
The server is started on the peer vpp . And through
'sock_test_client/sock_test_server' can be normal communication.
Thanks,
xyxue
From: Florin Coras
Date: 2017-09-20 10:52
To: 薛欣颖
CC: dwallacelf; vpp-dev
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi xyxue,
What you’re getting is a connect fail because, I assume from trace, the server
is not started on the peer vpp. Because the server is not started, i.e., bind
wasn’t called, when the peer vpp receives the syn it replies with a reset. That
reset finally results in a connect fail notify.
As for your other questions:
1. Obviously, the one in vpp is for handling connect requests from applications
while the one in vppcom is for cut-through session. That is, vpp acts as
introduction mechanism for the two apps which afterwards exchange data via
shared memory fifos.
2. For exchanging control messages, e.g., bind, connect, accept, they use the
binary api. For exchanging data, that is, moving data from vpp to vcl and
vice-versa, they use shared memory fifos.
3. That message is a notification from vpp to the application (vcl in this
case) regarding a previous connect attempt. As you’ve discovered, if is_fail=1,
the connect attempt failed.
Hope this helps,
Florin
On Sep 19, 2017, at 7:30 PM, 薛欣颖 wrote:
Hi ,
There are still problems:
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
./vcl_test_client -U 1.1.1.2 22000
CLIENT: Connecting to server...
vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session
failed to connect (-115)
Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0,
s=0x0, is_fail=1 '\001')
at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
157 {
(gdb) bt
#0 send_session_connected_callback (app_index=1, api_context=0, s=0x0,
is_fail=1 '\001')
at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
#1 0x7f35c658459c in stream_session_connect_notify (tc=0x7f358585e3f8,
is_fail=,
is_fail@entry=1 '\001') at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
#2 0x7f35c6456972 in tcp_connection_reset (tc=tc@entry=0x7f358585e3f8)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:258
#3 0x7f35c6429977 in tcp46_syn_sent_inline (is_ip4=1,
from_frame=, node=,
vm=) at
/home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2023
#4 tcp4_syn_sent (vm=, node=,
from_frame=)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2184
#5 0x7f35c6962d14 in dispatch_node (last_time_stamp=204974335045786,
frame=0x7f35858596c0,
dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL,
node=0x7f3584da06c0,
code segment：
int
send_session_connected_callback (u32 app_index, u32 api_context,
stream_session_t * s, u8 is_fail)
{
vl_api_connect_session_reply_t *mp;
unix_shared_memory_queue_t *q;
application_t *app;
unix_shared_memory_queue_t *vpp_queue;
app = application_get (app_index);
q = vl_api_client_index_to_input_queue (app->api_client_index);
if (!q)
return -1;
mp = vl_msg_api_alloc (sizeof (*mp));
mp->_vl_msg_id = clib_host_to_net_u16 (VL_API_CONNECT_SESSION_REPLY);
mp->context = api_context;
if (!is_fail)
{
vpp_queue = session_manager_get_vpp_event_queue (s->thread_index);
mp->server_rx_fifo = pointer_to_uword (s->server_rx_fifo);
mp->server_tx_fifo = pointer_to_uword (s->server_tx_fifo);
mp->handle = stream_session_handle (s);
mp->vpp_event_queue_address = pointer_to_uword (vpp_queue);
mp->retval = 0;
}
else
{
mp->retval = clib_host_to_net_u32 (VNET_API_ERROR_SESSION_CONNECT_FAIL);
}
vl_msg_api_send_shmem (q, (u8 *) & mp);
return 0;
}
ruturn message to VCL， connect failed: Session failed to connect
I have two question :
1. there are two function "vl_api_connect_sock_t_handler", one in
session_api.c, another in vppcom.c,
How to work ?
2. How to VCL and VPP communication ?
3. Why the message of VPP to VCL is "send_session_connected_callback" function
send ?
thanks,
xyxue
From: Dave Wallace
Date: 2017-09-19 01:29
To: 薛欣颖; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi Xyeue,
I believe this patch fixes this issue: https://gerrit.fd.io/r/#/c/8315/
Can you please pull the latest source code and try again?
Thanks,
-daw-
On 9/18/2017 2:43 AM, 薛欣颖 wrote:
Hi,
When I test vcl ,there is some error :
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
./vcl_test_client -U 1.1.1.2 22000
CLIENT: Connecting to server...
msg_handler_internal:429: no handler for msg id 424
..
...
...
ERROR in main(): Bad file descriptor
ERROR: connect failed (errno =
Re: [vpp-dev] memmove fault
Hi Chris, Until today, the problem only appeared again: Program received signal SIGSEGV, Segmentation fault. __memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1663 1663../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S: No such file or directory. (gdb) bt #0 __memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1663 #1 0x7796531f in unix_cli_line_process_one (cm=0x77ba6d80 , um=0x77ba77e0 , cf=0x7fffb5e5bf80, uf=0x7fffb5e5bf24, input=115 's', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2065 #2 0x77965911 in unix_cli_line_edit (cm=0x77ba6d80 , um=0x77ba77e0 , cf=0x7fffb5e5bf80) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2154 #3 0x77965c49 in unix_cli_process_input (cm=0x77ba6d80 , cli_file_index=0) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2194 #4 0x77966814 in unix_cli_process (vm=0x77ba7080 , rt=0x7fffb5e5c000, f=0x0) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2320 #5 0x77928699 in vlib_process_bootstrap (_a=140736239855696) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1275 #6 0x7695fddc in clib_calljmp () at /home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/longjmp.S:128 #7 0x7fffb5956820 in ?? () #8 0x779287ce in vlib_process_startup (vm=0x7795c5b2 , p=0x7fffb5956880, f=0x8496528d2a6d3500) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1300 Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) f 1 #1 0x7796531f in unix_cli_line_process_one (cm=0x77ba6d80 , um=0x77ba77e0 , cf=0x7fffb5e5bf80, uf=0x7fffb5e5bf24, input=115 's', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2065 2065 memmove (cf->current_command + cf->cursor + 1, (gdb) p cf->current_command $36 = (u8 *) 0x7fffb5e5b740 "Ahow interface ipsec-gre " (gdb) p cf->cursor $37 = 15 (gdb) p j $38 = -15 (gdb) Until now I have not figured out the rule that it appears. Thanks, xyxue From: Luke, Chris Date: 2017-08-17 04:54 To: 薛欣颖; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] memmove fault Can you be more specific about the steps that led up to this issue? I won’t be able to work on it until September (about to go on vacation) but I do want to try to capture the details so I can try to recreate it. Chris. From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of ??? Sent: Tuesday, August 15, 2017 5:14 To: vpp-dev@lists.fd.io Subject: [vpp-dev] memmove fault Hi, When I failed to configure a command, then click the up key , there is a Segmentation fault(not every time): Program received signal SIGSEGV, Segmentation fault. __memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664 1664../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S: No such file or directory. (gdb) bt #0 __memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664 #1 0x77966f56 in unix_cli_line_process_one (cm=0x77ba4960 , um=0x77ba7dc0 , cf=0x7fffb5de5b3c, uf=0x7fffb5de5ae0, input=102 'f', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2063 #2 0x77967548 in unix_cli_line_edit (cm=0x77ba4960 , um=0x77ba7dc0 , cf=0x7fffb5de5b3c) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2152 #3 0x77967880 in unix_cli_process_input (cm=0x77ba4960 , cli_file_index=0) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2192 #4 0x7796844b in unix_cli_process (vm=0x77ba7560 , rt=0x7fffb5e7, f=0x0) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2318 #5 0x7792a320 in vlib_process_bootstrap (_a=140736239921232) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1274 #6 0x7696fd4c in clib_calljmp () at /home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/longjmp.S:128 #7 0x7fffb5966820 in ?? () #8 0x7792a455 in vlib_process_startup (vm=0x7795e1e9 , p=0x7fffb5966880, f=0xedcb4a35d968b00) at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1299 Backtrace stopped: previous frame inner to this frame (corrupt stack?) How should we solve this problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Failed to use vcl_test_client
Hi Florin,
There is a compile error:not support ‘__NR_memfd_create’
/home/vpp_communication/vpp/build-root/../src/vppinfra/linux/syscall.h:45:19:
error: '__NR_memfd_create' undeclared (first use in this function)
return syscall (__NR_memfd_create, name, flags);
Is the kernel version of the problem ? What is your kernel version?
The Kernel version of mine：
root@ubuntu:/home/vpp_communication/vppsb/vcl-ldpreload/src# uname -a
Linux ubuntu 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
If I change ‘return syscall (__NR_memfd_create, name, flags);’ to ‘return 0’.
Will the vcl function be affected?
Thanks,
xyxue
From: Florin Coras
Date: 2017-09-20 13:05
To: 薛欣颖
CC: dwallacelf; vpp-dev
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi xyxue,
I just tested the stack with linux and everything seems to be working fine. I
tested the stack with linux using uri_tcp_test and nc and the cut-through path
with the vcl test tools. How are you running the server?
Florin
On Sep 19, 2017, at 8:29 PM, 薛欣颖 wrote:
Hi Florin,
The server is started on the peer vpp . And through
'sock_test_client/sock_test_server' can be normal communication.
Thanks,
xyxue
From: Florin Coras
Date: 2017-09-20 10:52
To: 薛欣颖
CC: dwallacelf; vpp-dev
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi xyxue,
What you’re getting is a connect fail because, I assume from trace, the server
is not started on the peer vpp. Because the server is not started, i.e., bind
wasn’t called, when the peer vpp receives the syn it replies with a reset. That
reset finally results in a connect fail notify.
As for your other questions:
1. Obviously, the one in vpp is for handling connect requests from applications
while the one in vppcom is for cut-through session. That is, vpp acts as
introduction mechanism for the two apps which afterwards exchange data via
shared memory fifos.
2. For exchanging control messages, e.g., bind, connect, accept, they use the
binary api. For exchanging data, that is, moving data from vpp to vcl and
vice-versa, they use shared memory fifos.
3. That message is a notification from vpp to the application (vcl in this
case) regarding a previous connect attempt. As you’ve discovered, if is_fail=1,
the connect attempt failed.
Hope this helps,
Florin
On Sep 19, 2017, at 7:30 PM, 薛欣颖 wrote:
Hi ,
There are still problems:
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
./vcl_test_client -U 1.1.1.2 22000
CLIENT: Connecting to server...
vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session
failed to connect (-115)
Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0,
s=0x0, is_fail=1 '\001')
at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
157 {
(gdb) bt
#0 send_session_connected_callback (app_index=1, api_context=0, s=0x0,
is_fail=1 '\001')
at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
#1 0x7f35c658459c in stream_session_connect_notify (tc=0x7f358585e3f8,
is_fail=,
is_fail@entry=1 '\001') at
/home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
#2 0x7f35c6456972 in tcp_connection_reset (tc=tc@entry=0x7f358585e3f8)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:258
#3 0x7f35c6429977 in tcp46_syn_sent_inline (is_ip4=1,
from_frame=, node=,
vm=) at
/home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2023
#4 tcp4_syn_sent (vm=, node=,
from_frame=)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2184
#5 0x7f35c6962d14 in dispatch_node (last_time_stamp=204974335045786,
frame=0x7f35858596c0,
dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL,
node=0x7f3584da06c0,
code segment：
int
send_session_connected_callback (u32 app_index, u32 api_context,
stream_session_t * s, u8 is_fail)
{
vl_api_connect_session_reply_t *mp;
unix_shared_memory_queue_t *q;
application_t *app;
unix_shared_memory_queue_t *vpp_queue;
app = application_get (app_index);
q = vl_api_client_index_to_input_queue (app->api_client_index);
if (!q)
return -1;
mp = vl_msg_api_alloc (sizeof (*mp));
mp->_vl_msg_id = clib_host_to_net_u16 (VL_API_CONNECT_SESSION_REPLY);
mp->context = api_context;
if (!is_fail)
{
vpp_queue = session_manager_get_vpp_event_queue (s->thread_index);
mp->server_rx_fifo = pointer_to_uword (s->server_rx_fifo);
mp->server_tx_fifo = pointer_to_uword (s->server_tx_fifo);
mp->handle = stream_session_handle (s);
mp->vpp_event_queue_address = pointer_to_uword (vpp_queue);
mp->retval = 0;
}
else
{
mp->retval = clib_host_to_net_u32 (VNET_API_ERROR_SESSION_CONNECT_FAIL);
}
vl_msg_api_send
Re: [vpp-dev] Failed to use vcl_test_client
Hi, I have added '#define __NR_memfd_create 319' to /usr/include/x86_64-linux-gnu/asm/unistd_64.h. The following error still occurred during the test: root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# ./vcl_test_client -U 1.1.1.2 22000 CLIENT: Connecting to server... vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session failed to connect (-115) Are we missing the configuration? Or are there any problems with our testing methods? The kernel version： root@ubuntu:/home/vpp_communication/vppsb/vcl-ldpreload/src# uname -a Linux ubuntu 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Test topology: Server vpp configure： create host-interface name eth1 set interface mac address host-eth1 00:0c:29:4c:35:65 set interface state host-eth1 up set interface ip address host-eth1 1.1.1.2/24 start VCL server ： root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# ./vcl_test_server SERVER: Waiting for a client to connect on port 22000... vcl Client: create host-interface name eth1 set interface mac address host-eth1 00:0c:29:db:3c:8f set interface state host-eth1 up set interface ip address host-eth1 1.1.1.1/24 start VCL client： root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# ./vcl_test_client -U 1.1.1.2 22000 CLIENT: Connecting to server... vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session failed to connect (-115) Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0, s=0x0, is_fail=1 '\001') at /home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157 2. Run the test script 'socket_test.sh' directly.The error is shown below： -(missing a software?) root@ubuntu:/home/vpp_communication/vpp/test/scripts# ./socket_test.sh -U nv Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm: xterm: Xt error: Can't open display: %s Xt error: Can't open display: %s xterm: xterm: DISPLAY is not set Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm: Xt error: Can't open display: %s xterm: DISPLAY is not set DISPLAY is not set Thanks, Xyxue From: Florin Coras Date: 2017-09-28 02:31 To: John Lo (loj) CC: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] Failed to use vcl_test_client Cool! Thanks for the info, John! Xyxue, could you try it out and see if it works? Florin On Sep 27, 2017, at 11:25 AM, John Lo (loj) wrote: I am able to use memfd with 14.04 by updating its kernel to 3.19 (my 14.04 kernel was 3.13 before the update). I also had to add the following to /usr/include/x86_64-linux-gnu/asm/unistd_64.h #define __NR_memfd_create 319 Hope this works for you, John From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Florin Coras Sent: Wednesday, September 27, 2017 10:46 AM To: 薛欣颖 Cc: vpp-dev Subject: Re: [vpp-dev] Failed to use vcl_test_client Hi xyxue, VPP now has a dependency on memfd which is not available in 14.04. Unfortunately, that means you’ll have to switch to ubuntu 16.04. Florin On Sep 27, 2017, at 1:34 AM, 薛欣颖 wrote: Hi Florin, There is a compile error:not support ‘__NR_memfd_create’ /home/vpp_communication/vpp/build-root/../src/vppinfra/linux/syscall.h:45:19: error: '__NR_memfd_create' undeclared (first use in this function) return syscall (__NR_memfd_create, name, flags); Is the kernel version of the problem ? What is your kernel version? The Kernel version of mine： root@ubuntu:/home/vpp_communication/vppsb/vcl-ldpreload/src# uname -a Linux ubuntu 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux If I change ‘return syscall (__NR_memfd_create, name, flags);’ to ‘return 0’. Will the vcl function be affected? Thanks, xyxue From: Florin Coras Date: 2017-09-20 13:05 To: 薛欣颖 CC: dwallacelf; vpp-dev Subject: Re: [vpp-dev] Failed to use vcl_test_client Hi xyxue, I just tested the stack with linux and everything seems to be working fine. I tested the stack with linux using uri_tcp_test and nc and
Re: [vpp-dev] Failed to use vcl_test_client
Hi， topology： VPP1 and VPP2 on two virtual machines, Have you verified the VPP1 and VPP2 are connected (i.e. ping 1.1.1.2 from vpp1) ? ---ping 1.1.1.2 from vpp1 is ok The following configuration for cyberspace is on the same virtual machine: Linux: ip netns add vppns ip link add veth_vpp1 type veth peer name vpp1 ip link set dev vpp1 up ip link set dev veth_vpp1 up netns vppns ip link add veth_vpp2 type veth peer name vpp2 ip link set dev vpp2 up ip link set dev veth_vpp2 up netns vppns By the way, is it ok to start two vpp in the same virtual machine? Thanks， xyxue From: Dave Wallace Date: 2017-09-29 00:03 To: 薛欣颖; Florin Coras; John Lo (loj) CC: vpp-dev Subject: Re: [vpp-dev] Failed to use vcl_test_client Xyxue, Have you verified the VPP1 and VPP2 are connected (i.e. ping 1.1.1.2 from vpp1) ? The multi-host configuration has been tested using vagrant/virtualbox using .../vpp/extras/vagrant/Vagrantfile.vcl_test. I will add a recipe to the wiki in the next day or so. The socket_test.sh script is designed to auto-configure different test configurations in an X-Window environment. It runs the client / server configuration in xterm (or xfce4_terminal) and can optionally run gdb in the xterm or in emacs. Thanks, -daw- On 09/28/2017 08:11 AM, 薛欣颖 wrote: Hi, I have added '#define __NR_memfd_create 319' to /usr/include/x86_64-linux-gnu/asm/unistd_64.h. The following error still occurred during the test: root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# ./vcl_test_client -U 1.1.1.2 22000 CLIENT: Connecting to server... vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session failed to connect (-115) Are we missing the configuration? Or are there any problems with our testing methods? The kernel version： root@ubuntu:/home/vpp_communication/vppsb/vcl-ldpreload/src# uname -a Linux ubuntu 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Test topology: Server vpp configure： create host-interface name eth1 set interface mac address host-eth1 00:0c:29:4c:35:65 set interface state host-eth1 up set interface ip address host-eth1 1.1.1.2/24 start VCL server ： root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# ./vcl_test_server SERVER: Waiting for a client to connect on port 22000... vcl Client: create host-interface name eth1 set interface mac address host-eth1 00:0c:29:db:3c:8f set interface state host-eth1 up set interface ip address host-eth1 1.1.1.1/24 start VCL client： root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# ./vcl_test_client -U 1.1.1.2 22000 CLIENT: Connecting to server... vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session failed to connect (-115) Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0, s=0x0, is_fail=1 '\001') at /home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157 2. Run the test script 'socket_test.sh' directly.The error is shown below： -(missing a software?) root@ubuntu:/home/vpp_communication/vpp/test/scripts# ./socket_test.sh -U nv Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm: xterm: Xt error: Can't open display: %s Xt error: Can't open display: %s xterm: xterm: DISPLAY is not set Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm: Xt error: Can't open display: %s xterm: DISPLAY is not set DISPLAY is not set Thanks, Xyxue From: Florin Coras Date: 2017-09-28 02:31 To: John Lo (loj) CC: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] Failed to use vcl_test_client Cool! Thanks for the info, John! Xyxue, could you try it out and see if it works? Florin On Sep 27, 2017, at 11:25 AM, John Lo (loj) wrote: I am able to use memfd with 14.04 by updating its kernel to 3.19 (my 14.04 kernel was 3.13 before the update). I also had to add the following to /usr/include/x86_64-linux-gnu/asm/unistd_64.h #define __NR_memfd_create 319 Hope this works for you, John ___ vpp-dev mailing list vpp-dev@lists.fd.io
Re: [vpp-dev] Failed to use vcl_test_client
Hi，
We use the TCP protocol to test VCL, the function is OK. If I modify the UDP
protocol, the function is abnormal.
The error message is:
DBGvpp# 0: udp_open_connection:254: Not implemented
The code is implemented as follows:
int
udp_open_connection (transport_endpoint_t * tep)
{
clib_warning ("Not implemented");
return 0;
}
Does the current VCL support the UDP protocol?
Thanks,
xyxue
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Segmentation fault in ikev2 test
Hi, I'm testing ikev2 and there is something error in my test: VPP# ikev2 initiate del-sa ee25d9aa4e7a0f1a 0: ikev2_generate_message:1774: sa state changed to IKEV2_STATE_NOTIFY_AND_DELETE Program received signal SIGSEGV, Segmentation fault. 0x2b293d767f4b in ip4_fib_mtrie_lookup_step_one (m=0x0, dst_address=0x2b2991d243f4) at /root/tmp64/build-data/../src/vnet/ip/ip4_mtrie.h:225 225 next_leaf = m->root_ply.leaves[dst_address->as_u16[0]]; (gdb) bt #0 0x2b293d767f4b in ip4_fib_mtrie_lookup_step_one (m=0x0, dst_address=0x2b2991d243f4) at /root/tmp64/build-data/../src/vnet/ip/ip4_mtrie.h:225 #1 0x2b293d769bb3 in ip4_lookup_inline (vm=0x2b293d59c120 , node=0x2b293f843080, frame=0x2b293fbfe800, lookup_for_responses_to_locally_received_packets=0) at /root/tmp64/build-data/../src/vnet/ip/ip4_forward.c:362 #2 0x2b293d76a02f in ip4_lookup (vm=0x2b293d59c120 , node=0x2b293f843080, frame=0x2b293fbfe800) at /root/tmp64/build-data/../src/vnet/ip/ip4_forward.c:472 #3 0x2b293d31b910 in dispatch_node (vm=0x2b293d59c120 , node=0x2b293f843080, type=VLIB_NODE_TYPE_INTERNAL, dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x2b293fbfe800, last_time_stamp=375367370313442) at /root/tmp64/build-data/../src/vlib/main.c:1032 #4 0x2b293d31bef3 in dispatch_pending_node (vm=0x2b293d59c120 , pending_frame_index=0, last_time_stamp=375367370313442) at /root/tmp64/build-data/../src/vlib/main.c:1182 #5 0x2b293d31e009 in vlib_main_or_worker_loop (vm=0x2b293d59c120 , is_main=1) at /root/tmp64/build-data/../src/vlib/main.c:1649 #6 0x2b293d31e0bb in vlib_main_loop (vm=0x2b293d59c120 ) at /root/tmp64/build-data/../src/vlib/main.c:1668 #7 0x2b293d31e76f in vlib_main (vm=0x2b293d59c120 , input=0x2b293f728fb0) at /root/tmp64/build-data/../src/vlib/main.c:1804 #8 0x2b293d361d48 in thread0 (arg=47456122945824) at /root/tmp64/build-data/../src/vlib/unix/main.c:515 #9 0x2b293e2e8dcc in clib_calljmp () at /root/tmp64/build-data/../src/vppinfra/longjmp.S:128 #10 0x7ffcf2dbf510 in ?? () #11 0x2b293d3621e1 in vlib_unix_main (argc=4, argv=0x7ffcf2dc0798) at /root/tmp64/build-data/../src/vlib/unix/main.c:578 #12 0x00407ff1 in main (argc=4, argv=0x7ffcf2dc0798) at /root/tmp64/build-data/../src/vpp/vnet/main.c:206 (gdb) in ip4_lookup_inline ' fib_index0 = vec_elt (im->fib_index_by_sw_if_index, vnet_buffer (p0)->sw_if_index[VLIB_RX]); fib_index0 = (vnet_buffer (p0)->sw_if_index[VLIB_TX] == (u32) ~ 0) ? fib_index0 : vnet_buffer (p0)->sw_if_index[VLIB_TX]; ' The '(vnet_buffer (p0)->sw_if_index[VLIB_TX] ' is (u32) ~ 0 when 'del-sa' execute success. The '(vnet_buffer (p0)->sw_if_index[VLIB_TX] ' is 2 when 'del-sa' execute fail. By the way, the fault doesn't happen every time. What should I do to solve the problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] MPLS LABEL problem
Hi guys, My vpp version :18.01. vpp1-vpp2 When the flows out of vpp1, it has two layers of tags. The flow was dropped in vpp2. And the error information:MPLS not enabled. Is there anything wrong in my configuration on vpp2? Has the configuration in 18.01 changed? vpp1 create host-interface name eth2 mac 00:0c:29:6d:b0:82 create host-interface name eth1 mac 00:0c:29:6d:b0:78 set interface ip table host-eth2 1 set interface ip address host-eth2 1.1.1.1/24 set interface ip address host-eth1 2.1.1.1/24 set interface state host-eth2 up set interface state host-eth1 up set interface mpls host-eth1 enable create mpls tunnel out-label 33 out-label 34 via 2.1.1.2 host-eth1 set interface state mpls-tunnel0 up mpls table add 1 ip route add 3.1.1.0/24 via ip4-address 2.1.1.2 interface mpls-tunnel0 table 1 mpls local-label add eos 1023 table 1 ip4-lookup-in-table 1 mpls local-label add non-eos 1023 table 1 mpls-lookup-in-table 1 vpp2 create host-interface name eth2 mac 2c:53:4a:03:93:31 create host-interface name eth1 mac 2c:53:4a:03:94:59 set interface ip table host-eth2 1 set interface ip address host-eth1 2.1.1.2/24 set interface ip address host-eth2 3.1.1.1/24 set interface state host-eth2 up set interface state host-eth1 up set interface mpls host-eth1 enable create mpls tunnel out-label 1023 out-label 1024 via 2.1.1.1 host-eth1 set interface state mpls-tunnel0 up mpls table add 1 ip route add 1.1.1.0/24 via ip4-address 2.1.1.1 interface mpls-tunnel0 table 1 mpls local-label add eos 34 table 1 ip4-lookup-in-table 1 mpls local-label add non-eos 33 table 1 mpls-lookup-in-table 1 the vpp2 error information is shown below: VPP# show errors CountNode Reason 4889 mpls-input MPLS input packets decapsulated 4889 mpls-input MPLS not enabled 31ip4-input valid ip4 packets 103 ethernet-input no error 2arp-input ARP replies sent 1arp-input ARP request IP4 source address learned VPP# show trace --- Start of thread 0 vpp_main --- Packet 1 00:11:22:232258: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 132 snaplen 132 mac 66 net 80 sec 0x5a141690 nsec 0x3162f619 vlan 0 00:11:22:232280: ethernet-input MPLS: 00:0c:29:6d:b0:78 -> 2c:53:4a:03:94:59 00:11:22:232332: mpls-input MPLS: next BUG![2] label 33 ttl 255 00:11:22:232342: error-drop mpls-input: MPLS not enabled Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] SR MPLS not effective
Hi Pablo, After hearing your advice, I modified my configuration on P: create host-interface name eth2 mac 00:0c:29:0f:e2:a8 create host-interface name eth3 mac 00:0c:29:0f:e2:b2 set interface state host-eth2 up set interface state host-eth3 up set interface ip address host-eth3 12.1.1.1/24 mpls table add 0 set interface mpls host-eth2 enable set interface mpls host-eth3 enable set interface ip address host-eth2 14.1.1.2/24 create mpls tunnel out-label 60 via 12.1.1.2 host-eth3 set interface state mpls-tunnel0 up sr mpls policy add bsid 33 next 60 //exchange the out-label to 60 sr mpls steer l3 23.1.1.0/24 via sr policy bsid 33 set interface mpls mpls-tunnel0 enable the trace info on P: 00:01:54:346199: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 86 snaplen 86 mac 66 net 80 sec 0x5a1d417b nsec 0xdffd3a9 vlan 0 00:01:54:346226: ethernet-input MPLS: 00:0c:29:4d:af:a1 -> 00:0c:29:0f:e2:a8 00:01:54:346243: mpls-input MPLS: next mpls-lookup[1] label 33 ttl 255 00:01:54:346249: mpls-lookup MPLS: next [0], lookup fib index 0, LB index 26 hash 0 label 33 eos 0 00:01:54:346259: error-drop mpls-input: MPLS DROP DPO The SR MPLS still not effctive. Is there any example on SR MPLS configuration? Thanks, Xyxue From: Pablo Camarillo (pcamaril) Date: 2017-11-28 18:16 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] SR MPLS not effective Hi Xyxue, Could you please explain what you want to achieve with this config? Where do you want to start your SR policy? None of the configs that you described below for P will work. In the case #1 you are creating a SR policy with BSID 33. Then for any packet with incoming label 33 you will push the SID list of the SR policy. However, you are also creating an mpls local-label for 33 as well which you do not need. On top of that, you are configuring the SR policy with SID list < 60 >, but you have not set a local-label/route for 60. Hence packet will be dropped. Thanks. Cheers, Pablo. From: on behalf of 薛欣颖 Date: Tuesday, 28 November 2017 at 08:08 To: vpp-dev Subject: [vpp-dev] SR MPLS not effective Hi guys， I have tried every configuration I can guess. The sr mpls still not effective on my vpp. Can you give me an effective configuration, or can you help figure out the error in my configuration? PE1 - P - PE2 PE1 configuration: create host-interface name eth4 mac 00:0c:29:4d:af:b5 create host-interface name eth2 mac 00:0c:29:4d:af:a1 set interface state host-eth2 up set interface state host-eth4 up set interface ip table host-eth4 1 set interface ip address host-eth2 14.1.1.1/24 set interface ip address host-eth4 21.1.1.1/24 create mpls tunnel out-label 33 out-label 53 via 14.1.1.2 host-eth2 set interface state mpls-tunnel0 up mpls table add 0 set interface mpls host-eth2 enable ip route add 23.1.1.1/24 via interface mpls-tunnel0 table 1 mpls local-label add eos 1053 ip4-lookup-in-table 1 mpls local-label add non-eos 1060 mpls-lookup-in-table 0 PE2 configuration: create host-interface name eth3 mac 00:0c:29:19:8e:76 create host-interface name eth5 mac 00:0c:29:19:8e:8a set interface state host-eth3 up set interface state host-eth5 up set interface ip address host-eth3 12.1.1.2/24 set interface ip table host-eth5 1 set interface ip address host-eth5 23.1.1.1/24 mpls table add 0 mpls table add 1 mpls local-label add non-eos 60 mpls-lookup-in-table 0 mpls local-label add eos 53 ip4-lookup-in-table 1 set interface mpls host-eth5 enable set interface mpls host-eth3 enable create mpls tunnel out-label 1023 out-label 1053 via 12.1.1.1 host-eth3 set interface state mpls-tunnel0 up ip route add 21.1.1.0/24 via interface mpls-tunnel0 table 1 P configuration: (only modify the configuration on P) 1. drop packet.(when decap outer label,can't encap outer label) the configuration and trace is following: create host-interface name eth2 mac 00:0c:29:0f:e2:a8 create host-interface name eth3 mac 00:0c:29:0f:e2:b2 set interface state host-eth2 up set interface state host-eth3 up set interface ip address host-eth3 12.1.1.1/24 mpls table add 0 mpls table add 1 set interface mpls host-eth2 enable set interface mpls host-eth3 enable mpls local-label add non-eos 33 mpls-lookup-in-table 0 set interface ip address host-eth2 14.1.1.2/24 mpls local-label add eos 53 ip4-lookup-in-table 0 mpls local-label add eos 1053 ip4-lookup-in-table 0 mpls local-label add non-eos 1023 mpls-lookup-in-table 0 sr mpls policy add bsid 33 next 60 00:08:35:510564: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 86 snaplen 86 mac 66 net 80 sec 0x5a1cbe94 nsec 0x1ea50e69 vlan 0 00:08:35:510591: ethernet-input MPLS: 00:0c:29:4d:af:a1 -> 00:0c:29:0f:e2:a8 00:08:35:510650: mpls-input MPLS: next mpls-lookup[1] label 33 ttl 255 00:0
Re: [vpp-dev] SR MPLS not effective
Hi Neale, After add the 'mpls local-label add non-eos 33 mpls-lookup-in-table 0 ' on P, the mistake still exist. create host-interface name eth2 mac 00:0c:29:0f:e2:a8 create host-interface name eth3 mac 00:0c:29:0f:e2:b2 set interface state host-eth2 up set interface state host-eth3 up set interface ip address host-eth3 12.1.1.1/24 mpls table add 0 set interface mpls host-eth2 enable set interface mpls host-eth3 enable set interface ip address host-eth2 14.1.1.2/24 create mpls tunnel out-label 60 via 12.1.1.2 host-eth3 set interface state mpls-tunnel0 up sr mpls policy add bsid 33 next 60 sr mpls steer l3 23.1.1.0/24 via sr policy bsid 33 set interface mpls mpls-tunnel0 enable mpls local-label add non-eos 33 mpls-lookup-in-table 0 // local-label 33/non-eos configured the mistake is the same as before: 00:06:02:539782: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 86 snaplen 86 mac 66 net 80 sec 0x5a1e5992 nsec 0x193b68e0 vlan 0 00:06:02:539813: ethernet-input MPLS: 00:0c:29:4d:af:a1 -> 00:0c:29:0f:e2:a8 00:06:02:539869: mpls-input MPLS: next mpls-lookup[1] label 33 ttl 255 00:06:02:539878: mpls-lookup MPLS: next [0], lookup fib index 0, LB index 25 hash 0 label 33 eos 0 00:06:02:539889: error-drop mpls-input: MPLS DROP DPO Is there any example on SR MPLS configuration I can get? Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-11-28 20:29 To: 薛欣颖; Pablo Camarillo (pcamaril); vpp-dev Subject: Re: [vpp-dev] SR MPLS not effective Hi Xyxue, Your trace says: 00:01:54:346249: mpls-lookup MPLS: next [0], lookup fib index 0, LB index 26 hash 0 label 33 eos 0 so the packet required an MPLS lookup on label 33 non-eos. Your config has no local-label 33/non-eos configured, so the packet is dropped. /neale From: on behalf of 薛欣颖 Date: Tuesday, 28 November 2017 at 12:20 To: "Pablo Camarillo (pcamaril)" , vpp-dev Subject: Re: [vpp-dev] SR MPLS not effective Hi Pablo, After hearing your advice, I modified my configuration on P: create host-interface name eth2 mac 00:0c:29:0f:e2:a8 create host-interface name eth3 mac 00:0c:29:0f:e2:b2 set interface state host-eth2 up set interface state host-eth3 up set interface ip address host-eth3 12.1.1.1/24 mpls table add 0 set interface mpls host-eth2 enable set interface mpls host-eth3 enable set interface ip address host-eth2 14.1.1.2/24 create mpls tunnel out-label 60 via 12.1.1.2 host-eth3 set interface state mpls-tunnel0 up sr mpls policy add bsid 33 next 60 //exchange the out-label to 60 sr mpls steer l3 23.1.1.0/24 via sr policy bsid 33 set interface mpls mpls-tunnel0 enable the trace info on P: 00:01:54:346199: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 86 snaplen 86 mac 66 net 80 sec 0x5a1d417b nsec 0xdffd3a9 vlan 0 00:01:54:346226: ethernet-input MPLS: 00:0c:29:4d:af:a1 -> 00:0c:29:0f:e2:a8 00:01:54:346243: mpls-input MPLS: next mpls-lookup[1] label 33 ttl 255 00:01:54:346249: mpls-lookup MPLS: next [0], lookup fib index 0, LB index 26 hash 0 label 33 eos 0 00:01:54:346259: error-drop mpls-input: MPLS DROP DPO The SR MPLS still not effctive. Is there any example on SR MPLS configuration? Thanks, Xyxue From: Pablo Camarillo (pcamaril) Date: 2017-11-28 18:16 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] SR MPLS not effective Hi Xyxue, Could you please explain what you want to achieve with this config? Where do you want to start your SR policy? None of the configs that you described below for P will work. In the case #1 you are creating a SR policy with BSID 33. Then for any packet with incoming label 33 you will push the SID list of the SR policy. However, you are also creating an mpls local-label for 33 as well which you do not need. On top of that, you are configuring the SR policy with SID list < 60 >, but you have not set a local-label/route for 60. Hence packet will be dropped. Thanks. Cheers, Pablo. From: on behalf of 薛欣颖 Date: Tuesday, 28 November 2017 at 08:08 To: vpp-dev Subject: [vpp-dev] SR MPLS not effective Hi guys， I have tried every configuration I can guess. The sr mpls still not effective on my vpp. Can you give me an effective configuration, or can you help figure out the error in my configuration? PE1 - P - PE2 PE1 configuration: create host-interface name eth4 mac 00:0c:29:4d:af:b5 create host-interface name eth2 mac 00:0c:29:4d:af:a1 set interface state host-eth2 up set interface state host-eth4 up set interface ip table host-eth4 1 set interface ip address host-eth2 14.1.1.1/24 set interface ip address host-eth4 21.1.1.1/24 create mpls tunnel out-label 33 out-label 53 via 14.1.1.2 host-eth2 set interface state mpls-tunnel0 up mpls table add 0 set interface mpls host-eth2 enable ip route add 23.1.1.1/24 via interface mpls-tunnel0 table 1 m
Re: [vpp-dev] SR MPLS not effective
Hi Neale， After referring to your example, I modified my configuration. And the two layer label SR MPLS works well. But when configure ten layer label, the bottom label is different from the configuration. vpp1 configuration: create host-interface name eth4 mac 00:0c:29:4d:af:b5 create host-interface name eth2 mac 00:0c:29:4d:af:a1 set interface state host-eth2 up set interface state host-eth4 up set interface ip address host-eth2 14.1.1.1/24 set interface ip address host-eth4 21.1.1.1/24 mpls table add 0 set interface mpls host-eth2 enable sr mpls policy add bsid 999 next 210 next 209 next 208 next 207 next 206 next 205 next 204 next 203 next 202 next 201 // encap 10 layer label sr mpls steer l3 23.1.1.0/24 via sr policy bsid 999 mpls local-label add non-eos 210 via 14.1.1.2 host-eth2 out-label 211 Actually, the bottom is 16416 (the value configured is 201). The ttl is 63 and others is 255. The trace info and message info is shown below: 00:31:47:618725: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 78 snaplen 78 mac 66 net 80 sec 0x5a1fb1aa nsec 0x22ae91a9 vlan 0 00:31:47:618752: ethernet-input IP4: 00:00:00:66:00:55 -> 00:0c:29:4d:af:b5 00:31:47:618815: ip4-input ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:31:47:618823: ip4-lookup fib 0 dpo-idx 34 flow hash: 0x ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:31:47:618833: ip4-load-balance fib 0 dpo-idx 34 flow hash: 0x ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:31:47:618837: ip4-mpls-label-imposition mpls-header:[16416:63:0:eos] 00:31:47:618844: mpls-label-imposition mpls-header:[211:255:0:neos] 00:31:47:618846: mpls-output adj-idx 3 : mpls via 14.1.1.2 host-eth2: 000c290fe2a8000c294dafa18847 flow hash: 0x : 0020: 00:31:47:618853: host-eth2-output host-eth2 MPLS: 00:0c:29:4d:af:a1 -> 00:0c:29:0f:e2:a8 label 211 exp 0, s 0, ttl 255 Thanks for your help. Thanks,Xyxue From: Neale Ranns (nranns) Date: 2017-11-29 16:37 To: 薛欣颖; Pablo Camarillo (pcamaril); vpp-dev Subject: Re: [vpp-dev] SR MPLS not effective Hi Xyxue, Here’s a hastily assembled guide on how I would do it; https://wiki.fd.io/view/VPP/Segment_Routing_for_MPLS I’ve not verified the configs myself. If you use it, please let me know any errors you find. Regards, neale From: 薛欣颖 Date: Wednesday, 29 November 2017 at 08:13 To: "Neale Ranns (nranns)" , "Pablo Camarillo (pcamaril)" , vpp-dev Subject: Re: Re: [vpp-dev] SR MPLS not effective After add the 'mpls local-label add non-eos 33 mpls-lookup-in-table 0 ' on P, the mistake still exist. ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] SR MPLS not effective
Hi Neale, I can't configure the command like this: 'VPP# sr mpls policy add bsid 999 next 210 209 208 207 206 205 204 203 202 201 unknown input `209 208 207 206 205 204 ...'' I configured the command like before. And the all info is shown below: packet info: 00:05:58:166326: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 78 snaplen 78 mac 66 net 80 sec 0x5a1feacb nsec 0x372a239a vlan 0 00:05:58:166355: ethernet-input IP4: 00:00:00:66:00:55 -> 00:0c:29:4d:af:b5 00:05:58:166385: ip4-input ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:05:58:166391: ip4-lookup fib 0 dpo-idx 33 flow hash: 0x ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:05:58:166401: ip4-load-balance fib 0 dpo-idx 33 flow hash: 0x ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:05:58:166405: ip4-mpls-label-imposition mpls-header:[16416:63:0:eos] //when I configured two layer label,this info is ' mpls-header:[101:63:0:eos] ' 00:05:58:166415: mpls-label-imposition mpls-header:[211:255:0:neos] 00:05:58:166416: mpls-output adj-idx 3 : mpls via 14.1.1.2 host-eth2: 000c290fe2a8000c294dafa18847 flow hash: 0x : 0020: 00:05:58:166424: host-eth2-output host-eth2 MPLS: 00:0c:29:4d:af:a1 -> 00:0c:29:0f:e2:a8 label 211 exp 0, s 0, ttl 255 VPP# show sr mpls policies VPP# show sr mpls policies SR MPLS policies: [0].- BSID: 999 Type: Default Segment Lists: [0].- < 210, 209, 208, 207, 206, 205, 204, 203, 202, 201 > --- VPP# show mpls fib label 999 MPLS-VRF:0, fib_index 0 999:neos/21 fib:0 index:26 locks:2 src:SR refs:1 index:27 locks:4 flags:shared, uPRF-list:28 len:1 itfs:[2, ] index:27 pl-index:27 mpls weight=1 pref=0 recursive: oper-flags:resolved, via 210 neos in fib:0 via-fib:27 via-dpo:[dpo-load-balance:29] Extensions: path:27 labels:209 208 207 206 205 204 203 202 201 forwarding: mpls-neos-chain [@0]: dpo-load-balance: [proto:mpls index:30 buckets:1 uRPF:28 to:[0:0]] [0] [@8]: mpls-label:[0]:[209:255:0:neos][208:255:0:neos][207:255:0:neos][206:255:0:neos][205:255:0:neos][204:255:0:neos][203:255:0:neos][202:255:0:neos][16416:0:1:neos] [@2]: dpo-load-balance: [proto:mpls index:29 buckets:1 uRPF:29 to:[0:0] via:[586:58600]] [0] [@8]: mpls-label:[3]:[211:255:0:neos] [@3]: mpls via 14.1.1.2 host-eth2: 000c290fe2a8000c294dafa18847 999:eos/21 fib:0 index:28 locks:4 src:SR refs:1 index:27 locks:4 flags:shared, uPRF-list:28 len:1 itfs:[2, ] index:27 pl-index:27 mpls weight=1 pref=0 recursive: oper-flags:resolved, via 210 neos in fib:0 via-fib:27 via-dpo:[dpo-load-balance:29] Extensions: path:27 labels:209 208 207 206 205 204 203 202 201 src:recursive-resolution cover:-1 refs:1 forwarding: mpls-eos-chain [@0]: dpo-load-balance: [proto:mpls index:31 buckets:1 uRPF:28 to:[0:0]] [0] [@8]: mpls-label:[2]:[209:255:0:neos][208:255:0:neos][207:255:0:neos][206:255:0:neos][205:255:0:neos][204:255:0:neos][203:255:0:neos][202:255:0:neos][16416:0:1:neos] [@2]: dpo-load-balance: [proto:mpls index:29 buckets:1 uRPF:29 to:[0:0] via:[586:58600]] [0] [@8]: mpls-label:[3]:[211:255:0:neos] [@3]: mpls via 14.1.1.2 host-eth2: 000c290fe2a8000c294dafa18847 VPP# show mpls fib label 210 MPLS-VRF:0, fib_index 0 210:neos/21 fib:0 index:27 locks:4 src:CLI refs:1 index:29 locks:2 flags:shared, uPRF-list:29 len:1 itfs:[2, ] index:29 pl-index:29 ip4 weight=1 pref=0 attached-nexthop: oper-flags:resolved, 14.1.1.2 host-eth2 [@0]: ipv4 via 14.1.1.2 host-eth2: 000c290fe2a8000c294dafa10800 Extensions: path:29 labels:211 src:recursive-resolution cover:-1 refs:1 forwarding: mpls-neos-chain [@0]: dpo-load-balance: [proto:mpls index:29 buckets:1 uRPF:29 to:[0:0] via:[686:68600]] [0] [@8]: mpls-label:[3]:[211:255:0:neos] [@3]: mpls via 14.1.1.2 host-eth2: 000c290fe2a8000c294dafa18847 Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-11-30 18:40 To: 薛欣颖; Pablo Camarillo (pcamaril); vpp-dev Subject: Re: [vpp-dev] SR MPLS not effective Hi Xyxue, To get a 10 label stack, you need to do; sr mpls policy add bsid 999 next 210 209 208 207 206 205 204 203 202 201 i.e. only use the ‘next’ keyword once. And then if you don’t get the desired result, could show me the following outputs; sh sr mpls polic sh mpls fib 999 sh mpls fib 210 st trace <<< for a ‘bad’ packet. thanks, neale From: 薛欣颖 Date: Thursday, 30 November 2017 at 10:23 To: "Neale Ranns (nranns)" , "Pablo Camarillo (pcamaril)"
Re: [vpp-dev] memory issues
Hi Chris， I see what you mean. I have two other questions: 1. 200k static routing use 5g memory is also large , how can I configure it use less physical memory? 2. How can I check the packet buffer memory? BTW, do you have the test similar with 'the memory size 200k static routing use'? Thanks, Xyxue From: Luke, Chris Date: 2017-12-05 21:43 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] memory issues You’re misreading top. “Virt” only means the virtual memory footprint of the process. This includes unused heap, shared libraries, anonymous mmap() regions etc. “RSS” is the resident-in-memory size. It’s actually using 5G. “show memory” also only shows the heap usage, it does not include packet buffer memory. Chris. From: on behalf of 薛欣颖 Date: Tuesday, December 5, 2017 at 00:51 To: vpp-dev Subject: [vpp-dev] memory issues Hi guys， I am using vpp v18.01-rc0~241-g4c9f2a8. I configured 200K static routing. When I 'show memory' in VPP, '150+k used'. But in my machine ,used almost 15g. After del the static routing ,almost using 16g memory. More info is shown below: VPP# show memory Thread 0 vpp_main heap 0x7fffb58e9000, 1076983 objects, 110755k of 151671k used, 15386k free, 13352k reclaimed, 16829k overhead, 1048572k capacity User heap index=0: heap 0x7fffb58e9000, 1076984 objects, 110755k of 151671k used, 15386k free, 13352k reclaimed, 16829k overhead, 1048572k capacity User heap index=1: heap 0x77ed4000, 2 objects, 128k of 130k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=2: heap 0x7fffb1e28000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k overhead, 8188k capacity User heap index=3: heap 0x7fffb1628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k overhead, 8188k capacity User heap index=4: heap 0x7fffaf628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k overhead, 32764k capacity User heap index=5: heap 0x7fffaf528000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=6: heap 0x7fffaf428000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=7: heap 0x7fffaf328000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=8: heap 0x7fffaf228000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=9: heap 0x7fffa7228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 131068k capacity User heap index=10: heap 0x7fff9f228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 131068k capacity User heap index=11: heap 0x7fff9b228000, 2 objects, 16k of 18k used, 92 free, 0 reclaimed, 1k overhead, 65532k capacity User heap index=12: heap 0x7fff9b028000, 2 objects, 256k of 258k used, 92 free, 0 reclaimed, 1k overhead, 2044k capacity User heap index=13: heap 0x7fff9ae28000, 2 objects, 240k of 242k used, 92 free, 0 reclaimed, 1k overhead, 2044k capacity User heap index=14: heap 0x7fff9ad28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=15: heap 0x7fff9ac28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=16: heap 0x7fff9ab28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=17: heap 0x7fff9a128000, 2 objects, 1k of 3k used, 88 free, 0 reclaimed, 1k overhead, 10236k capacity User heap index=18: heap 0x7fff9a028000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=19: heap 0x7fff99f28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=20: heap 0x7fff99e28000, 2 objects, 2k of 4k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=21: heap 0x7fff99d28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=22: heap 0x7fff99c28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=23: heap 0x7fff99b28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=24: heap 0x7fff99a28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=25: heap 0x7fff99928000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=26: heap 0x7fff97928000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 32764k capacity User heap index=27: heap 0x7fff95928000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 32764k capacity User heap index=28: heap 0x7fff94928000, 2 objects, 1k of 3k
Re: [vpp-dev] memory issues
Hi, Thank you for your reply. And there's another question : After delete the static routing , the RSS is not falling. Is this normal? Thanks, Xyxue From: Dave Barach (dbarach) Date: 2017-12-06 20:38 To: Luke, Chris; 薛欣颖; vpp-dev Subject: RE: [vpp-dev] memory issues Before we crank up the vppinfra memory leakfinder, etc. etc.: cat /proc/`pidof vpp`/maps and have a hard stare at the output. Configure one step at a time, looking for significant changes in the address space layout. HTH… Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Luke, Chris Sent: Tuesday, December 5, 2017 9:58 PM To: 薛欣颖 ; vpp-dev Subject: Re: [vpp-dev] memory issues I agree 5g is large, but I do not think this is the FIB. The default heap maxes out much sooner than that. Something else is going on. For DPDK, “show dpdk buffer” and otherwise “show physmem”. Chris. From: 薛欣颖 Date: Tuesday, December 5, 2017 at 20:06 To: Chris Luke , vpp-dev Subject: Re: Re: [vpp-dev] memory issues Hi Chris， I see what you mean. I have two other questions: 1. 200k static routing use 5g memory is also large , how can I configure it use less physical memory? 2. How can I check the packet buffer memory? BTW, do you have the test similar with 'the memory size 200k static routing use'? Thanks, Xyxue From: Luke, Chris Date: 2017-12-05 21:43 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] memory issues You’re misreading top. “Virt” only means the virtual memory footprint of the process. This includes unused heap, shared libraries, anonymous mmap() regions etc. “RSS” is the resident-in-memory size. It’s actually using 5G. “show memory” also only shows the heap usage, it does not include packet buffer memory. Chris. From: on behalf of 薛欣颖 Date: Tuesday, December 5, 2017 at 00:51 To: vpp-dev Subject: [vpp-dev] memory issues Hi guys， I am using vpp v18.01-rc0~241-g4c9f2a8. I configured 200K static routing. When I 'show memory' in VPP, '150+k used'. But in my machine ,used almost 15g. After del the static routing ,almost using 16g memory. More info is shown below: VPP# show memory Thread 0 vpp_main heap 0x7fffb58e9000, 1076983 objects, 110755k of 151671k used, 15386k free, 13352k reclaimed, 16829k overhead, 1048572k capacity User heap index=0: heap 0x7fffb58e9000, 1076984 objects, 110755k of 151671k used, 15386k free, 13352k reclaimed, 16829k overhead, 1048572k capacity User heap index=1: heap 0x77ed4000, 2 objects, 128k of 130k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=2: heap 0x7fffb1e28000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k overhead, 8188k capacity User heap index=3: heap 0x7fffb1628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k overhead, 8188k capacity User heap index=4: heap 0x7fffaf628000, 2 objects, 512k of 514k used, 92 free, 0 reclaimed, 1k overhead, 32764k capacity User heap index=5: heap 0x7fffaf528000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=6: heap 0x7fffaf428000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=7: heap 0x7fffaf328000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=8: heap 0x7fffaf228000, 2 objects, 120k of 122k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=9: heap 0x7fffa7228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 131068k capacity User heap index=10: heap 0x7fff9f228000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 131068k capacity User heap index=11: heap 0x7fff9b228000, 2 objects, 16k of 18k used, 92 free, 0 reclaimed, 1k overhead, 65532k capacity User heap index=12: heap 0x7fff9b028000, 2 objects, 256k of 258k used, 92 free, 0 reclaimed, 1k overhead, 2044k capacity User heap index=13: heap 0x7fff9ae28000, 2 objects, 240k of 242k used, 92 free, 0 reclaimed, 1k overhead, 2044k capacity User heap index=14: heap 0x7fff9ad28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=15: heap 0x7fff9ac28000, 5 objects, 8k of 10k used, 168 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=16: heap 0x7fff9ab28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=17: heap 0x7fff9a128000, 2 objects, 1k of 3k used, 88 free, 0 reclaimed, 1k overhead, 10236k capacity User heap index=18: heap 0x7fff9a028000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=19: heap 0x7fff99f28000, 2 objects, 8k of 10k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity User heap index=20: heap 0x7fff99e28000, 2 objects, 2k of 4k used, 92 free, 0 reclaimed, 1k overhead, 1020k capacity
Re: [vpp-dev] assertion in gpe testing
Hi Florin，
After starting VPP, I just configured two commands, first is "lisp enable on",
another command(not congfig in vpp CLI) is to directly pass parameter
parameters to vl_api_gpe_add_del_fwd_entry_t_handler. This problem exists every
time in the 18.01 version of VPP
Breakpoint 1, vl_api_gpe_add_del_fwd_entry_t_handler (mp=0x2b8413872f9c) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/lisp-gpe/lisp_gpe_api.c:328
328 {
(gdb) p *mp
$1 = {_vl_msg_id = 16129, client_index = 805306625, context = 0, is_add = 1
'\001', eid_type = 0 '\000', rmt_eid =
"1.1.3.1\000\000\000\000\000\000\000\000",
lcl_eid = "1.1.2.1\000\000\000\000\000\000\000\000", rmt_len = 24 '\030',
lcl_len = 24 '\030', vni = 16777216, dp_table = 16777216, action = 4 '\004',
loc_num = 33554432,
locs = 0x2b8413872fd7}
(gdb)
Thanks,
Xyxue
From: Florin Coras
Date: 2017-12-11 10:37
To: 薛欣颖
CC: vpp-dev
Subject: Re: [vpp-dev] assertion in gpe testing
Hi Xyxue,
Did you by chance configure an ip or a route through the gpe interface? If yes,
then that is probably the issue. If not, could you provide more details
regarding your configuration.
Thanks,
Florin
On Dec 10, 2017, at 6:25 PM, 薛欣颖 wrote:
Hi guys，
There is an assertion when I was configuring the GPE service, and I didn't find
a solution. Can you help me see the reasons for it?
Breakpoint 1, vl_api_gpe_add_del_fwd_entry_t_handler (mp=0x2b8413872f9c) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/lisp-gpe/lisp_gpe_api.c:328
328 {
(gdb) p *mp
$1 = {_vl_msg_id = 16129, client_index = 805306625, context = 0, is_add = 1
'\001', eid_type = 0 '\000', rmt_eid =
"1.1.3.1\000\000\000\000\000\000\000\000",
lcl_eid = "1.1.2.1\000\000\000\000\000\000\000\000", rmt_len = 24 '\030',
lcl_len = 24 '\030', vni = 16777216, dp_table = 16777216, action = 4 '\004',
loc_num = 33554432,
locs = 0x2b8413872fd7}
(gdb) c
Continuing.
Program received signal SIGABRT, Aborted.
0x2b8412519c37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x2b8412519c37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x2b841251d028 in __GI_abort () at abort.c:89
#2 0x00406e9b in os_panic () at
/home/vpp/17.07_x64/vpp/build-data/../src/vpp/vnet/main.c:294
#3 0x2b8411e36b98 in debugger () at
/home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/error.c:84
#4 0x2b8411e36f9f in _clib_error (how_to_die=2, function_name=0x0,
line_number=0, fmt=0x2b8411a87488 "%s:%d (%s) assertion `%s' fails")
at /home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/error.c:143
#5 0x2b84117d9f14 in lisp_gpe_build_rewrite (vnm=0x2b8411e07560
, sw_if_index=3, link_type=VNET_LINK_ARP, dst_address=0x0)
at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/lisp-gpe/lisp_gpe_adjacency.c:370
#6 0x2b8411985a76 in vnet_rewrite_for_sw_interface (vnm=0x2b8411e07560
, link_type=VNET_LINK_ARP, sw_if_index=3, node_index=312,
dst_address=0x0, rw=0x2b841386a780,
max_rewrite_bytes=112) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/adj/rewrite.c:133
#7 0x2b8411978012 in adj_glean_add_or_lock (proto=FIB_PROTOCOL_IP4,
sw_if_index=3, nh_addr=0x0) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/adj/adj_glean.c:73
#8 0x2b84119683b6 in fib_path_attached_get_adj (path=0x2b8413866bc8,
link=VNET_LINK_IP4) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/fib/fib_path.c:719
#9 0x2b841196a7a2 in fib_path_resolve (path_index=22) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/fib/fib_path.c:1880
#10 0x2b8411964406 in fib_path_list_resolve (path_list=0x2b841386619c) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/fib/fib_path_list.c:567
#11 0x2b84119648bd in fib_path_list_create
(flags=FIB_PATH_LIST_FLAG_SHARED, rpaths=0x2b8413a96080) at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/fib/fib_path_list.c:725
#12 0x2b841195ff39 in fib_entry_src_lisp_path_swap (src=0x2b8413872dd4,
entry=0x2b84138700c4, pl_flags=FIB_PATH_LIST_FLAG_NONE, paths=0x2b8413a96080)
at
/home/vpp/17.07_x64/vpp/build-data/../src/vnet/fib/fib_entry_src_lisp.c:42
#13 0x2b841195b529 in fib_entry_src_action_path_swap
(fib_entry=0x2b84138700c4, source=FIB_SOURCE_LISP, flags=FIB_ENTRY_FLAG_NONE,
rpaths=0x2b8413a96080)
at /home/vpp/17.07_x64/vpp/build-data/../src/vnet/fib/fib_entry_src.c:1191
#14 0x2b8411956c3c in fib_entry_create (fib_index=1, prefix=0x2b8413674a30,
source=FIB_SOURCE_LISP, flags=FIB_ENTRY_FLAG_NONE, paths=0x2b8413a96080)
at /home/vpp/17.07_x64/vpp/build-data/../src/vnet/fib/fib_entry.c:828
#15 0x2b8411947a39 in fib_table_entry_update (fib_index=1,
prefix=0x2b8413674a30, source=FIB_SOURCE_LISP, flags=FIB_ENTRY_F
[vpp-dev] mpls tunnel in l2 mode del error
Hi guys, I'm testing L2VPN. After I del the mpls tunnel ,there is a 'signal SIGABRT'. My configuration and more info is shown below: configuration: create host-interface name eth2 mac 00:0c:29:0f:e2:a8 create host-interface name eth5 mac 00:0c:29:0f:e2:c6 set interface state host-eth2 up set interface state host-eth5 up mpls table add 0 set interface mpls host-eth2 enable set interface ip address host-eth2 14.1.1.2/24 mpls local-label add non-eos 33 mpls-lookup-in-table 0 create bridge-domain 1 set interface l2 bridge host-eth5 1 create mpls tunnel out-label 1023 out-label 1053 via 14.1.1.1 host-eth2 l2-only set interface l2 bridge mpls-tunnel0 1 mpls local-label add eos 53 l2-input-on mpls-tunnel0 set interface state mpls-tunnel0 up Program received signal SIGABRT, Aborted. 0x2b871bf02c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: (gdb) bt #0 0x2b871bf02c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x2b871bf06028 in __GI_abort () at abort.c:89 #2 0x00406e8b in os_panic () at /home/VPP/build-data/../src/vpp/vnet/main.c:294 #3 0x2b871b820b88 in debugger () at /home/VPP/build-data/../src/vppinfra/error.c:84 #4 0x2b871b820f8f in _clib_error (how_to_die=2, function_name=0x0, line_number=0, fmt=0x2b871b462138 "%s:%d (%s) assertion `%s' fails") at /home/VPP/build-data/../src/vppinfra/error.c:143 #5 0x2b871b14c2b0 in mpls_tunnel_tx (vm=0x2b871adab7e0 , node=0x2b871d024200, frame=0x2b871d8a7240) at /home/VPP/build-data/../src/vnet/mpls/mpls_tunnel.c:490 #6 0x2b871ab2d178 in dispatch_node (vm=0x2b871adab7e0 , node=0x2b871d024200, type=VLIB_NODE_TYPE_INTERNAL, dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x2b871d8a7240, last_time_stamp=60292005734565) at /home/VPP/build-data/../src/vlib/main.c:1010 #7 0x2b871ab2d75b in dispatch_pending_node (vm=0x2b871adab7e0 , pending_frame_index=6, last_time_stamp=60292005734565) at /home/VPP/build-data/../src/vlib/main.c:1160 #8 0x2b871ab2f90b in vlib_main_or_worker_loop (vm=0x2b871adab7e0 , is_main=1) at /home/VPP/build-data/../src/vlib/main.c:1629 #9 0x2b871ab2f9ba in vlib_main_loop (vm=0x2b871adab7e0 ) at /home/VPP/build-data/../src/vlib/main.c:1648 #10 0x2b871ab30103 in vlib_main (vm=0x2b871adab7e0 , input=0x2b871ce96fb0) at /home/VPP/build-data/../src/vlib/main.c:1806 #11 0x2b871ab72680 in thread0 (arg=47859271120864) at /home/VPP/build-data/../src/vlib/unix/main.c:617 #12 0x2b871b835560 in clib_calljmp () at /home/VPP/build-data/../src/vppinfra/longjmp.S:128 #13 0x7fffe00f3af0 in ?? () #14 0x2b871ab72b2a in vlib_unix_main (argc=4, argv=0x7fffe00f4d88) at /home/VPP/build-data/../src/vlib/unix/main.c:681 #15 0x00406b67 in main (argc=4, argv=0x7fffe00f4d88) at /home/VPP/build-data/../src/vpp/vnet/main.c:233 (gdb) Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] mpls tunnel in l2 mode del error
Hi Neale， After remove the tunnel from the bridge domain, the problem solved. Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-12-13 17:33 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] mpls tunnel in l2 mode del error Hi Xyxue, Did you remove the tunnel from the bridge before it was deleted? /neale From: on behalf of 薛欣颖 Date: Wednesday, 13 December 2017 at 04:14 To: vpp-dev Subject: [vpp-dev] mpls tunnel in l2 mode del error Hi guys, I'm testing L2VPN. After I del the mpls tunnel ,there is a 'signal SIGABRT'. My configuration and more info is shown below: configuration: create host-interface name eth2 mac 00:0c:29:0f:e2:a8 create host-interface name eth5 mac 00:0c:29:0f:e2:c6 set interface state host-eth2 up set interface state host-eth5 up mpls table add 0 set interface mpls host-eth2 enable set interface ip address host-eth2 14.1.1.2/24 mpls local-label add non-eos 33 mpls-lookup-in-table 0 create bridge-domain 1 set interface l2 bridge host-eth5 1 create mpls tunnel out-label 1023 out-label 1053 via 14.1.1.1 host-eth2 l2-only set interface l2 bridge mpls-tunnel0 1 mpls local-label add eos 53 l2-input-on mpls-tunnel0 set interface state mpls-tunnel0 up Program received signal SIGABRT, Aborted. 0x2b871bf02c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: (gdb) bt #0 0x2b871bf02c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x2b871bf06028 in __GI_abort () at abort.c:89 #2 0x00406e8b in os_panic () at /home/VPP/build-data/../src/vpp/vnet/main.c:294 #3 0x2b871b820b88 in debugger () at /home/VPP/build-data/../src/vppinfra/error.c:84 #4 0x2b871b820f8f in _clib_error (how_to_die=2, function_name=0x0, line_number=0, fmt=0x2b871b462138 "%s:%d (%s) assertion `%s' fails") at /home/VPP/build-data/../src/vppinfra/error.c:143 #5 0x2b871b14c2b0 in mpls_tunnel_tx (vm=0x2b871adab7e0 , node=0x2b871d024200, frame=0x2b871d8a7240) at /home/VPP/build-data/../src/vnet/mpls/mpls_tunnel.c:490 #6 0x2b871ab2d178 in dispatch_node (vm=0x2b871adab7e0 , node=0x2b871d024200, type=VLIB_NODE_TYPE_INTERNAL, dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x2b871d8a7240, last_time_stamp=60292005734565) at /home/VPP/build-data/../src/vlib/main.c:1010 #7 0x2b871ab2d75b in dispatch_pending_node (vm=0x2b871adab7e0 , pending_frame_index=6, last_time_stamp=60292005734565) at /home/VPP/build-data/../src/vlib/main.c:1160 #8 0x2b871ab2f90b in vlib_main_or_worker_loop (vm=0x2b871adab7e0 , is_main=1) at /home/VPP/build-data/../src/vlib/main.c:1629 #9 0x2b871ab2f9ba in vlib_main_loop (vm=0x2b871adab7e0 ) at /home/VPP/build-data/../src/vlib/main.c:1648 #10 0x2b871ab30103 in vlib_main (vm=0x2b871adab7e0 , input=0x2b871ce96fb0) at /home/VPP/build-data/../src/vlib/main.c:1806 #11 0x2b871ab72680 in thread0 (arg=47859271120864) at /home/VPP/build-data/../src/vlib/unix/main.c:617 #12 0x2b871b835560 in clib_calljmp () at /home/VPP/build-data/../src/vppinfra/longjmp.S:128 #13 0x7fffe00f3af0 in ?? () #14 0x2b871ab72b2a in vlib_unix_main (argc=4, argv=0x7fffe00f4d88) at /home/VPP/build-data/../src/vlib/unix/main.c:681 #15 0x00406b67 in main (argc=4, argv=0x7fffe00f4d88) at /home/VPP/build-data/../src/vpp/vnet/main.c:233 (gdb) Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] a problem about dhcp
Hi guys, I'm testing the dhcp function. There is a problem : when I delete the dhcp client, the address del success, but there is no 'release message' to server. Is there a plan to solve this problem? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] a problem about dhcp
Hi Neale, I have filed a JIRA ticket : VPP-1104. Thank you for your help. Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-12-18 00:20 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] a problem about dhcp Hi Xyxue, Please file a JIRA ticket at: https://jira.fd.io/secure/Dashboard.jspa /neale From: on behalf of 薛欣颖 Date: Saturday, 16 December 2017 at 07:26 To: vpp-dev Subject: [vpp-dev] a problem about dhcp Hi guys, I'm testing the dhcp function. There is a problem : when I delete the dhcp client, the address del success, but there is no 'release message' to server. Is there a plan to solve this problem? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] problem in delete the 'sr mpls steer'
Hi Pablo, After the update of the code, the problem is resolved. Thank you for your help. Thanks, Xyxue From: Pablo Camarillo (pcamaril) Date: 2017-12-21 06:56 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] problem in delete the 'sr mpls steer' Hi Xyxue, I’m unable to reproduce the crash. What was your initial state before typing that CLI? _____ _ ___ __/ __/ _ \ (_)__| | / / _ \/ _ \ _/ _// // / / / _ \ | |/ / ___/ ___/ /_/ /(_)_/\___/ |___/_/ /_/ DBGvpp# DBGvpp# DBGvpp# DBGvpp# mpls table add 9 DBGvpp# mpls table add 0 DBGvpp# sr mpls policy add bsid 999 next 202 next 203 next 204 DBGvpp# sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999 DBGvpp# sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999 del DBGvpp# DBGvpp# Thank you. Cheers, Pablo. From: on behalf of 薛欣颖 Date: Wednesday, 20 December 2017 at 10:26 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] problem in delete the 'sr mpls steer' Hi guys, I'm testing sr mpls. When I del the 'sr mpls steer' ,there is a 'signal SIGABRT'. My configuration and more info is shown below: configuration: mpls table add 9 mpls table add 0 sr mpls policy add bsid 999 next 202 next 203 next 204 sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999 sr mpls steer l3 23.1.1.1/24 via sr policy bsid 999 del Program received signal SIGABRT, Aborted. 0x2b69d0d5bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录. (gdb) bt #0 0x2b69d0d5bc37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x2b69d0d5f028 in __GI_abort () at abort.c:89 #2 0x00405d2b in os_panic () at /home/VPP/build-data/../src/vpp/vnet/main.c:294 #3 0x2b69d0679b88 in debugger () at /home/VPP/build-data/../src/vppinfra/error.c:84 #4 0x2b69d0679f8f in _clib_error (how_to_die=2, function_name=0x0, line_number=0, fmt=0x2b69d0301438 "%s:%d (%s) assertion `%s' fails") at /home/VPP/build-data/../src/vppinfra/error.c:143 #5 0x2b69d018ddfb in fib_table_get (index=1, proto=FIB_PROTOCOL_IP4) at /home/VPP/build-data/../src/vnet/fib/fib_table.c:33 #6 0x2b69d018e2df in fib_table_lookup_exact_match (fib_index=1, prefix=0x2b69d22d6980) at /home/VPP/build-data/../src/vnet/fib/fib_table.c:98 #7 0x2b69d018faf1 in fib_table_entry_delete (fib_index=1, prefix=0x2b69d22d6980, source=FIB_SOURCE_SR) at /home/VPP/build-data/../src/vnet/fib/fib_table.c:900 #8 0x2b69d0079392 in sr_mpls_steering_policy (is_del=1, bsid=999, sr_policy_index=4294967295, table_id=4294967295, prefix=0x2b69d22d6a70, mask_width=24, traffic_type=4 '\004') at /home/VPP/build-data/../src/vnet/srmpls/sr_mpls_steering.c:112 #9 0x2b69d007aa5b in sr_mpls_steer_policy_command_fn (vm=0x2b69cfbea800 , input=0x2b69d22d6ec0, cmd=0x2b69d223561c) at /home/VPP/build-data/../src/vnet/srmpls/sr_mpls_steering.c:356 VPP# show mpls fib MPLS-VRF:9, fib_index 0 ip4-explicit-null:neos/21 fib:0 index:10 locks:2 ... MPLS-VRF:0, fib_index -1 ip4-explicit-null:neos/21 fib:1 index:16 locks:2 ... Does the wrong fib_index have an impact on this problem? What could I do to slove the problem? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] 'pool_elt_at_index' Relative Addressing Cause a Mistake
Hi guys, I'm testing ikev2. When I initiate a sa succeed(pr1), then add the other one (pr2), the sa->pr1->name is rewritten. After viewing I find the 'pool_elt_at_index' is relative addressing . And the 'pool_base' may change when use the pointer we preserved before. eg:'pool_elt_at_index (km->profiles, p[0]);' How can we solve the problem? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] 'vlib_buffer_alloc' alloc an uninitialized memory
Hi guys,
I'm testing ikev2. In the function 'ikev2_rekey_child_sa_internal',:
bi0 = ikev2_get_new_ike_header_buff (vm, &ike0);
//The following is the debug code
vlib_buffer_t *b0;
b0 = vlib_get_buffer (vm, bi0);
(gdb) p *(vnet_buffer_opaque_t *)(b0->opaque)
$1 = {
sw_if_index = {2, 4294967295},//The rest of the value is correct
l2_hdr_offset = 0,
l3_hdr_offset = 0,
l4_hdr_offset = 0,
The wrong may cause an error in 'ip4_lookup_inline '.
BTW, the problem doesn't happen every time.
Thanks,
Xyxue
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] question about load balance
Hi guys, I'm testing routing load balance. There is a question : When I configured 1:2 , the actual effect 3:5. My configuration and more info is shown below: configuration: ip route add 4.1.1.1/24 via ip4-address 1.1.1.2 interface host-eth0 weight 1 ip route add 4.1.1.1/24 via ip4-address 2.1.1.2 interface host-eth4 weight 2 The actual effect: 4.1.1.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:22 buckets:8 uRPF:29 to:[0:0]] [0] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [1] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [2] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [3] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [4] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [5] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 [6] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 [7] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 How can I make the actual effect the same as my configuration? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] question about load balance
Hi Neale, I know what you mean. What should I do to match exactly I configured? And ignore constraints 'a load-balance is always a power of 2'. Thanks, Xyxue From: Neale Ranns (nranns) Date: 2018-01-09 20:58 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] question about load balance Hi Xyxue, It does match your configuration. You requested a 2:1 ratio un-equal cost load balancing, you got a 5:3, which VPP considers to be close enough. It’s not exact because the number of buckets in a load-balance is always a power of 2. /neale From: on behalf of 薛欣颖 Date: Tuesday, 9 January 2018 at 12:26 To: vpp-dev Subject: [vpp-dev] question about load balance Hi guys, I'm testing routing load balance. There is a question : When I configured 1:2 , the actual effect 3:5. My configuration and more info is shown below: configuration: ip route add 4.1.1.1/24 via ip4-address 1.1.1.2 interface host-eth0 weight 1 ip route add 4.1.1.1/24 via ip4-address 2.1.1.2 interface host-eth4 weight 2 The actual effect: 4.1.1.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:22 buckets:8 uRPF:29 to:[0:0]] [0] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [1] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [2] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [3] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [4] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [5] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 [6] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 [7] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 How can I make the actual effect the same as my configuration? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] question about load balance
Hi， My question has been solved. Thank you for your help! Thanks, Xyxue From: Neale Ranns (nranns) Date: 2018-01-10 23:47 To: Pierre Pfister (ppfister); 薛欣颖 CC: vpp-dev Subject: Re: [vpp-dev] question about load balance You could also try adjusting in vnet/dpo/load_balance.c: /* * distribution error tolerance for load-balancing */ const f64 multipath_next_hop_error_tolerance = 0.1; to a lower values, until it meets your needs. Note this value is not exposed to the CLI/API for adjustment. /neale From: "Pierre Pfister (ppfister)" Date: Wednesday, 10 January 2018 at 10:39 To: 薛欣颖 Cc: "Neale Ranns (nranns)" , vpp-dev Subject: Re: [vpp-dev] question about load balance Hello, You will not be able to get an exact match on 1/3 - 2/3 traffic sharing since 3 is not a power of two. If you want to get something closer, you may try to increase the values to get a better approximation. For instance, 43 and 85 have a sum of 128 with 43/128 = 0.3359375, which is close to the 0.3 you are looking for. - Pierre Le 10 janv. 2018 à 07:36, 薛欣颖 a écrit : Hi Neale, I know what you mean. What should I do to match exactly I configured? And ignore constraints 'a load-balance is always a power of 2'. Thanks, Xyxue From: Neale Ranns (nranns) Date: 2018-01-09 20:58 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] question about load balance Hi Xyxue, It does match your configuration. You requested a 2:1 ratio un-equal cost load balancing, you got a 5:3, which VPP considers to be close enough. It’s not exact because the number of buckets in a load-balance is always a power of 2. /neale From: on behalf of 薛欣颖 Date: Tuesday, 9 January 2018 at 12:26 To: vpp-dev Subject: [vpp-dev] question about load balance Hi guys, I'm testing routing load balance. There is a question : When I configured 1:2 , the actual effect 3:5. My configuration and more info is shown below: configuration: ip route add 4.1.1.1/24 via ip4-address 1.1.1.2 interface host-eth0 weight 1 ip route add 4.1.1.1/24 via ip4-address 2.1.1.2 interface host-eth4 weight 2 The actual effect: 4.1.1.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:22 buckets:8 uRPF:29 to:[0:0]] [0] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [1] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [2] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [3] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [4] [@5]: ipv4 via 2.1.1.2 host-eth4: 000c296db08c2c534a0393540800 [5] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 [6] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 [7] [@5]: ipv4 via 1.1.1.2 host-eth0: 000c296db078fc4dd4dad8af0800 How can I make the actual effect the same as my configuration? Thanks, Xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] problem in SRV6
Hi Pablo, My configuration and the trace info is shown below: VPP1： create host-interface name eth0 mac 00:0c:29:4d:af:8d create host-interface name eth4 mac 00:0c:29:4d:af:b5 set interface state host-eth0 up set interface state host-eth4 up enable ip6 interface host-eth0 set interface ip address host-eth0 a::1/64 enable ip6 interface host-eth4 set interface ip address host-eth4 2001::1/64 create loopback interface instance 0 set interface state loop0 up set interface ip address loop0 1::1/128 ip route add 2::2/128 via ip6-address a::2 host-eth0 ip route add 3::3/128 via ip6-address a::2 host-eth0 ip route add b::1/64 via ip6-address a::2 host-eth0 set sr encaps source addr 1::1 sr policy add bsid 1::1:999 next 2::2 next 3::3 sr steer l3 2003::1/64 via sr policy bsid 1::1:999 trace: 02:01:10:720008: af-packet-input af_packet: hw_if_index 3 next-index 4 tpacket2_hdr: status 0x2001 len 98 snaplen 98 mac 66 net 80 sec 0x5a571037 nsec 0x28091fb7 vlan 0 02:01:10:720040: ethernet-input IP6: 00:22:12:66:00:33 -> 00:0c:29:4d:af:b5 02:01:10:720068: ip6-input ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720075: ip6-lookup fib 0 dpo-idx 35 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720085: ip6-load-balance fib 0 dpo-idx 35 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720089: sr-pl-rewrite-encaps SR-policy-rewrite: src 1::1 dst 2::2 02:01:10:720096: ip6-lookup fib 0 dpo-idx 9 flow hash: 0x IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 64, payload length 140 02:01:10:720097: ip6-rewrite tx_sw_if_index 1 adj-idx 9 : ipv6 via a::2 host-eth0: 000c29198e58000c294daf8d86dd flow hash: 0x : 000c29198e58000c294daf8d86dd608c2b3f0001 0020: 0001000200022906040202002003 0040: 0005000300030002 0060: 0002602c3a3f2001 02:01:10:720103: host-eth0-output host-eth0 IP6: 00:0c:29:4d:af:8d -> 00:0c:29:19:8e:58 IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 63, payload length 140 VPP2： create host-interface name eth0 mac 00:0c:29:19:8e:58 create host-interface name eth2 mac 00:0c:29:19:8e:6c set interface state host-eth0 up set interface state host-eth2 up enable ip6 interface host-eth0 enable ip6 interface host-eth2 set interface ip address host-eth0 a::2/64 set interface ip address host-eth2 b::1/64 create loopback interface instance 0 set interface state loop0 up set interface ip address loop0 2::2/128 ip route add 1::1/128 via ip6-address a::1 host-eth0 ip route add 3::3/128 via ip6-address b::2 host-eth2 sr localsid address 2::2 behavior end trace: 00:08:01:715943: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 178 snaplen 178 mac 66 net 80 sec 0x5a571fb9 nsec 0x2c338c0a vlan 0 00:08:01:715969: ethernet-input IP6: 00:0c:29:4d:af:8d -> 00:0c:29:19:8e:58 00:08:01:716017: ip6-input IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 63, payload length 124 00:08:01:716022: ip6-lookup fib 0 dpo-idx 13 flow hash: 0x IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 63, payload length 124 00:08:01:716030: ip6-local IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 63, payload length 124 00:08:01:716037: ip6-punt IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 63, payload length 124 00:08:01:716044: error-punt ip6-input: unknown ip protocol VPP3： create host-interface name eth2 mac 00:0c:29:a6:67:7c create host-interface name eth5 mac 00:0c:29:a6:67:9a set interface state host-eth2 up set interface state host-eth5 up enable ip6 interface host-eth2 enable ip6 interface host-eth5 set interface ip address host-eth2 b::2/64 set interface ip address host-eth5 2003::1/64 create loopback interface instance 0 set interface state loop0 up set interface ip address loop0 3::3/128 ip route add 2::2/128 via ip6-address b::1 host-eth2 ip route add 1::1/128 via ip6-address b::1 host-eth2 ip route add a::1/64 via ip6-address b::1 host-eth2 Thanks, Xyxue From: Pablo Camarillo (pcamaril) Date: 2018-01-12 15:56 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] problem in SRV6 Hi Xyxue, What is your entire config at VPP2? Looks like a misconfiguration in VPP2. Thanks, Pablo. From: on behalf of 薛欣颖 Date: Friday, 12 January 2018 at 02:04 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev]
Re: [vpp-dev] problem in SRV6
Hi Pablo, According to the following configs, since the SRv6 SID is not an interface address, VPP1: sr policy add bsid 1::1:999 next 2::2 next 3::3 , how to find VPP2 2::2？ The packets could not find the next-hop and out-if. trace in VPP1: 00:20:47:954483: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x2001 len 98 snaplen 98 mac 66 net 80 sec 0x5a59a8b5 nsec 0x287052ff vlan 0 00:20:47:954525: ethernet-input IP6: 00:22:12:66:00:33 -> 00:0c:29:4d:af:b5 00:20:47:954649: ip6-input ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 00:20:47:954664: ip6-lookup fib 0 dpo-idx 20 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 00:20:47:954687: ip6-load-balance fib 0 dpo-idx 20 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 00:20:47:954695: sr-pl-rewrite-encaps SR-policy-rewrite: src 1::1 dst 2::2 00:20:47:954709: ip6-lookup fib 0 dpo-idx 1 flow hash: 0x IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 64, payload length 124 00:20:47:954714: ip6-drop IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 64, payload length 124 00:20:47:954729: error-drop ethernet-input: no error Thanks， Xyxue From: Pablo Camarillo (pcamaril) Date: 2018-01-12 18:53 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] problem in SRV6 Hi Xyxue, The SRv6 SID is not an interface address. Hence creating the loopback interfaces and adding the SID address on the loopback is not necessary. Find below some corrected configs. (you were also missing the config on VPP3). Thanks. Cheers, Pablo. From: 薛欣颖 Date: Friday, 12 January 2018 at 09:19 To: "Pablo Camarillo (pcamaril)" , vpp-dev Subject: Re: Re: [vpp-dev] problem in SRV6 Hi Pablo, My configuration and the trace info is shown below: VPP1： create host-interface name eth0 mac 00:0c:29:4d:af:8d create host-interface name eth4 mac 00:0c:29:4d:af:b5 set interface state host-eth0 up set interface state host-eth4 up enable ip6 interface host-eth0 set interface ip address host-eth0 a::1/64 enable ip6 interface host-eth4 set interface ip address host-eth4 2001::1/64 create loopback interface instance 0 set interface state loop0 up set interface ip address loop0 1::1/128 ip route add 2::2/128 via ip6-address a::2 host-eth0 ip route add 3::3/128 via ip6-address a::2 host-eth0 ip route add b::1/64 via ip6-address a::2 host-eth0 set sr encaps source addr 1::1 sr policy add bsid 1::1:999 next 2::2 next 3::3 sr steer l3 2003::1/64 via sr policy bsid 1::1:999 trace: 02:01:10:720008: af-packet-input af_packet: hw_if_index 3 next-index 4 tpacket2_hdr: status 0x2001 len 98 snaplen 98 mac 66 net 80 sec 0x5a571037 nsec 0x28091fb7 vlan 0 02:01:10:720040: ethernet-input IP6: 00:22:12:66:00:33 -> 00:0c:29:4d:af:b5 02:01:10:720068: ip6-input ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720075: ip6-lookup fib 0 dpo-idx 35 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720085: ip6-load-balance fib 0 dpo-idx 35 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720089: sr-pl-rewrite-encaps SR-policy-rewrite: src 1::1 dst 2::2 02:01:10:720096: ip6-lookup fib 0 dpo-idx 9 flow hash: 0x IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 64, payload length 140 02:01:10:720097: ip6-rewrite tx_sw_if_index 1 adj-idx 9 : ipv6 via a::2 host-eth0: 000c29198e58000c294daf8d86dd flow hash: 0x : 000c29198e58000c294daf8d86dd608c2b3f0001 0020: 0001000200022906040202002003 0040: 0005000300030002 0060: 0002602c3a3f2001 02:01:10:720103: host-eth0-output host-eth0 IP6: 00:0c:29:4d:af:8d -> 00:0c:29:19:8e:58 IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 63, payload length 140 VPP2： create host-interface name eth0 mac 00:0c:29:19:8e:58 create host-interface name eth2 mac 00:0c:29:19:8e:6c set interface state host-eth0 up set interface state host-eth2 up enable ip6 interface host-eth0 enable ip6 interface host-eth2 set interface ip address host-eth0 a::2/64 set interface ip address host-eth2 b::1/64 create loopback interface instance 0 set interface state loop0 up set interface ip address loop0 2
Re: [vpp-dev] problem in SRV6
Hi Pablo, Thank you very much for your help . After following your advise the problem has been solved. Thanks, Xyxue From: Pablo Camarillo (pcamaril) Date: 2018-01-15 15:57 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] problem in SRV6 Xyxue, You need the corresponding FIB entry at R1 for VPP2 2::2. Typically you would route an entire VPP2 locator prefix for SRv6 SIDs, and then you would instantiate within that prefix as many functions as desired on VPP2. Notice that in the config below you do have the ip route command, so I guess that you didn’t type it this time. Thanks. Cheers, Pablo. From: 薛欣颖 Date: Saturday, 13 January 2018 at 07:46 To: "Pablo Camarillo (pcamaril)" , vpp-dev Subject: Re: Re: [vpp-dev] problem in SRV6 Hi Pablo, According to the following configs, since the SRv6 SID is not an interface address, VPP1: sr policy add bsid 1::1:999 next 2::2 next 3::3 , how to find VPP2 2::2？ The packets could not find the next-hop and out-if. trace in VPP1: 00:20:47:954483: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x2001 len 98 snaplen 98 mac 66 net 80 sec 0x5a59a8b5 nsec 0x287052ff vlan 0 00:20:47:954525: ethernet-input IP6: 00:22:12:66:00:33 -> 00:0c:29:4d:af:b5 00:20:47:954649: ip6-input ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 00:20:47:954664: ip6-lookup fib 0 dpo-idx 20 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 00:20:47:954687: ip6-load-balance fib 0 dpo-idx 20 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 00:20:47:954695: sr-pl-rewrite-encaps SR-policy-rewrite: src 1::1 dst 2::2 00:20:47:954709: ip6-lookup fib 0 dpo-idx 1 flow hash: 0x IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 64, payload length 124 00:20:47:954714: ip6-drop IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 64, payload length 124 00:20:47:954729: error-drop ethernet-input: no error Thanks， Xyxue From: Pablo Camarillo (pcamaril) Date: 2018-01-12 18:53 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] problem in SRV6 Hi Xyxue, The SRv6 SID is not an interface address. Hence creating the loopback interfaces and adding the SID address on the loopback is not necessary. Find below some corrected configs. (you were also missing the config on VPP3). Thanks. Cheers, Pablo. From: 薛欣颖 Date: Friday, 12 January 2018 at 09:19 To: "Pablo Camarillo (pcamaril)" , vpp-dev Subject: Re: Re: [vpp-dev] problem in SRV6 Hi Pablo, My configuration and the trace info is shown below: VPP1： create host-interface name eth0 mac 00:0c:29:4d:af:8d create host-interface name eth4 mac 00:0c:29:4d:af:b5 set interface state host-eth0 up set interface state host-eth4 up enable ip6 interface host-eth0 set interface ip address host-eth0 a::1/64 enable ip6 interface host-eth4 set interface ip address host-eth4 2001::1/64 create loopback interface instance 0 set interface state loop0 up set interface ip address loop0 1::1/128 ip route add 2::2/128 via ip6-address a::2 host-eth0 ip route add 3::3/128 via ip6-address a::2 host-eth0 ip route add b::1/64 via ip6-address a::2 host-eth0 set sr encaps source addr 1::1 sr policy add bsid 1::1:999 next 2::2 next 3::3 sr steer l3 2003::1/64 via sr policy bsid 1::1:999 trace: 02:01:10:720008: af-packet-input af_packet: hw_if_index 3 next-index 4 tpacket2_hdr: status 0x2001 len 98 snaplen 98 mac 66 net 80 sec 0x5a571037 nsec 0x28091fb7 vlan 0 02:01:10:720040: ethernet-input IP6: 00:22:12:66:00:33 -> 00:0c:29:4d:af:b5 02:01:10:720068: ip6-input ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720075: ip6-lookup fib 0 dpo-idx 35 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720085: ip6-load-balance fib 0 dpo-idx 35 flow hash: 0x ICMP6: 2001::5 -> 2003::5 tos 0x00, flow label 0x0, hop limit 64, payload length 44 ICMP echo_request checksum 0xa6e8 02:01:10:720089: sr-pl-rewrite-encaps SR-policy-rewrite: src 1::1 dst 2::2 02:01:10:720096: ip6-lookup fib 0 dpo-idx 9 flow hash: 0x IPV6_ROUTE: 1::1 -> 2::2 tos 0x00, flow label 0x0, hop limit 64, payload length 140 02:01:10:720097: ip6-rewrite tx_sw_if_index 1 adj-idx 9 : ipv6 via a::2 host-eth0: 000c29198e58000c294daf8d86dd flow hash: 0x : 000c29198e58000c294daf8d86dd608c2b3f0001 0020: 0001000200022906040202002003 0040: 000
[vpp-dev] problems in mips32
Guys,
I'm looking forward to run vpp in mips32 arch,but problem was caused by
"clib_calljmp","clib_setjmp" and "clib_longjmp". There is no code for mips32 in
vpp, so I wrote them by myself, and they worked very well in my test program,
However,when I run vpp with them, segmentation fault was happend when excute a
system call like "open","SYS_clock_gettime",etc.
The "stack" in "clib_calljmp" was alloced by "clib_mem_alloc_aligned", It is
strange that if I did not use "clib_mem_alloc_aligned" but with "malloc", the
problem is still there but less happened. Sometimes it occurs, but sometimes
it's ok.
Here is the code I worte for mips32.
uword clib_calljmp (uword (*func) (uword func_arg), uword func_arg, void *stack)
{
unsigned long ret=0;
__asm__ volatile (
".set push \n"
"move $23, $29\n"
"li $9, 4\n\t"
"subu $8, %3, $9\n\t"
"sll $8, $8, 0\n\t"
"move $29, $8\n\t"
"move $9, %1\n\t"
"move $4, %2\n\t"
"move $25,$9\n\t"
"move $22, $31\n\t"
"jalr.hb $25\n\t"
"nop\n\t"
"move %0, $2\n\t"
"move $29,$23\n"
"move $31, $22\n\t"
".set pop\n"
:"=r"(ret)
:"r"(func),"r"(func_arg),"r"(stack)
:"$8","$9","$23","$22"
);
return ret;
}
Thanks,
Xinying Xue
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] problems in mips32
Guys,
I'm looking forward to run vpp in mips32 arch,but problem was caused by
"clib_calljmp","clib_setjmp" and "clib_longjmp". There is no code for mips32 in
vpp, so I wrote them by myself, and they worked very well in my test program,
However,when I run vpp with them, segmentation fault was happend when excute a
system call like "open","SYS_clock_gettime",etc.
The "stack" in "clib_calljmp" was alloced by "clib_mem_alloc_aligned", It is
strange that if I did not use "clib_mem_alloc_aligned" but with "malloc", the
problem is still there but less happened. Sometimes it occurs, but sometimes
it's ok.
Here is the code I worte for mips32.
uword clib_calljmp (uword (*func) (uword func_arg), uword func_arg, void *stack)
{
unsigned long ret=0;
__asm__ volatile (
".set push \n"
"move $23, $29\n"
"li $9, 4\n\t"
"subu $8, %3, $9\n\t"
"sll $8, $8, 0\n\t"
"move $29, $8\n\t"
"move $9, %1\n\t"
"move $4, %2\n\t"
"move $25,$9\n\t"
"move $22, $31\n\t"
"jalr.hb $25\n\t"
"nop\n\t"
"move %0, $2\n\t"
"move $29,$23\n"
"move $31, $22\n\t"
".set pop\n"
:"=r"(ret)
:"r"(func),"r"(func_arg),"r"(stack)
:"$8","$9","$23","$22"
);
return ret;
}
Thanks,
Xinying Xue
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] problems in mips32
According to your suggestion，I re-write "clib_calljmp" in longjmp.S,and it also
passes test_longjmp.c;but it doesn't work in vpp, still segmentation fault when
excute a system call.
At last time, I saving return address(ra) and old stack-pointer(old sp) in
register s6 and s7, this time I saved them in new stack.
I don't think Ra and old stack is the key of the question, becuase the function
crashes before it returns.
Here is the code；
.text
.global clib_calljmp
.align 4;
.ent clib_calljmp,0;
.type clib_calljmp,@function
clib_calljmp:
move $10, $29 //sp->t2 backup old sp
li $9, 4 //t1 = 4
subu $8, $6, $9 //t0 = a2 - t1 new sp -4
move $29, $8 //t0->sp write new sp in register sp
addiu $29,$29,-8
sw $31,4($29) //push ra
sw $10,0($29) //push old stack
move $25, $4 //a0->t9 new function
move $4, $5 //a1->a0 new function arg
jalr $25 //jump
nop
lw $31,4($29) //pop ra
lw $29,0($29) //pop old stack
jr $31 //return
.end clib_calljmp;
Regards,
Xinying Xue
From: Dave Barach (dbarach)
Date: 2017-03-16 21:03
To: 薛欣颖; vpp-dev
Subject: RE: [vpp-dev] problems in mips32
Please make sure that src/vppinfra/test_longjmp.c passes before you move on.
You’ve undoubtedly pickled the stack and/or one or more of the registers.
Clib_calljmp is always the source of subsequent issues.
The code you wrote belongs in longjmp.S. Trying to write clib_calljmp(...) in C
/ doing the dirty work in an asm volatile makes it all but inevitable that GCC
will get in the way.
Even though it’s been a long time since I wrote MIPS assembler code: I don’t
see where you’re saving clib_calljmp’s return address and old stack-pointer on
the new stack.
If you expect people to even try to help you with assembly code, comments are
essential.
Thanks… Dave
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of ???
Sent: Wednesday, March 15, 2017 9:52 PM
To: vpp-dev
Subject: [vpp-dev] problems in mips32
Guys,
I'm looking forward to run vpp in mips32 arch,but problem was caused by
"clib_calljmp","clib_setjmp" and "clib_longjmp". There is no code for mips32 in
vpp, so I wrote them by myself, and they worked very well in my test program,
However,when I run vpp with them, segmentation fault was happend when excute a
system call like "open","SYS_clock_gettime",etc.
The "stack" in "clib_calljmp" was alloced by "clib_mem_alloc_aligned", It is
strange that if I did not use "clib_mem_alloc_aligned" but with "malloc", the
problem is still there but less happened. Sometimes it occurs, but sometimes
it's ok.
Here is the code I worte for mips32.
uword clib_calljmp (uword (*func) (uword func_arg), uword func_arg, void *stack)
{
unsigned long ret=0;
__asm__ volatile (
".set push \n"
"move $23, $29\n"
"li $9, 4\n\t"
"subu $8, %3, $9\n\t"
"sll $8, $8, 0\n\t"
"move $29, $8\n\t"
"move $9, %1\n\t"
"move $4, %2\n\t"
"move $25,$9\n\t"
"move $22, $31\n\t"
"jalr.hb $25\n\t"
"nop\n\t"
"move %0, $2\n\t"
"move $29,$23\n"
"move $31, $22\n\t"
".set pop\n"
:"=r"(ret)
:"r"(func),"r"(func_arg),"r"(stack)
:"$8","$9","$23","$22"
);
return ret;
}
Thanks,
Xinying Xue
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] problems in mips32
I use a physical device, not a vicual one.
Here are the information.
# cat /proc/cpuinfo
system type : Atheros AR934x
processor : 0
cpu model : MIPS 74Kc V4.12
BogoMIPS: 279.55
wait instruction: yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x, 0x0ff8,
0x0ff8, 0x0ff8]
ASEs implemented: mips16 dsp
shadow register sets: 1
core: 0
VCED exceptions : not available
VCEI exceptions : not available
From: Dave Barach (dbarach)
Date: 2017-03-20 19:56
To: 薛欣颖; vpp-dev
Subject: RE: RE: [vpp-dev] problems in mips32
Perhaps someone in the community can help you. I have neither cycles nor
equipment available to work on the problem. Just to ask: what kind of hardware
are you using, or are you using a qemu model?
From: 薛欣颖 [mailto:xy...@fiberhome.com]
Sent: Sunday, March 19, 2017 11:18 PM
To: Dave Barach (dbarach) ; vpp-dev
Subject: Re: RE: [vpp-dev] problems in mips32
According to your suggestion，I re-write "clib_calljmp" in longjmp.S,and it also
passes test_longjmp.c;but it doesn't work in vpp, still segmentation fault when
excute a system call.
At last time, I saving return address(ra) and old stack-pointer(old sp) in
register s6 and s7, this time I saved them in new stack.
I don't think Ra and old stack is the key of the question, becuase the function
crashes before it returns.
Here is the code；
.text
.global clib_calljmp
.align 4;
.ent clib_calljmp,0;
.type clib_calljmp,@function
clib_calljmp:
move $10, $29 //sp->t2 backup
old sp
li $9, 4 //t1 = 4
subu $8, $6, $9 //t0 = a2 - t1 new sp -4
move $29, $8 //t0->sp write
new sp in register sp
addiu $29,$29,-8
sw $31,4($29) //push ra
sw $10,0($29) //push old stack
move $25, $4
//a0->t9 new function
move $4, $5
//a1->a0 new function arg
jalr $25
//jump
nop
lw $31,4($29) //pop ra
lw $29,0($29) //pop old stack
jr $31
//return
.end clib_calljmp;
Regards,
Xinying Xue
From: Dave Barach (dbarach)
Date: 2017-03-16 21:03
To: 薛欣颖; vpp-dev
Subject: RE: [vpp-dev] problems in mips32
Please make sure that src/vppinfra/test_longjmp.c passes before you move on.
You’ve undoubtedly pickled the stack and/or one or more of the registers.
Clib_calljmp is always the source of subsequent issues.
The code you wrote belongs in longjmp.S. Trying to write clib_calljmp(...) in C
/ doing the dirty work in an asm volatile makes it all but inevitable that GCC
will get in the way.
Even though it’s been a long time since I wrote MIPS assembler code: I don’t
see where you’re saving clib_calljmp’s return address and old stack-pointer on
the new stack.
If you expect people to even try to help you with assembly code, comments are
essential.
Thanks… Dave
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of ???
Sent: Wednesday, March 15, 2017 9:52 PM
To: vpp-dev
Subject: [vpp-dev] problems in mips32
Guys,
I'm looking forward to run vpp in mips32 arch,but problem was caused by
"clib_calljmp","clib_setjmp" and "clib_longjmp". There is no code for mips32 in
vpp, so I wrote them by myself, and they worked very well in my test program,
However,when I run vpp with them, segmentation fault was happend when excute a
system call like "open","SYS_clock_gettime",etc.
The "stack" in "clib_calljmp" was alloced by "clib_mem_alloc_aligned", It is
strange that if I did not use "clib_mem_alloc_aligned" but with "malloc", the
problem is still there but less happened. Sometimes it occurs, but sometimes
it's ok.
Here is the code I worte for mips32.
uword clib_calljmp (uword (*func) (uword func_arg), uword func_arg, void *stack)
{
unsigned long ret=0;
__asm__ volatile (
".set push \n"
"move $23, $29\n"
"li $9, 4\n\t"
"subu $8, %3, $9\n\t"
"sll $8, $8, 0\n\t"
"move $29, $8\n\t"
"move $9, %1\n\t"
"move $4, %2\n\t"
"move $25,$9\n\t"
"move $22, $31\n\t"
&quo
[vpp-dev] some problem about sub-interface
Hi guys, I created a host-interface and a sub-interface, when I created bridge on sub-interface, the two sub-interface can not communicate. Another L3 ARP can not be normal learning. Any else seeing this problem? Do vpp support this feature now? If not,are there any plans to develop this feature? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] ACL match tunnel interface
Hi guys， There are some questions about acl in tunnel interface: I can only match the tunnel rather than the desired inner flow; What should I do to match the inner flow? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] 回复: RE: ACL match tunnel interface
Thank you for your reply! Do you mean that I need to skip the outer package when I'm matching the inner data？I tried ‘ current-data-offset’in 'classify table', but it didn't work. Are the parameters I'm studying right ? Thanks, xyxue 发件人： John Lo (loj) 发送时间： 2017-05-02 15:18 收件人： 薛欣颖; vpp-dev@lists.fd.io 主题： RE: [vpp-dev] ACL match tunnel interface If you are using classification CLI’s high level parameters to match l2/l3 etc, it is generating bit mask for tables and match hex values for sessions assuming matching from start of the received packet, thus always matching the outer L2 and L3 headers. These high level CLI parameter will not work if you have a VLAN tag in the received packet, such as on a VLAN sub-interface, that causes the bit mast and hex value to not be at the right offset from the start of the packet. The most flexible (and tedious) way is to use raw bit-mask with skip value on classify table and hex values on classify session to perform matching, as deep as you want into the packet, assuming you know the incoming packet layout whose L2/L3/L4 header fields always matches what you specified. Regards, John From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of ??? Sent: Monday, May 01, 2017 10:04 PM To: vpp-dev@lists.fd.io Subject: [vpp-dev] ACL match tunnel interface Hi guys， There are some questions about acl in tunnel interface: I can only match the tunnel rather than the desired inner flow; What should I do to match the inner flow? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] 回复: 回复: ACL match tunnel interface
A detailed description of my problem： I would like to match src 1.1.1.2 in gre0,but it did not work. Is there anything wrong in my configuration： vpp1： create gre tun src 2.1.1.1 dst 2.1.1.2 set int ip address gre0 100.1.1.1/24 set int state gre0 up ip route add 192.168.1.1/24 via 100.1.1.2 gre0 vpp2： create gre tun src 2.1.1.2 dst 2.1.1.1 set int ip address gre0 100.1.1.2/24 set int state gre0 up ip route add 1.1.1.2/24 via 100.1.1.1 gre0 classify table mask l3 ip4 src current-data-flag 1 current-data-offset 24 classify session acl-hit-next deny table-index 0 match l3 ip4 src 1.1.1.2 set interface input acl intfc gre0 ip4-table 0 I have tried current-data-offset value 4、20、24、38，but it did not hit anyone： DBGvpp# show classify table verbose TableIdx Sessions NextTbl NextNode 0 1-1-1 Heap: 3 objects, 172 of 1k used, 76 free, 0 reclaimed, 1k overhead, 2044k capacity nbuckets 2, skip 1 match 1 flag 1 offset 24 mask [1]: heap offset 192, len 1 0: [192]: next_index 0 advance 0 opaque -1 action 0 metadata 42832 k: 01010102 hits 0, last_heard 0.00 1 active elements 1 free lists Thanks, xyxue 发件人： xy...@fiberhome.com 发送时间： 2017-05-03 19:03 收件人： John Lo (loj); vpp-dev 主题： 回复: RE: [vpp-dev] ACL match tunnel interface Thank you for your reply! Do you mean that I need to skip the outer package when I'm matching the inner data？I tried ‘ current-data-offset’in 'classify table', but it didn't work. Are the parameters I'm studying right ? Thanks, xyxue 发件人： John Lo (loj) 发送时间： 2017-05-02 15:18 收件人： 薛欣颖; vpp-dev@lists.fd.io 主题： RE: [vpp-dev] ACL match tunnel interface If you are using classification CLI’s high level parameters to match l2/l3 etc, it is generating bit mask for tables and match hex values for sessions assuming matching from start of the received packet, thus always matching the outer L2 and L3 headers. These high level CLI parameter will not work if you have a VLAN tag in the received packet, such as on a VLAN sub-interface, that causes the bit mast and hex value to not be at the right offset from the start of the packet. The most flexible (and tedious) way is to use raw bit-mask with skip value on classify table and hex values on classify session to perform matching, as deep as you want into the packet, assuming you know the incoming packet layout whose L2/L3/L4 header fields always matches what you specified. Regards, John From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of ??? Sent: Monday, May 01, 2017 10:04 PM To: vpp-dev@lists.fd.io Subject: [vpp-dev] ACL match tunnel interface Hi guys， There are some questions about acl in tunnel interface: I can only match the tunnel rather than the desired inner flow; What should I do to match the inner flow? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] 回复: RE: ACL match tunnel interface
Hi John, This problem has been solved. Thank you very much! xyxue 发件人： John Lo (loj) 发送时间： 2017-05-04 22:33 收件人： 薛欣颖; vpp-dev 主题： RE: 回复: [vpp-dev] ACL match tunnel interface Hi Xyxue, With current-data-flag set to 1, I believe the classification match will start at the current_data pointer of the packet. After GRE tunnel decap, I believe the current_data pointer should be at the inner IP header. In order to match the source IP address of this inner header, the mask needs to be 0x and the value in the session needs to be 0x01010102 without any skip nor offset. May be you should try to specify these raw hex values without specifying any offset and try how it works? classify table mask hex 0x current-data-flag 1 classify session acl-hit-next deny table-index 0 match hex 0x01010102 As I mentioned in my original reply to you, the high level “match l3 ip-src..” will produce a mask that matches from start of packet assuming the presence of an Ethernet header with no VLAN tag and thus not quite usable. Regards, John From: 薛欣颖 [mailto:xy...@fiberhome.com] Sent: Wednesday, May 03, 2017 10:11 PM To: John Lo (loj) ; vpp-dev Subject: 回复: 回复: [vpp-dev] ACL match tunnel interface A detailed description of my problem： I would like to match src 1.1.1.2 in gre0,but it did not work. Is there anything wrong in my configuration： vpp1： create gre tun src 2.1.1.1 dst 2.1.1.2 set int ip address gre0 100.1.1.1/24 set int state gre0 up ip route add 192.168.1.1/24 via 100.1.1.2 gre0 vpp2： create gre tun src 2.1.1.2 dst 2.1.1.1 set int ip address gre0 100.1.1.2/24 set int state gre0 up ip route add 1.1.1.2/24 via 100.1.1.1 gre0 classify table mask l3 ip4 src current-data-flag 1 current-data-offset 24 classify session acl-hit-next deny table-index 0 match l3 ip4 src 1.1.1.2 set interface input acl intfc gre0 ip4-table 0 I have tried current-data-offset value 4、20、24、38，but it did not hit anyone： DBGvpp# show classify table verbose TableIdx Sessions NextTbl NextNode 0 1-1-1 Heap: 3 objects, 172 of 1k used, 76 free, 0 reclaimed, 1k overhead, 2044k capacity nbuckets 2, skip 1 match 1 flag 1 offset 24 mask [1]: heap offset 192, len 1 0: [192]: next_index 0 advance 0 opaque -1 action 0 metadata 42832 k: 01010102 hits 0, last_heard 0.00 1 active elements 1 free lists Thanks, xyxue 发件人： xy...@fiberhome.com 发送时间： 2017-05-03 19:03 收件人： John Lo (loj); vpp-dev 主题： 回复: RE: [vpp-dev] ACL match tunnel interface Thank you for your reply! Do you mean that I need to skip the outer package when I'm matching the inner data？I tried ‘ current-data-offset’in 'classify table', but it didn't work. Are the parameters I'm studying right ? Thanks, xyxue 发件人： John Lo (loj) 发送时间： 2017-05-02 15:18 收件人： 薛欣颖; vpp-dev@lists.fd.io 主题： RE: [vpp-dev] ACL match tunnel interface If you are using classification CLI’s high level parameters to match l2/l3 etc, it is generating bit mask for tables and match hex values for sessions assuming matching from start of the received packet, thus always matching the outer L2 and L3 headers. These high level CLI parameter will not work if you have a VLAN tag in the received packet, such as on a VLAN sub-interface, that causes the bit mast and hex value to not be at the right offset from the start of the packet. The most flexible (and tedious) way is to use raw bit-mask with skip value on classify table and hex values on classify session to perform matching, as deep as you want into the packet, assuming you know the incoming packet layout whose L2/L3/L4 header fields always matches what you specified. Regards, John From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of ??? Sent: Monday, May 01, 2017 10:04 PM To: vpp-dev@lists.fd.io Subject: [vpp-dev] ACL match tunnel interface Hi guys， There are some questions about acl in tunnel interface: I can only match the tunnel rather than the desired inner flow; What should I do to match the inner flow? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] sharding in tunnel
Hi guys， When the IP message enters the GRE、L2TP、MPLS tunnel， does the VPP support sharding? Thanks， xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] sharding in tunnel
I'm sorry I didn't say it clearly. My questions: Does the VPP support ip fragment in GRE、L2TP、MPLS tunnel? Whether the tunnel supports configuring the MTU？ Whether the receiver supports ip reassembly？ Thanks， xyxue From: otroan Date: 2017-05-08 15:16 To: 薛欣颖 CC: vpp-dev Subject: Re: [vpp-dev] sharding in tunnel > When the IP message enters the GRE、L2TP、MPLS tunnel， does the VPP support > sharding? I'm not quite sure what "sharding" would mean in this context. Are you thinking of point to multipoint tunnels? Or ECMP to a set of anycast tunnel destinations or something completely different? Cheers, Ole ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] sharding in tunnel
A detailed description of my problem： I would like to test ip fragment reassembly,but it didn't work.Is there anything wrong in my configuration： set interface mtu 2000 host-eth2 Did I miss anything configuration? If vpp support ip fragment reassembly on host interface . Does VPP support the IP fragment reassembly on the virtual interface we created, such as the GRE interface? Thanks, xyxue From: xy...@fiberhome.com Date: 2017-05-08 15:42 To: otroan CC: vpp-dev Subject: Re: Re: [vpp-dev] sharding in tunnel I'm sorry I didn't say it clearly. My questions: Does the VPP support ip fragment in GRE、L2TP、MPLS tunnel? Whether the tunnel supports configuring the MTU？ Whether the receiver supports ip reassembly？ Thanks， xyxue From: otroan Date: 2017-05-08 15:16 To: 薛欣颖 CC: vpp-dev Subject: Re: [vpp-dev] sharding in tunnel > When the IP message enters the GRE、L2TP、MPLS tunnel， does the VPP support > sharding? I'm not quite sure what "sharding" would mean in this context. Are you thinking of point to multipoint tunnels? Or ECMP to a set of anycast tunnel destinations or something completely different? Cheers, Ole ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Ip fragment reassembly
Hi guys, Whether vpp support ip fragment reassembly on host-interface? Can I use only" set interface mtu 2000 host-eth2 "to set mtu. Here's my test result: vpp+dpdk: mtu 1500 when the packet size 1500+ it dropped; mtu 2000 when the packet size 2000+ it dropped; mtu 300 when the packet size < 1500 it passed; no fragmentation in my test; vpp without dpdk: Configuring MTU is not effective. Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Ip fragment reassembly
ok .Thank you very much ! xyxue From: Kinsella, Ray Date: 2017-05-15 19:02 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] Ip fragment reassembly Hi Xyxue, Please try https://gerrit.fd.io/r/#/c/6695/ And see if it resolves your issue. Ray K On 10/05/2017 13:35, 薛欣颖 wrote: > Hi guys, > > Whether vpp support ip fragment reassembly on host-interface? > Can I use only" set interface mtu 2000 host-eth2 "to set mtu. > > Here's my test result: > vpp+dpdk: > mtu 1500 when the packet size 1500+ it dropped; > mtu 2000 when the packet size 2000+ it dropped; > mtu 300 when the packet size < 1500 it passed; > no fragmentation in my test; > vpp without dpdk: > Configuring MTU is not effective. > > Thanks, > xyxue > > > ___ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev > ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Failed to ping between two VPP
Hi guys, When I use stable 17.04,there is something wrong when I ping vpp2 from vpp1, I use" dpkg --purge vpp vpp-dbg vpp-dev vpp-dpdk-dev vpp-dpdk-dkms vpp-lib vpp-plugins vpp-python-api "to compile vpp. That is my configuration: vpp1: creat host-interface name eth1 set interface state host-eth1 up set interface ip addr host-eth1 192.168.153.130/24 set interface mac addr host-eth1 00:0c:29:31:29:ae vpp2: creat host-interface name eth1 set interface state host-eth1 up set interface ip addr host-eth1 192.168.153.131/24 set interface mac addr host-eth1 00:0c:29:8f:ad:61 then I " ping 192.168.153.131 "from vpp1,and "ping 192.168.153.130" from VPP2 the packet trace: 01:20:19:315340: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x2001 len 60 snaplen 60 mac 66 net 80 sec 0x59196685 nsec 0x18dd5a37 vlan 0 01:20:19:315391: ethernet-input IP4: 00:0c:29:31:29:b8 -> 00:0c:29:8f:ad:6b 01:20:19:315411: ip4-input ICMP: 192.168.190.134 -> 192.168.190.136 tos 0x00, ttl 64, length 25, checksum 0x5a2b fragment id 0x2259 ICMP echo_reply checksum 0x71ff 01:20:19:315430: ip4-lookup fib 0 dpo-idx 6 flow hash: 0x ICMP: 192.168.190.134 -> 192.168.190.136 tos 0x00, ttl 64, length 25, checksum 0x5a2b fragment id 0x2259 ICMP echo_reply checksum 0x71ff 01:20:19:315453: ip4-local ICMP: 192.168.190.134 -> 192.168.190.136 tos 0x00, ttl 64, length 25, checksum 0x5a2b fragment id 0x2259 ICMP echo_reply checksum 0x71ff 01:20:19:315476: ip4-icmp-input ICMP: 192.168.190.134 -> 192.168.190.136 tos 0x00, ttl 64, length 25, checksum 0x5a2b fragment id 0x2259 ICMP echo_reply checksum 0x71ff 01:20:19:315486: ip4-icmp-echo-reply ICMP echo id 36352 seq 0 (unknown) 01:20:19:315549: error-punt ip4-icmp-input: unknown type the ip fib has something wrong: 192.168.153.130/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:10 buckets:1 uRPF:9 to:[900:34260] via:[188:8648]] [0] [@5]: ipv4 via 192.168.153.130 host-eth1: 000c293129ae000c298fad610800 Is there something I forgot to config ?Did I conifg wrong command? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Failed to ping between two VPP
Hi Ray, The eth1 is real NIC，not a tap device. Here is the information about host-eth1: DBGvpp# show hardware NameIdx Link Hardware host-eth1 1 up host-eth1 Ethernet address 00:0c:29:31:29:ae Linux PACKET socket interface local0 0down local0 local DBGvpp# show int Name Idx State Counter Count host-eth1 1 up rx packets 549 rx bytes 33524 tx packets 529 tx bytes 25386 drops 9 punts 300 ip4 544 ip6 1 local00down drops DBGvpp# show ip arp Time IP4 Flags Ethernet Interface 194.9013 192.168.153.1 DN00:50:56:c0:00:03 host-eth1 68.5358 192.168.153.131 DN00:0c:29:8f:ad:61 host-eth1 Thanks, xyxue From: Kinsella, Ray Date: 2017-05-16 17:28 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] Failed to ping between two VPP Hi xyxue, Not sure that `set interface mac addr` will work with af_packet. Can you provide a little bit more information ... Are eth1 device's real NICs, or are they Tap devices connected to a bridge. In the case of a bridge, I presume its a Linux Kernel bridge? Ray K On 16/05/2017 09:16, 薛欣颖 wrote: > > Hi guys, > > When I use stable 17.04,there is something wrong when I ping vpp2 from vpp1, > I > use" dpkg --purge vpp vpp-dbg vpp-dev vpp-dpdk-dev vpp-dpdk-dkms vpp-lib > vpp-plugins vpp-python-api > "to compile vpp. > That is my configuration: > > vpp1: > creat host-interface name eth1 > set interface state host-eth1 up > set interface ip addr host-eth1 192.168.153.130/24 > set interface mac addr host-eth1 00:0c:29:31:29:ae > vpp2: > creat host-interface name eth1 > set interface state host-eth1 up > set interface ip addr host-eth1 192.168.153.131/24 > set interface mac addr host-eth1 00:0c:29:8f:ad:61 > > then I " ping 192.168.153.131 "from vpp1,and "ping 192.168.153.130" from > VPP2 > > the packet trace: > 01:20:19:315340: af-packet-input > af_packet: hw_if_index 2 next-index 4 > tpacket2_hdr: > status 0x2001 len 60 snaplen 60 mac 66 net 80 > sec 0x59196685 nsec 0x18dd5a37 vlan 0 > 01:20:19:315391: ethernet-input > IP4: 00:0c:29:31:29:b8 -> 00:0c:29:8f:ad:6b > 01:20:19:315411: ip4-input > ICMP: 192.168.190.134 -> 192.168.190.136 > tos 0x00, ttl 64, length 25, checksum 0x5a2b > fragment id 0x2259 > ICMP echo_reply checksum 0x71ff > 01:20:19:315430: ip4-lookup > fib 0 dpo-idx 6 flow hash: 0x > ICMP: 192.168.190.134 -> 192.168.190.136 > tos 0x00, ttl 64, length 25, checksum 0x5a2b > fragment id 0x2259 > ICMP echo_reply checksum 0x71ff > 01:20:19:315453: ip4-local > ICMP: 192.168.190.134 -> 192.168.190.136 > tos 0x00, ttl 64, length 25, checksum 0x5a2b > fragment id 0x2259 > ICMP echo_reply checksum 0x71ff > 01:20:19:315476: ip4-icmp-input > ICMP: 192.168.190.134 -> 192.168.190.136 > tos 0x00, ttl 64, length 25, checksum 0x5a2b > fragment id 0x2259 > ICMP echo_reply checksum 0x71ff > 01:20:19:315486: ip4-icmp-echo-reply > ICMP echo id 36352 seq 0 (unknown) > 01:20:19:315549: error-punt > ip4-icmp-input: unknown type > > the ip fib has something wrong: > 192.168.153.130/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [index:10 buckets:1 uRPF:9 to:[900:34260] > via:[188:8648]] > > [0] [@5]: ipv4 via 192.168.153.130 host-eth1: 000c293129ae000c298fad610800 > > Is there something I forgot to config ?Did I conifg wrong command? > > > > Thanks, > xyxue > > > ___ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev > ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Failed to ping between two VPP
I sorry to copy the eth2's packet,that is the eth1's packet in vpp1: 00:02:32:132870: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 60 snaplen 60 mac 66 net 80 sec 0x591b9b2d nsec 0x70a3271 vlan 0 00:02:32:134189: ethernet-input IP4: 00:0c:29:8f:ad:61 -> 00:0c:29:31:29:ae 00:02:32:134247: ip4-input ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134290: ip4-lookup fib 0 dpo-idx 5 flow hash: 0x ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134349: ip4-local ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134413: ip4-icmp-input ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134433: ip4-icmp-echo-reply ICMP echo id 29952 seq 0 (unknown) 00:02:32:135147: error-punt ip4-icmp-input: unknown type I know the only way to check the mac on interface "show hardware",how could I check the " underlying device"? Fib entry display 17.04 not exactly correct compared to fib entry 17.01 : 17.04: 192.168.153.131/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:10 buckets:1 uRPF:9 to:[600:22840] via:[205:9430]] [0] [@5]: ipv4 via 192.168.153.131 host-eth1: 000c298fad61000c293129ae0800 17.01(not the same device): 192.168.190.138/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:16 buckets:1 uRPF:15 to:[9:756]] [0] [@5]: ipv4 via 192.168.190.138 host-eth8: IP4: 00:0c:29:b7:19:20 -> 00:0c:29:57:8f:fa Will this change affect my test results? Thanks, xyxue From: Damjan Marion Date: 2017-05-16 22:27 To: 薛欣颖 CC: vpp-dev@lists.fd.io; Dave Barach Subject: Re: [vpp-dev] Failed to ping between two VPP On 16 May 2017, at 13:32, Dave Barach (dbarach) wrote: Copying vpp-dev [and Neale Ranns AKA Dr. Fib...] Thanks… Dave From: 薛欣颖 [mailto:xy...@fiberhome.com] Sent: Tuesday, May 16, 2017 2:16 AM To: Dave Barach (dbarach) Subject: Failed to ping between two VPP Hi Dave, When I use stable 17.04,there is something wrong when I ping vpp2 from vpp1,that is my configuration: vpp1: creat host-interface name eth1 set interface state host-eth1 up set interface ip addr host-eth1 192.168.153.130/24 set interface mac addr host-eth1 00:0c:29:31:29:ae vpp2: creat host-interface name eth1 set interface state host-eth1 up set interface ip addr host-eth1 192.168.153.131/24 set interface mac addr host-eth1 00:0c:29:8f:ad:61 then I " ping 192.168.153.131 "from vpp1,and "ping 192.168.153.130" from VPP2 the packet trace: 01:20:19:315340: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x2001 len 60 snaplen 60 mac 66 net 80 sec 0x59196685 nsec 0x18dd5a37 vlan 0 01:20:19:315391: ethernet-input IP4: 00:0c:29:31:29:b8 -> 00:0c:29:8f:ad:6b 01:20:19:315411: ip4-input ICMP: 192.168.190.134 -> 192.168.190.136 tos 0x00, ttl 64, length 25, checksum 0x5a2b fragment id 0x2259 Are you sure that this trace belongs to your pings? Both MAC and IP address is different than one you configured…. ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Failed to ping between two VPP
Hi neale, 'failed' means this : DBGvpp# ping 192.168.153.130 Statistics: 300 sent, 0 received, 100% packet loss what I know is in'run_ping_ip46_address', L598 got the wrong event_type I'm not running with multiple worker threads. My two vpp is in two 14.04 ubuntu,The two host interfaces are in the two VPP. The two interfaces connect directly. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-17 16:27 To: 薛欣颖; Damjan Marion CC: vpp-dev; Dave Barach (dbarach) Subject: Re: [vpp-dev] Failed to ping between two VPP Hi Xyxue, I don’t understand what has ‘failed’ here. The trace shows an echo-reply packet was received, matched against and outstanding request and punted. If you are running with multiple worker threads, you’ll need to include; https://gerrit.fd.io/r/#/c/6736/ the difference in the FIB output from 17.04 to 17.01 is not an error, it’s just that the rewrite string on the adjacency is no longer pretty printed/decoded. Regards, neale From: 薛欣颖 Date: Wednesday, 17 May 2017 at 02:07 To: Damjan Marion Cc: vpp-dev , "Dave Barach (dbarach)" , "Neale Ranns (nranns)" Subject: Re: Re: [vpp-dev] Failed to ping between two VPP I sorry to copy the eth2's packet,that is the eth1's packet in vpp1: 00:02:32:132870: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x2001 len 60 snaplen 60 mac 66 net 80 sec 0x591b9b2d nsec 0x70a3271 vlan 0 00:02:32:134189: ethernet-input IP4: 00:0c:29:8f:ad:61 -> 00:0c:29:31:29:ae 00:02:32:134247: ip4-input ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134290: ip4-lookup fib 0 dpo-idx 5 flow hash: 0x ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134349: ip4-local ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134413: ip4-icmp-input ICMP: 192.168.153.131 -> 192.168.153.130 tos 0x00, ttl 64, length 25, checksum 0x5386 fragment id 0x7307 ICMP echo_reply checksum 0x8aff 00:02:32:134433: ip4-icmp-echo-reply ICMP echo id 29952 seq 0 (unknown) 00:02:32:135147: error-punt ip4-icmp-input: unknown type I know the only way to check the mac on interface "show hardware",how could I check the " underlying device"? Fib entry display 17.04 not exactly correct compared to fib entry 17.01 : 17.04: 192.168.153.131/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:10 buckets:1 uRPF:9 to:[600:22840] via:[205:9430]] [0] [@5]: ipv4 via 192.168.153.131 host-eth1: 000c298fad61000c293129ae0800 17.01(not the same device): 192.168.190.138/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:16 buckets:1 uRPF:15 to:[9:756]] [0] [@5]: ipv4 via 192.168.190.138 host-eth8: IP4: 00:0c:29:b7:19:20 -> 00:0c:29:57:8f:fa Will this change affect my test results? Thanks, xyxue From: Damjan Marion Date: 2017-05-16 22:27 To: 薛欣颖 CC: vpp-dev@lists.fd.io; Dave Barach Subject: Re: [vpp-dev] Failed to ping between two VPP On 16 May 2017, at 13:32, Dave Barach (dbarach) wrote: Copying vpp-dev [and Neale Ranns AKA Dr. Fib...] Thanks… Dave From: 薛欣颖 [mailto:xy...@fiberhome.com] Sent: Tuesday, May 16, 2017 2:16 AM To: Dave Barach (dbarach) Subject: Failed to ping between two VPP Hi Dave, When I use stable 17.04,there is something wrong when I ping vpp2 from vpp1,that is my configuration: vpp1: creat host-interface name eth1 set interface state host-eth1 up set interface ip addr host-eth1 192.168.153.130/24 set interface mac addr host-eth1 00:0c:29:31:29:ae vpp2: creat host-interface name eth1 set interface state host-eth1 up set interface ip addr host-eth1 192.168.153.131/24 set interface mac addr host-eth1 00:0c:29:8f:ad:61 then I " ping 192.168.153.131 "from vpp1,and "ping 192.168.153.130" from VPP2 the packet trace: 01:20:19:315340: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x2001 len 60 snaplen 60 mac 66 net 80 sec 0x59196685 nsec 0x18dd5a37 vlan 0 01:20:19:315391: ethernet-input IP4: 00:0c:29:31:29:b8 -> 00:0c:29:8f:ad:6b 01:20:19:315411: ip4-input ICMP: 192.168.190.134 -> 192.168.190.136 tos 0x00, ttl 64, length 25, checksum 0x5a2b fragment id 0x2259 Are you sure that this trace belongs to your pings? Both MAC and IP address is different than one you configured…. ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Failed to ping between two VPP
Hi Ray, The problem still exists, Is there any problem in reply message? Thanks, xyxue From: Kinsella, Ray Date: 2017-05-18 19:05 To: 薛欣颖; nranns; Damjan Marion CC: vpp-dev Subject: Re: [vpp-dev] Failed to ping between two VPP Hi Xyxue, Please try this patch to see if it helps. https://gerrit.fd.io/r/#/c/6758/1 Ray K On 18/05/2017 09:28, 薛欣颖 wrote: > Hi neale, > > 'failed' means this : > DBGvpp# ping 192.168.153.130 > > Statistics: 300 sent, 0 received, 100% packet loss > > what I know is in'run_ping_ip46_address', L598 got the wrong event_type > > I'm not running with multiple worker threads. > > My two vpp is in two 14.04 > ubuntu,The two host interfaces are in the two VPP. The two interfaces > connect directly. > > Thanks, > xyxue > > > *From:* Neale Ranns (nranns) <mailto:nra...@cisco.com> > *Date:* 2017-05-17 16:27 > *To:* 薛欣颖 <mailto:xy...@fiberhome.com>; Damjan Marion > <mailto:dmarion.li...@gmail.com> > *CC:* vpp-dev <mailto:vpp-dev@lists.fd.io>; Dave Barach (dbarach) > <mailto:dbar...@cisco.com> > *Subject:* Re: [vpp-dev] Failed to ping between two VPP > > > > Hi Xyxue, > > > > I don’t understand what has ‘failed’ here. > > The trace shows an echo-reply packet was received, matched against > and outstanding request and punted. > > > > If you are running with multiple worker threads, you’ll need to include; > > https://gerrit.fd.io/r/#/c/6736/ > > > > the difference in the FIB output from 17.04 to 17.01 is not an > error, it’s just that the rewrite string on the adjacency is no > longer pretty printed/decoded. > > > > Regards, > > neale > > > > *From: *薛欣颖 > *Date: *Wednesday, 17 May 2017 at 02:07 > *To: *Damjan Marion > *Cc: *vpp-dev , "Dave Barach (dbarach)" > , "Neale Ranns (nranns)" > *Subject: *Re: Re: [vpp-dev] Failed to ping between two VPP > > > > > > > > I sorry to copy the eth2's packet,that is the eth1's packet in vpp1: > > 00:02:32:132870: af-packet-input > af_packet: hw_if_index 1 next-index 4 > tpacket2_hdr: > status 0x2001 len 60 snaplen 60 mac 66 net 80 > sec 0x591b9b2d nsec 0x70a3271 vlan 0 > 00:02:32:134189: ethernet-input > IP4: 00:0c:29:8f:ad:61 -> 00:0c:29:31:29:ae > 00:02:32:134247: ip4-input > ICMP: 192.168.153.131 -> 192.168.153.130 > tos 0x00, ttl 64, length 25, checksum 0x5386 > fragment id 0x7307 > ICMP echo_reply checksum 0x8aff > 00:02:32:134290: ip4-lookup > fib 0 dpo-idx 5 flow hash: 0x > ICMP: 192.168.153.131 -> 192.168.153.130 > tos 0x00, ttl 64, length 25, checksum 0x5386 > fragment id 0x7307 > ICMP echo_reply checksum 0x8aff > 00:02:32:134349: ip4-local > ICMP: 192.168.153.131 -> 192.168.153.130 > tos 0x00, ttl 64, length 25, checksum 0x5386 > fragment id 0x7307 > ICMP echo_reply checksum 0x8aff > 00:02:32:134413: ip4-icmp-input > ICMP: 192.168.153.131 -> 192.168.153.130 > tos 0x00, ttl 64, length 25, checksum 0x5386 > fragment id 0x7307 > ICMP echo_reply checksum 0x8aff > 00:02:32:134433: ip4-icmp-echo-reply > ICMP echo id 29952 seq 0 (unknown) > 00:02:32:135147: error-punt > ip4-icmp-input: unknown type > > I know the only way to check the mac on interface "show hardware",how > could I check the " underlying device"? > > Fib entry display 17.04 not exactly correct compared to fib entry > 17.01 : > 17.04: > 192.168.153.131/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [index:10 buckets:1 uRPF:9 to:[600:22840] > via:[205:9430]] > [0] [@5]: ipv4 via 192.168.153.131 host-eth1: > 000c298fad61000c293129ae0800 > > 17.01(not the same device): > 192.168.190.138/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [index:16 buckets:1 uRPF:15 to:[9:756]] > [0] [@5]: ipv4 via 192.168.190.138 host-eth8: IP4: > 00:0c:29:b7:19:20 -> 00:0c:29:57:8f:fa > > Will this change affect my test results? > > > > Thanks, > > xyxue > > > > *From:* Damjan Marion <mailto:dmarion.li...@gmail.com> > >
[vpp-dev] IPSEC IPV6
Hi guys, Is it possible to configure IPSEC IPV6 now? And how can I configure it? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] 回复: RE: IPSEC IPV6
Hi Matus, There is only ip4 address in create_ipsec_tunnel_command_fn and ipsec_add_del_tunnel_args_t if (unformat (line_input, "local-ip %U", unformat_ip4_address, &a.local_ip)) num_m_args++; else if (unformat (line_input, "remote-ip %U", unformat_ip4_address, &a.remote_ip)) num_m_args++; ip4_address_t local_ip, remote_ip; When I add ipv6 addr and input,then I configure ipsec ipv6 ,will IPSec IPv6 work? By the way, does vpp support IPSEC AH? What about IPSEC AH + ESP? Thanks, xyxue 发件人： Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 发送时间： 2017-05-22 12:50 收件人： 薛欣颖; vpp-dev@lists.fd.io 主题： RE: [vpp-dev] IPSEC IPV6 Hi, IPSec has IPv6 support, see examples here https://wiki.fd.io/view/VPP/IPSec_and_IKEv2#IPSec and use IPv6 adresses instead of IPv4. Regards, Matus From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of ??? Sent: Saturday, May 20, 2017 8:05 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] IPSEC IPV6 Hi guys, Is it possible to configure IPSEC IPV6 now? And how can I configure it? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] MPLS LABEL
Hi guys, I can configure mpls out-label with "ip route add 1.1.1.1/24 via 1.1.2.1 GigE0/0/0/0 out-label 123". How can I configure mpls local-label? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS LABEL
Hi guys, How can I configure label pop in Egress node? That's my configure in my vpp , and the label didn't pop : set interface mpls host-eth1 enable set interface mpls host-eth0 enable mpls local-label 33 ip4-lookup-in-table 0 mpls local-label 33 via 2.1.1.2 host-eth0 mpls local-label 33 via 2.1.1.2 host-eth0 out-label 66 ip route add 192.168.1.0/24 via 2.1.1.2 host-eth0 out-label 66 mpls tunnel add via 2.1.1.2 host-eth0 out-label 66 set int state mpls-tunnel0 up ip route add 192.168.1.0/24 via mpls-tunnel0 What's wrong with my configuration ? Did I miss any configuration? Thanks, xyxue From: xy...@fiberhome.com Date: 2017-05-23 11:43 To: vpp-dev Subject: MPLS LABEL Hi guys, I can configure mpls out-label with "ip route add 1.1.1.1/24 via 1.1.2.1 GigE0/0/0/0 out-label 123". How can I configure mpls local-label? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Assert appears when configuring MPLS tunnel
Hi guys, Why the assert appear on version 17.07, is there anything wrong with my configuration? DBGvpp# mpls local-label add eos 33 ip4-lookup-in-table 1 DBGvpp# mpls local-label add non-eos 34 mpls-lookup-in-table 0 DBGvpp# mpls tunnel add via 2.1.1.1 host-eth1 out-label 1023 DBGvpp# set int state mpls-tunnel0 up DBGvpp# ip route add 192.168.1.0/24 via mpls-tunnel0 out-label 1024 0: /home/vpp_1707/vpp/build-data/../src/vnet/dpo/dpo.c:329 (dpo_get_next_node) assertion `NULL != dpo_nodes[parent_type]' fails Aborted / # Connection closed by foreign host. Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS LABEL
Hi neale, Thank you very much for your reply! You mean that I can configure "mpls local-label add eos 33 ip4-lookup-in-table 1"to pop the inner label,and use "mpls local-label add non-eos 34 mpls-lookup-in-table 0" to pop the outer label. Am I right? Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-05-23 15:18 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS LABEL Hi Xyxue, MPLS labels are popped once they have been used in the lookup stage. The path (i.e. the config after the ‘via’ keyword) describes whether a new label should be pushed, so the absence of an out-label keyword there means that the router will be seen to pop the label. These configs then; 1) mpls local-label 33 ip4-lookup-in-table 0 removes label 33 and does an IP lookup in Table-ID 0 2) mpls local-label 33 via 2.1.1.2 host-eth0 remove label 33, does not add another, and forwards to 2.1.1.1 on host-eth0 (this is probably what you want) 3) mpls local-label 33 via 2.1.1.2 host-eth0 out-label 66 removes label 33, then adds 66 and forwards via 2.1.1.2 on host-eth0 If you add all three statements, then that’s ECMP. The hash algorithm for MPLS uses only the packets MPLS label, which is always 33, so it’ll only every take one of these choices. Hth, neale From: on behalf of 薛欣颖 Date: Tuesday, 23 May 2017 at 07:28 To: vpp-dev Subject: Re: [vpp-dev] MPLS LABEL Hi guys, How can I configure label pop in Egress node? That's my configure in my vpp , and the label didn't pop : set interface mpls host-eth1 enable set interface mpls host-eth0 enable mpls local-label 33 ip4-lookup-in-table 0 mpls local-label 33 via 2.1.1.2 host-eth0 mpls local-label 33 via 2.1.1.2 host-eth0 out-label 66 ip route add 192.168.1.0/24 via 2.1.1.2 host-eth0 out-label 66 mpls tunnel add via 2.1.1.2 host-eth0 out-label 66 set int state mpls-tunnel0 up ip route add 192.168.1.0/24 via mpls-tunnel0 What's wrong with my configuration ? Did I miss any configuration? Thanks, xyxue From: xy...@fiberhome.com Date: 2017-05-23 11:43 To: vpp-dev Subject: MPLS LABEL Hi guys, I can configure mpls out-label with "ip route add 1.1.1.1/24 via 1.1.2.1 GigE0/0/0/0 out-label 123". How can I configure mpls local-label? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS LABEL
Hi neale, Got it. Thank you very much! Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-05-23 18:21 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS LABEL Hi Xyxue, Yes, that’s correct. Note the ip4-lookup-in-table-1 implies a VRF lookup. Regards, neale From: 薛欣颖 Date: Tuesday, 23 May 2017 at 10:15 To: "Neale Ranns (nranns)" , vpp-dev Subject: Re: Re: [vpp-dev] MPLS LABEL Hi neale, Thank you very much for your reply! You mean that I can configure "mpls local-label add eos 33 ip4-lookup-in-table 1"to pop the inner label,and use "mpls local-label add non-eos 34 mpls-lookup-in-table 0" to pop the outer label. Am I right? Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-05-23 15:18 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS LABEL Hi Xyxue, MPLS labels are popped once they have been used in the lookup stage. The path (i.e. the config after the ‘via’ keyword) describes whether a new label should be pushed, so the absence of an out-label keyword there means that the router will be seen to pop the label. These configs then; 1) mpls local-label 33 ip4-lookup-in-table 0 removes label 33 and does an IP lookup in Table-ID 0 2) mpls local-label 33 via 2.1.1.2 host-eth0 remove label 33, does not add another, and forwards to 2.1.1.1 on host-eth0 (this is probably what you want) 3) mpls local-label 33 via 2.1.1.2 host-eth0 out-label 66 removes label 33, then adds 66 and forwards via 2.1.1.2 on host-eth0 If you add all three statements, then that’s ECMP. The hash algorithm for MPLS uses only the packets MPLS label, which is always 33, so it’ll only every take one of these choices. Hth, neale From: on behalf of 薛欣颖 Date: Tuesday, 23 May 2017 at 07:28 To: vpp-dev Subject: Re: [vpp-dev] MPLS LABEL Hi guys, How can I configure label pop in Egress node? That's my configure in my vpp , and the label didn't pop : set interface mpls host-eth1 enable set interface mpls host-eth0 enable mpls local-label 33 ip4-lookup-in-table 0 mpls local-label 33 via 2.1.1.2 host-eth0 mpls local-label 33 via 2.1.1.2 host-eth0 out-label 66 ip route add 192.168.1.0/24 via 2.1.1.2 host-eth0 out-label 66 mpls tunnel add via 2.1.1.2 host-eth0 out-label 66 set int state mpls-tunnel0 up ip route add 192.168.1.0/24 via mpls-tunnel0 What's wrong with my configuration ? Did I miss any configuration? Thanks, xyxue From: xy...@fiberhome.com Date: 2017-05-23 11:43 To: vpp-dev Subject: MPLS LABEL Hi guys, I can configure mpls out-label with "ip route add 1.1.1.1/24 via 1.1.2.1 GigE0/0/0/0 out-label 123". How can I configure mpls local-label? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Assert appears when configuring MPLS tunnel
Hi neale, Thank you very much. Thanks, Xyxue From: Neale Ranns (nranns) Date: 2017-05-23 19:13 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] Assert appears when configuring MPLS tunnel Hi Xyxue, https://gerrit.fd.io/r/#/c/6837/ regards, neale From: on behalf of "Neale Ranns (nranns)" Date: Tuesday, 23 May 2017 at 08:42 To: 薛欣颖 , vpp-dev Subject: Re: [vpp-dev] Assert appears when configuring MPLS tunnel Hi Xyxue, Nothing wrong with that config. But there is a bug in VPP. I’ll fix that ASAP. Thanks, neale From: on behalf of 薛欣颖 Date: Tuesday, 23 May 2017 at 07:52 To: vpp-dev Subject: [vpp-dev] Assert appears when configuring MPLS tunnel Hi guys, Why the assert appear on version 17.07, is there anything wrong with my configuration? DBGvpp# mpls local-label add eos 33 ip4-lookup-in-table 1 DBGvpp# mpls local-label add non-eos 34 mpls-lookup-in-table 0 DBGvpp# mpls tunnel add via 2.1.1.1 host-eth1 out-label 1023 DBGvpp# set int state mpls-tunnel0 up DBGvpp# ip route add 192.168.1.0/24 via mpls-tunnel0 out-label 1024 0: /home/vpp_1707/vpp/build-data/../src/vnet/dpo/dpo.c:329 (dpo_get_next_node) assertion `NULL != dpo_nodes[parent_type]' fails Aborted / # Connection closed by foreign host. Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] VPLS VPWS
Hi guys, Does VPP support VPWS 、VPLS? How should it be configured？Does my configuration below implement VPWS? PE1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface ip table host-eth0 0 set int ip address host-eth0 1.1.1.1/24 set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set interface mpls host-eth0 enable mpls tunnel add via 1.1.1.2 host-eth0 out-label 34 set int state mpls-tunnel0 up set interface l2 xconnect mpls-tunnel0 host-eth1 / To implement VPWS ,directly xconnect eth interface to MPLS TUNNEL，is that correct? How to add PW LABEL 33? mpls local-label add eos 1023 ip4-lookup-in-table 1 ###PW Label, how to pop? mpls local-label add non-eos 1024 mpls-lookup-in-table 0 ###LSP Label pop,is that correct? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] MPLS L3VPN PING FAILED
Hi guys, I have the following configuration: mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024 set int state mpls-tunnel0 up ip route add 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Ping from CE to PE ,and the PE drop it. That is the fib : 192.168.3.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 to:[0:0] via:[15:1320]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 The following is the trace info: 00:17:54:791606: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 98 snaplen 98 mac 66 net 80 sec 0x16645 nsec 0x34a33284 vlan 0 00:17:54:791899: ethernet-input IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02 00:17:54:791956: ip4-input ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792005: ip4-lookup fib 1 dpo-idx 1 flow hash: 0x ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792062: ip4-drop ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792110: error-drop ip4-input: ip4 adjacency drop How can I solve the problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Some error in L3VPN
Hi guys, There is a ping failed occured in L3vpn,and the trace had incorrect print information below: DBGvpp# show trace CLIB unknown format `%#' x label 0 eos 1024 17:23:38:439098: lookup-mpls-dst fib-index:0 hdr:[1023:85:0:eos] load-balance:29 17:23:38:439159: ip4-mpls-label-disposition disp:0 17:23:38:439198: lookup-ip4-dst fib-index:1 addr:63.1.94.231 load-balance:9 17:23:38:439325: ip4-drop IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231 version 0, header length 0 tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x) fragment id 0x0002 offset 35320, flags CONGESTION 17:23:38:439391: error-drop ip4-input: ip4 adjacency drop What should I do to solve this? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale, The ping still failed .Here is the specific information： DBGvpp# show trace CLIB unknown format `%#' x label 0 eos 1024 17:23:38:439098: lookup-mpls-dst fib-index:0 hdr:[1023:85:0:eos] load-balance:29 17:23:38:439159: ip4-mpls-label-disposition disp:0 17:23:38:439198: lookup-ip4-dst fib-index:1 addr:63.1.94.231 load-balance:9 17:23:38:439325: ip4-drop IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231 version 0, header length 0 tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x) fragment id 0x0002 offset 35320, flags CONGESTION 17:23:38:439391: error-drop ip4-input: ip4 adjacency drop By the way , I didn't build tunnels. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-24 18:18 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, The lookup was performed in FIB index 1– you must have used ‘set int ip table host-XXX YYY’ - but the route you added is in the default table. If you want the routes in the same table as the interface do; Ip route add table YYY 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Regards, Neale p.s. are you really constructing the L3VPN from a [full] mesh of MPLS tunnels, or is it LDP in the core? From: on behalf of 薛欣颖 Date: Wednesday, 24 May 2017 at 09:09 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] MPLS L3VPN PING FAILED Hi guys, I have the following configuration: mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024 set int state mpls-tunnel0 up ip route add 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Ping from CE to PE ,and the PE drop it. That is the fib : 192.168.3.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 to:[0:0] via:[15:1320]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 The following is the trace info: 00:17:54:791606: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 98 snaplen 98 mac 66 net 80 sec 0x16645 nsec 0x34a33284 vlan 0 00:17:54:791899: ethernet-input IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02 00:17:54:791956: ip4-input ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792005: ip4-lookup fib 1 dpo-idx 1 flow hash: 0x ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792062: ip4-drop ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792110: error-drop ip4-input: ip4 adjacency drop How can I solve the problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale, I forgot to say ,I neither created tunnel nor used LDP.I used the static command configuration. Thanks, xyxue From: 薛欣颖 Date: 2017-05-25 13:36 To: nranns; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Neale, The ping still failed .Here is the specific information： DBGvpp# show trace CLIB unknown format `%#' x label 0 eos 1024 17:23:38:439098: lookup-mpls-dst fib-index:0 hdr:[1023:85:0:eos] load-balance:29 17:23:38:439159: ip4-mpls-label-disposition disp:0 17:23:38:439198: lookup-ip4-dst fib-index:1 addr:63.1.94.231 load-balance:9 17:23:38:439325: ip4-drop IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231 version 0, header length 0 tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x) fragment id 0x0002 offset 35320, flags CONGESTION 17:23:38:439391: error-drop ip4-input: ip4 adjacency drop By the way , I didn't build tunnels. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-24 18:18 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, The lookup was performed in FIB index 1– you must have used ‘set int ip table host-XXX YYY’ - but the route you added is in the default table. If you want the routes in the same table as the interface do; Ip route add table YYY 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Regards, Neale p.s. are you really constructing the L3VPN from a [full] mesh of MPLS tunnels, or is it LDP in the core? From: on behalf of 薛欣颖 Date: Wednesday, 24 May 2017 at 09:09 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] MPLS L3VPN PING FAILED Hi guys, I have the following configuration: mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024 set int state mpls-tunnel0 up ip route add 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Ping from CE to PE ,and the PE drop it. That is the fib : 192.168.3.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 to:[0:0] via:[15:1320]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 The following is the trace info: 00:17:54:791606: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 98 snaplen 98 mac 66 net 80 sec 0x16645 nsec 0x34a33284 vlan 0 00:17:54:791899: ethernet-input IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02 00:17:54:791956: ip4-input ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792005: ip4-lookup fib 1 dpo-idx 1 flow hash: 0x ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792062: ip4-drop ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792110: error-drop ip4-input: ip4 adjacency drop How can I solve the problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show error ： DBGvpp# show error CountNode Reason 114 ethernet-input l3 mac mismatch 3ip4-glean address overflow drops 213ip4-glean ARP requests sent 15ip4-input ip4 length > l2 length 95199ip4-input ip4 adjacency drop 190519 mpls-lookup MPLS input packets decapsulated 381270 mpls-output MPLS output packets encapsulated 190519 mpls-input MPLS input packets decapsulated DBGvpp# VPP2 show error： DBGvpp# show error CountNode Reason 1345 mpls-input MPLS input packets decapsulated 2664 mpls-output MPLS output packets encapsulated 1345 mpls-lookup MPLS input packets decapsulated 685ip4-input ip4 adjacency drop 10ip4-glean ARP requests sent 5 ethernet-input l3 mac mismatch DBGvpp# Bidirectional flow,Messages can already go out of the interface and encapsulate the corresponding two tags,but droped at the other end equipment. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-25 15:00 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, A few things please: 1) A Chris mentions on another thread, please add https://gerrit.fd.io/r/#/c/6865 so we see a better trace 2) Please collect ‘sh mpls fib ’, for both of the labels you are popping 3) Please collect ‘sh ip fib index 1 ’ for the prefix you expect the decapped packet to match. Thanks, neale From: 薛欣颖 Date: Thursday, 25 May 2017 at 06:36 To: "Neale Ranns (nranns)" , vpp-dev Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Neale, The ping still failed .Here is the specific information： DBGvpp# show trace CLIB unknown format `%#' x label 0 eos 1024 17:23:38:439098: lookup-mpls-dst fib-index:0 hdr:[1023:85:0:eos] load-balance:29 17:23:38:439159: ip4-mpls-label-disposition disp:0 17:23:38:439198: lookup-ip4-dst fib-index:1 addr:63.1.94.231 load-balance:9 17:23:38:439325: ip4-drop IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231 version 0, header length 0 tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x) fragment id 0x0002 offset 35320, flags CONGESTION 17:23:38:439391: error-drop ip4-input: ip4 adjacency drop By the way , I didn't build tunnels. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-24 18:18 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, The lookup was performed in FIB index 1– you must have used ‘set int ip table host-XXX YYY’ - but the route you added is in the default table. If you want the routes in the same table as the interface do; Ip route add table YYY 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Regards, Neale p.s. are you really constructing the L3VPN from a [full] mesh of MPLS tunnels, or is it LDP in the core? From: on behalf of 薛欣颖 Date: Wednesday, 24 May 2017 at 09:09 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] MPLS L3VPN PING FAILED Hi guys, I have the following configuration: mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024 set int state mpls-tunnel0 up ip route add 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Ping from CE to PE ,and the PE drop it. That is the fib : 192.168.3.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 to:[0:0] via:[15:1320]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 The following is the trace info: 00:17:54:791606: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 98 snaplen 98 mac 66 net 80 sec 0x16645 nsec 0x34a33284 vlan 0 00:17:54:791899: ethernet-input IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02 00:17:54:791956: ip4-input ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792005: ip4-lookup fib 1 dpo-idx 1 flow hash: 0x ICMP: 192.168
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale， That is the infomation about it: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 VPP1 show trace （RX） Packet 1 00:18:57:701485: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 132 snaplen 132 mac 66 net 80 sec 0x5a7 nsec 0x211a6b95 vlan 0 00:18:57:702142: ethernet-input MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe 00:18:57:702305: mpls-input MPLS: next mpls-lookup[1] label 1024 ttl 255 00:18:57:702436: mpls-lookup MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0 00:18:57:702569: lookup-mpls-dst fib-index:0 hdr:[1023:254:0:eos] load-balance:33 00:18:57:702629: ip4-mpls-label-disposition disp:0 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 00:18:57:702795: ip4-mpls-label-imposition mpls-header:[33:82:0:eos] 00:18:57:702851: mpls-midchain adj-idx 5 : mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[171485:19898930]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@1]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0x 00:18:57:702982: adj-midchain-tx adj-midchain:[5]:mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[171485:19898930]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@1]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 00:18:57:703067: mpls-label-imposition mpls-header:[34:255:0:neos] 00:18:57:703110: mpls-output adj-idx 4 : mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0x : 0020: 00:18:57:703192: host-eth1-output host-eth1 MPLS: 00:03:7f:ff:ff:fe -> 0e:1a:0d:00:50:43 label 34 exp 0, s 0, ttl 255 - VPP2 show trace （tx） DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:21:48:468740: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 124 snaplen 124 mac 66 net 80 sec 0x66a nsec 0x13c20c2d vlan 0 00:21:48:471028: ethernet-input IP4: 00:10:94:00:00:03 -> 00:50:43:00:02:02 00:21:48:471147: ip4-input unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0x8fde fragment id 0xa37b 00:21:48:471269: ip4-lookup fib 1 dpo-idx 3 flow hash: 0x unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0x8fde fragment id 0xa37b 00:21:48:471339: ip4-mpls-label-imposition mpls-header:[1023:254:0:eos] 00:21:48:471386: mpls-midchain adj-idx 5 : mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:34 buckets:1 uRPF:-1 to:[0:0] via:[191878:22337288]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 flow hash: 0x 00:21:48:471415: adj-midchain-tx adj-midchain:[5]:mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:34 buckets:1 uRPF:-1 to:[0:0] via:[191878:22337288]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 00:21:48:471454: mpls-label-imposition mpls-header:[1024:255:0:neos] 00:21:48:471501: mpls-output adj-idx 4 : mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 flow hash: 0x : 0020: 00:21:48:471535: host-eth1-output host-eth1 MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe label 1024 exp 0, s 0, ttl 255 - VPP1 show mpls fib DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35 ip4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.3.20 host-eth0 [@0]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 Extensions: path:35 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:35 buckets:1 uRPF:35 to:[0:0]] [0] [@5]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 DBGvpp# Thanks， xyxue From: Neale Ranns (nranns) Date: 2017-05-25 1
[vpp-dev] 回复: RE: IPSEC IPV6
Hi Matus, In https://wiki.fd.io/view/VPP/IPSec_and_IKEv2#Enable_SPD_on_an_interface I can only find the configuration about IPSEC ESP .What should I do to configure IPSec AH in tunnel or transport mode? Thanks, xyxue 发件人： Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 发送时间： 2017-05-22 14:17 收件人： 薛欣颖; vpp-dev 主题： RE: RE: [vpp-dev] IPSEC IPV6 Hi, Ipsec tunnel interface support only IPv4, IPv6 works only when you create SA and SPD entry and enable IPSec feature on interface (https://wiki.fd.io/view/VPP/IPSec_and_IKEv2#Enable_SPD_on_an_interface). Supported is only AH+ESP in tunnel or transport mode. Regards, Matus From: 薛欣颖 [mailto:xy...@fiberhome.com] Sent: Monday, May 22, 2017 8:09 AM To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) ; vpp-dev Subject: 回复: RE: [vpp-dev] IPSEC IPV6 Hi Matus, There is only ip4 address in create_ipsec_tunnel_command_fn and ipsec_add_del_tunnel_args_t if (unformat (line_input, "local-ip %U", unformat_ip4_address, &a.local_ip)) num_m_args++; else if (unformat (line_input, "remote-ip %U", unformat_ip4_address, &a.remote_ip)) num_m_args++; ip4_address_t local_ip, remote_ip; When I add ipv6 addr and input,then I configure ipsec ipv6 ,will IPSec IPv6 work? By the way, does vpp support IPSEC AH? What about IPSEC AH + ESP? Thanks, xyxue 发件人： Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 发送时间： 2017-05-22 12:50 收件人： 薛欣颖; vpp-dev@lists.fd.io 主题： RE: [vpp-dev] IPSEC IPV6 Hi, IPSec has IPv6 support, see examples here https://wiki.fd.io/view/VPP/IPSec_and_IKEv2#IPSec and use IPv6 adresses instead of IPv4. Regards, Matus From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of ??? Sent: Saturday, May 20, 2017 8:05 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] IPSEC IPV6 Hi guys, Is it possible to configure IPSEC IPV6 now? And how can I configure it? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale, Is this correct in trace: 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 192.168.2.20 is src ip not the dst ip. It seems that lack of pop a label . That is the infomation about it: VPP1: show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.2.0/24 fib:1 index:26 locks:2 src:CLI refs:1 flags:attached,import, index:31 locks:2 flags:shared, uPRF-list:32 len:1 itfs:[3, ] index:31 pl-index:31 ip4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:31 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:30 buckets:1 uRPF:32 to:[264:30096]] [0] [@10]: mpls-label:[3]:[33:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[264:31152]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@2]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35 ip4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.3.20 host-eth0 [@0]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 Extensions: path:35 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:35 buckets:1 uRPF:35 to:[0:0]] [0] [@5]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 DBGvpp# -- vpp2 : show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.20/32 fib:1 index:31 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:36 locks:2 uPRF-list:36 len:1 itfs:[1, ] index:36 pl-index:36 ipv4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.2.20 host-eth0 [@0]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 Extensions: path:36 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[0:0]] [0] [@5]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:34 labels:1023 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:33 buckets:1 uRPF:35 to:[448:49280]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[448:51072]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.3.1/24 table 1 host-eth1 (up): 2.1.1.1/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# - VPP2 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.2.1/24 table 1 host-eth1 (up): 2.1.1.2/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-26 15:22 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, If these are the addresses you are pinging to and from: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 Then let’s see how they are reachable on each device; sh ip fib index 1 192.168.2.20 sh ip fib index 1 192.168.3.20 on both VPP instances. And also: sh int addr on both. Sp we see VPP’s local addresses. Thanks, neale From: 薛欣颖 Date: Friday, 26 May 2017 at 03:26 To: "Neale Ranns (nranns)" , vpp-dev Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Neale， That is the infomation about it: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 VPP1 show trace （RX） Packet 1 00:18:57:701485: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 132 snaplen 132 mac 66 net 80 sec 0x5a7 nsec 0x211a6b95 vlan 0 00:18:57:702142: ethernet-input MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe 00:18:57
Re: [vpp-dev] VPLS VPWS
Hi neale,
Is my configuration below correct?
MPLS L2VPN（VPWS）
PE1
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set int ip address host-eth0 1.1.1.1/24
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set interface mpls host-eth0 enable
mpls tunnel l2-only via 1.1.1.2 host-eth0 out-label 34 out-label 33
set int state mpls-tunnel0 up
set interface l2 xconnect mpls-tunnel0 host-eth1
mpls local-label add eos 1023 l2-input-on mpls-tunnel0
mpls local-label add non-eos 1024 mpls-lookup-in-table 0
PE2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set int ip address host-eth1 1.1.1.2/24
set interface mac address host-eth0 00:50:43:00:02:02
set interface mac address host-eth1 0E:1A:0D:00:50:43
mpls tunnel l2-only via 1.1.1.1 host-eth1 out-label 1024 out-label 1023
set int state mpls-tunnel0 up
set interface l2 xconnect mpls-tunnel0 host-eth1
mpls local-label add eos 33 l2-input-on mpls-tunnel0
mpls local-label add non-eos 34 mpls-lookup-in-table 0
In addtion,how to configure VPLS?
Thanks,
xyxue
From: Neale Ranns (nranns)
Date: 2017-05-25 00:32
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] VPLS VPWS
Hi Xyxue,
VPP does not support VP{WL]S.
However, I’ve made a patch to enable it;
https://gerrit.fd.io/r/#/c/6861/1
please experiment and let me know how you get on.
Changes to your configs below:
- Create the mpls tunnel in L2 mode
mpls tunnel l2-only via 1.1.1.2 host-eth0 out-label 34 [out-label PW_CW]
- Pop the inner label with an instruction to send the payload to an L2
interface
mpls local-label add eos 1023 l2-input-on mpls-tunnelXXX
add the use of the l2 configs remains the same.
Regards,
Neale
From: on behalf of 薛欣颖
Date: Wednesday, 24 May 2017 at 03:24
To: vpp-dev
Subject: [vpp-dev] VPLS VPWS
Hi guys,
Does VPP support VPWS 、VPLS? How should it be configured？Does my configuration
below implement VPWS?
PE1
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth0 0
set int ip address host-eth0 1.1.1.1/24
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set interface mpls host-eth0 enable
mpls tunnel add via 1.1.1.2 host-eth0 out-label 34
set int state mpls-tunnel0 up
set interface l2 xconnect mpls-tunnel0 host-eth1 / To implement VPWS
,directly xconnect eth interface to MPLS TUNNEL，is that correct? How to add PW
LABEL 33?
mpls local-label add eos 1023 ip4-lookup-in-table 1 ###PW Label, how to
pop?
mpls local-label add non-eos 1024 mpls-lookup-in-table 0 ###LSP Label pop,is
that correct?
Thanks,
xyxue
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale, Each of the two VPP is connected to a CE. I'm pinging to and from the CE. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-26 17:07 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, So the addresses you are pinging to and from are not owned by the VPPs. Are you issuing the ping command on a VPP or on the device that owns the address.? /neale From: 薛欣颖 Date: Friday, 26 May 2017 at 08:43 To: "Neale Ranns (nranns)" , vpp-dev Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi neale, Is this correct in trace: 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 192.168.2.20 is src ip not the dst ip. It seems that lack of pop a label . That is the infomation about it: VPP1: show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.2.0/24 fib:1 index:26 locks:2 src:CLI refs:1 flags:attached,import, index:31 locks:2 flags:shared, uPRF-list:32 len:1 itfs:[3, ] index:31 pl-index:31 ip4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:31 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:30 buckets:1 uRPF:32 to:[264:30096]] [0] [@10]: mpls-label:[3]:[33:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[264:31152]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@2]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35 ip4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.3.20 host-eth0 [@0]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 Extensions: path:35 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:35 buckets:1 uRPF:35 to:[0:0]] [0] [@5]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 DBGvpp# -- vpp2 : show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.20/32 fib:1 index:31 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:36 locks:2 uPRF-list:36 len:1 itfs:[1, ] index:36 pl-index:36 ipv4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.2.20 host-eth0 [@0]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 Extensions: path:36 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[0:0]] [0] [@5]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:34 labels:1023 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:33 buckets:1 uRPF:35 to:[448:49280]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[448:51072]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.3.1/24 table 1 host-eth1 (up): 2.1.1.1/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# - VPP2 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.2.1/24 table 1 host-eth1 (up): 2.1.1.2/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-26 15:22 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, If these are the addresses you are pinging to and from: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 Then let’s see how they are reachable on each device; sh ip fib index 1 192.168.2.20 sh ip fib index 1 192.168.3.20 on both VPP instances. And also: sh int addr on both. Sp we see VPP’s local addresses. Thanks,
Re: [vpp-dev] VPLS VPWS
Hi neale, My configuration and result is shown below: VPWS: PE1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 PE2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 -- VPP1:TRACE DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:09:25:129727: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 76 snaplen 76 mac 66 net 80 sec 0xf4f nsec 0x116a48bd vlan 0 00:09:25:130448: ethernet-input IP4: 00:03:7f:ff:ff:ff -> 2c:53:4a:02:19:32 00:09:25:130633: l2-input l2-input: sw_if_index 1 dst 2c:53:4a:02:19:32 src 00:03:7f:ff:ff:ff 00:09:25:130766: l2-output l2-output: sw_if_index 3 dst 2c:53:4a:02:19:32 src 00:03:7f:ff:ff:ff data 08 00 45 00 00 3e 89 7b 40 00 40 06 00:09:25:130898: mpls-tunnel0-output mpls-tunnel0 : 2c534a02193200037fff0800453e897b4000400629c6c0a8031ec0a8 0020: 030a0017c27ca39f95145a447717801806b4f0500101080a000dce770177 0040: 2f3b0d0a4442477670702320 0060: 00:09:25:131028: mpls-tunnel0-tx MPLS: tunnel 0 00:09:25:131076: l2-load-balance L2-load-balance: index 22 00:09:25:131136: ethernet-mpls-label-imposition mpls-header:[33:255:0:eos] 00:09:25:131185: mpls-output adj-idx 2 : mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0x34f3c577 : 0020: 00:09:25:131367: host-eth1-output host-eth1 MPLS: 00:03:7f:ff:ff:fe -> 0e:1a:0d:00:50:43 label 34 exp 0, s 0, ttl 255 VPP2 :TRACE DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:07:39:676480: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x9 len 76 snaplen 76 mac 66 net 80 sec 0x34d7 nsec 0x127c23fe vlan 0 00:07:39:678704: ethernet-input IP4: 00:50:43:00:02:02 -> 2c:53:4a:02:91:db 00:07:39:678768: l2-input l2-input: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 00:07:39:678820: l2-output l2-output: sw_if_index 3 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 data 08 00 45 00 00 3e d3 86 40 00 40 06 00:07:39:678871: mpls-tunnel0-output mpls-tunnel0 : 2c534a0291db0050430002020800453ed38640004006e1bac0a8021ec0a8 0020: 020a0017dfbad30444a91093a7448018007c85a90101080a00142eeb0161 0040: 59bc0d0a4442477670702320 0060: 9081ca313a4b9123cba7542b6a6590af9a3c24b9 00:07:39:678928: mpls-tunnel0-tx MPLS: tunnel 0 00:07:39:678948: l2-load-balance L2-load-balance: index 22 00:07:39:678980: ethernet-mpls-label-imposition mpls-header:[1023:255:0:eos] 00:07:39:679035: mpls-output adj-idx 2 : mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 flow hash: 0xc147b333 : 0020: 00:07:39:679078: host-eth1-output host-eth1 MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe label 1024 exp 0, s 0, ttl 255 It seems that MPLS label didn't pop,cause the message format to be incorrect.capture result is in the annex. Fib info is shown below: vpp1 show mpls fib DBGvpp#show mpls fib
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale, The result :flow is ok. But when have bi-directional flow ,the assertion will appear: That is the assertion: DBGvpp# 0: /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2635 (ip4_rewrite_inline) assertion `ip0->checksum == ip4_header_checksum (ip0)' fails Aborted /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2497 (ip4_rewrite_inline) assertion `ip1->checksum == ip4_header_checksum (ip1)' fails Aborted 192.168.2.20 --192.168.3.20 VPP2VPP1 The trace is shown below: VPP1 Packet 4 01:06:37:616042: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 132 snaplen 132 mac 66 net 80 sec 0xff9 nsec 0x34b682dc vlan 0 01:06:37:616604: ethernet-input MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe 01:06:37:616765: mpls-input MPLS: next mpls-lookup[1] label 1024 ttl 255 01:06:37:616898: mpls-lookup MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0 01:06:37:617032: lookup-mpls-dst fib-index:0 hdr:[1023:254:0:eos] load-balance:33 01:06:37:617097: ip4-mpls-label-disposition disp:0 01:06:37:617139: lookup-ip4-dst fib-index:1 addr:192.168.3.20 load-balance:35 01:06:37:617255: ip4-rewrite tx_sw_if_index 1 dpo-idx 6 : ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 flow hash: 0x : 0010940400037fff080045c0006e8e07fdfda752c0a80214c0a8 0020: 0314 01:06:37:617323: host-eth0-output host-eth0 IP4: 00:03:7f:ff:ff:ff -> 00:10:94:00:00:04 unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 253, length 110, checksum 0xa752 fragment id 0x8e07 VPP2 Packet 3 01:02:34:895149: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x5 len 124 snaplen 124 mac 66 net 80 sec 0x1054 nsec 0x11097ff5 vlan 0 01:02:34:895471: ethernet-input IP4: 00:10:94:00:00:03 -> 00:50:43:00:02:02 01:02:34:895533: ip4-input unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0xa169 fragment id 0x91f0 01:02:34:895586: ip4-lookup fib 1 dpo-idx 3 flow hash: 0x unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0xa169 fragment id 0x91f0 01:02:34:895643: ip4-mpls-label-imposition mpls-header:[1023:254:0:eos] 01:02:34:895695: mpls-midchain adj-idx 7 : mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[37340:4266490]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 flow hash: 0x 01:02:34:895726: adj-midchain-tx adj-midchain:[7]:mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[37340:4266490]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 01:02:34:895767: mpls-label-imposition mpls-header:[1024:255:0:neos] 01:02:34:895814: mpls-output adj-idx 6 : mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 flow hash: 0x : 0020: 01:02:34:895851: host-eth1-output host-eth1 MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe label 1024 exp 0, s 0, ttl 255 Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
ex 22 00:03:05:987162: ethernet-mpls-label-imposition mpls-header:[33:255:0:eos] 00:03:05:987207: mpls-output adj-idx 2 : mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0xb78171c6 : 0020: 00:03:05:987385: host-eth1-output host-eth1 MPLS: 00:03:7f:ff:ff:fe -> 0e:1a:0d:00:50:43 label 34 exp 0, s 0, ttl 255 - VPP2 Packet 6 00:07:14:455621: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 146 snaplen 146 mac 66 net 80 sec 0x24ba nsec 0x7299553 vlan 0 00:07:14:455772: ethernet-input MPLS: 00:03:7f:ff:ff:fe -> 0e:1a:0d:00:50:43 00:07:14:455928: mpls-input MPLS: next mpls-lookup[1] label 34 ttl 255 00:07:14:456060: mpls-lookup MPLS: next [7], lookup fib index 0, LB index 23 hash 0 label 34 eos 0 00:07:14:456177: lookup-mpls-dst fib-index:0 hdr:[33:255:0:eos] load-balance:21 00:07:14:456251: interface-dpo-l2 sw_if_index:3 00:07:14:456289: l2-input l2-input: sw_if_index 3 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 00:07:14:456468: l2-output l2-output: sw_if_index 1 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 data 08 00 45 c0 00 6e 0b 24 00 00 ff fd 00:07:14:456511: host-eth0-output host-eth0 IP4: 00:10:94:00:00:04 -> 00:03:7f:ff:ff:ff unknown 253: 192.168.3.20 -> 192.168.2.20 tos 0xc0, ttl 255, length 110, checksum 0x2836 fragment id 0x0b24 Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-27 17:11 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xxyue, Can you please be more specific about what is working and was is not. Does the ping we were debugging previously now work? What is this ‘bi-directional flow’ you speak of, if it is not the ping. Those asserts could be related to: https://gerrit.fd.io/r/#/c/6883/ I saw them, whilst debugging the original problem. I you sure you patched and recompiled the DEBUG version of VPP on both ‘PE’s’? Thanks, neale From: 薛欣颖 Date: Saturday, 27 May 2017 at 06:33 To: "Neale Ranns (nranns)" , vpp-dev Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi neale, The result :flow is ok. But when have bi-directional flow ,the assertion will appear: That is the assertion: DBGvpp# 0: /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2635 (ip4_rewrite_inline) assertion `ip0->checksum == ip4_header_checksum (ip0)' fails Aborted /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2497 (ip4_rewrite_inline) assertion `ip1->checksum == ip4_header_checksum (ip1)' fails Aborted 192.168.2.20 --192.168.3.20 VPP2VPP1 The trace is shown below: VPP1 Packet 4 01:06:37:616042: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 132 snaplen 132 mac 66 net 80 sec 0xff9 nsec 0x34b682dc vlan 0 01:06:37:616604: ethernet-input MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe 01:06:37:616765: mpls-input MPLS: next mpls-lookup[1] label 1024 ttl 255 01:06:37:616898: mpls-lookup MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0 01:06:37:617032: lookup-mpls-dst fib-index:0 hdr:[1023:254:0:eos] load-balance:33 01:06:37:617097: ip4-mpls-label-disposition disp:0 01:06:37:617139: lookup-ip4-dst fib-index:1 addr:192.168.3.20 load-balance:35 01:06:37:617255: ip4-rewrite tx_sw_if_index 1 dpo-idx 6 : ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 flow hash: 0x : 0010940400037fff080045c0006e8e07fdfda752c0a80214c0a8 0020: 0314 01:06:37:617323: host-eth0-output host-eth0 IP4: 00:03:7f:ff:ff:ff -> 00:10:94:00:00:04 unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 253, length 110, checksum 0xa752 fragment id 0x8e07 VPP2 Packet 3 01:02:34:895149: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x5 len 124 snaplen 124 mac 66 net 80 sec 0x1054 nsec 0x11097ff5 vlan 0 01:02:34:895471: ethernet-input IP4: 00:10:94:00:00:03 -> 00:50:43:00:02:02 01:02:34:895533: ip4-input unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0xa169 fragment id 0x91f0 01:02:34:895586: ip4-lookup fib 1 dpo-idx 3 flow hash: 0x unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255,
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale, Sorry for not replying to your email in time. 192.168.2.20 --192.168.3.20 VPP2VPP1 A brief description of the problem: When vpp without MPLS the ping packet from CE to CE is ok. When vpp configured MPLS the ping packet from CE to CE is failed ,the assertion occured at the meantime.The assertion is shown below： /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2635 (ip4_rewrite_inline) assertion `ip0->checksum == ip4_header_checksum (ip0)' fails Aborted /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2497 (ip4_rewrite_inline) assertion `ip1->checksum == ip4_header_checksum (ip1)' fails Aborted Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-27 18:25 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, One issue at a time please J let’s start with getting L3VPN to work correctly. Please describe what the 3 flows are that we you discussing; - Fade flow - Ip4 flow - Mpls flow Describe, as in what headers they have, addressing etc. The IP chksum will change from CE->CE since the IP TTL decrements. /neale ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] The count information on virtual interface
Hi guys， Whether VPP collect count information on virtual interfaces? I can only see the count information on virtual interfaces associated with VLAN.Some infomation is shown below: vpp# show int Name Idx State Counter Count local00down vxlan_tunnel0 5 up rx packets39 rx bytes 13489 tx packets 43 tx bytes 15277 DBGvpp# Name Idx State Counter Count local00down mpls-tunnel0 3 up Do other virtual interfaces support the count information? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale,
The configuration is shown below:
PE1
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth1 0
set interface ip table host-eth0 1
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set int ip address host-eth0 192.168.3.1/24
set int ip address host-eth1 2.1.1.1/24
set interface mpls host-eth1 enable
set interface mpls host-eth0 enable
mpls tunnel add via 2.1.1.2 host-eth1 out-label 34
set int state mpls-tunnel0 up
ip route add 192.168.2.0/24 table 1 via mpls-tunnel0 out-label 33
mpls local-label add eos 1023 ip4-lookup-in-table 1
mpls local-label add non-eos 1024 mpls-lookup-in-table 0
PE2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth0 1
set interface ip table host-eth1 0
set interface mac address host-eth0 00:50:43:00:02:02
set interface mac address host-eth1 0E:1A:0D:00:50:43
set int ip address host-eth0 192.168.2.1/24
set int ip address host-eth1 2.1.1.2/24
set interface mpls host-eth1 enable
set interface mpls host-eth0 enable
mpls local-label add eos 33 ip4-lookup-in-table 1
mpls local-label add non-eos 34 mpls-lookup-in-table 0
mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024
set int state mpls-tunnel0 up
ip route add 192.168.3.0/24 table 1 via mpls-tunnel0 out-label 1023
Thanks,
xyxue
From: Neale Ranns (nranns)
Date: 2017-05-31 15:02
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
Can you please give me the full configs in each case.
Thanks,
neale
From: 薛欣颖
Date: Wednesday, 31 May 2017 at 06:56
To: "Neale Ranns (nranns)" , vpp-dev
Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale,
Sorry for not replying to your email in time.
192.168.2.20 --192.168.3.20 VPP2VPP1
A brief description of the problem:
When vpp without MPLS the ping packet from CE to CE is ok.
When vpp configured MPLS the ping packet from CE to CE is failed ,the
assertion occured at the meantime.The assertion is shown below：
/home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2635 (ip4_rewrite_inline)
assertion `ip0->checksum == ip4_header_checksum (ip0)' fails
Aborted
/home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2497 (ip4_rewrite_inline)
assertion `ip1->checksum == ip4_header_checksum (ip1)' fails
Aborted
Thanks,
xyxue
From: Neale Ranns (nranns)
Date: 2017-05-27 18:25
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
One issue at a time please J let’s start with getting L3VPN to work correctly.
Please describe what the 3 flows are that we you discussing;
- Fade flow
- Ip4 flow
- Mpls flow
Describe, as in what headers they have, addressing etc.
The IP chksum will change from CE->CE since the IP TTL decrements.
/neale
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] The count information on virtual interface
Hi Neale, I'm sorry. The previous display was caused by my error configuration.The display after change configuration is shown below: DBGvpp# Name Idx State Counter Count local00down mpls-tunnel0 3 up rx packets 21792 tx packets 2484288 Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-31 15:14 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] The count information on virtual interface Hi Xyxue, MPLS tunnels (and all other tunnels/virtual interfaces) should accumulate stats. Are you seeing no stats when the MPLS tunnel is carrying L2 or L3 traffic? Regards, neale From: on behalf of 薛欣颖 Date: Wednesday, 31 May 2017 at 07:28 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] The count information on virtual interface Hi guys， Whether VPP collect count information on virtual interfaces? I can only see the count information on virtual interfaces associated with VLAN.Some infomation is shown below: vpp# show int Name Idx State Counter Count local00down vxlan_tunnel0 5 up rx packets39 rx bytes 13489 tx packets 43 tx bytes 15277 DBGvpp# Name Idx State Counter Count local00down mpls-tunnel0 3 up Do other virtual interfaces support the count information? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale,
The configuration without MPLS:
###VPP1
create host-interface name eth0
create host-interface name eth1
set interface ip table host-eth1 0
set interface ip table host-eth0 1
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set int ip address host-eth0 192.168.3.1/24
set int ip address host-eth1 2.1.1.1/24
ip route add 192.168.2.0/24 via 2.1.1.2
VPP2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface mac address host-eth0 00:50:43:00:02:02
set interface mac address host-eth1 0E:1A:0D:00:50:43
set int ip address host-eth0 192.168.2.1/24
set int ip address host-eth1 2.1.1.2/24
ip route add 192.168.3.0/24 via 2.1.1.1
The configuration with MPLS:
PE1
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth1 0
set interface ip table host-eth0 1
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set int ip address host-eth0 192.168.3.1/24
set int ip address host-eth1 2.1.1.1/24
set interface mpls host-eth1 enable
set interface mpls host-eth0 enable
mpls tunnel add via 2.1.1.2 host-eth1 out-label 34
set int state mpls-tunnel0 up
ip route add 192.168.2.0/24 table 1 via mpls-tunnel0 out-label 33
mpls local-label add eos 1023 ip4-lookup-in-table 1
mpls local-label add non-eos 1024 mpls-lookup-in-table 0
PE2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth0 1
set interface ip table host-eth1 0
set interface mac address host-eth0 00:50:43:00:02:02
set interface mac address host-eth1 0E:1A:0D:00:50:43
set int ip address host-eth0 192.168.2.1/24
set int ip address host-eth1 2.1.1.2/24
set interface mpls host-eth1 enable
set interface mpls host-eth0 enable
mpls local-label add eos 33 ip4-lookup-in-table 1
mpls local-label add non-eos 34 mpls-lookup-in-table 0
mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024
set int state mpls-tunnel0 up
ip route add 192.168.3.0/24 table 1 via mpls-tunnel0 out-label 1023
Thanks,
xyxue
From: Neale Ranns (nranns)
Date: 2017-05-31 15:19
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
You said there are two scenarios; with MPLS (broken), without MPLS (working).
Which scenario is this config for? And can I see the other one too please.
Thanks,
neale
From: 薛欣颖
Date: Wednesday, 31 May 2017 at 08:10
To: "Neale Ranns (nranns)" , vpp-dev
Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale,
The configuration is shown below:
PE1
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth1 0
set interface ip table host-eth0 1
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set int ip address host-eth0 192.168.3.1/24
set int ip address host-eth1 2.1.1.1/24
set interface mpls host-eth1 enable
set interface mpls host-eth0 enable
mpls tunnel add via 2.1.1.2 host-eth1 out-label 34
set int state mpls-tunnel0 up
ip route add 192.168.2.0/24 table 1 via mpls-tunnel0 out-label 33
mpls local-label add eos 1023 ip4-lookup-in-table 1
mpls local-label add non-eos 1024 mpls-lookup-in-table 0
PE2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth0 1
set interface ip table host-eth1 0
set interface mac address host-eth0 00:50:43:00:02:02
set interface mac address host-eth1 0E:1A:0D:00:50:43
set int ip address host-eth0 192.168.2.1/24
set int ip address host-eth1 2.1.1.2/24
set interface mpls host-eth1 enable
set interface mpls host-eth0 enable
mpls local-label add eos 33 ip4-lookup-in-table 1
mpls local-label add non-eos 34 mpls-lookup-in-table 0
mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024
set int state mpls-tunnel0 up
ip route add 192.168.3.0/24 table 1 via mpls-tunnel0 out-label 1023
Thanks,
xyxue
From: Neale Ranns (nranns)
Date: 2017-05-31 15:02
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
Can you please give me the full configs in each case.
Thanks,
neale
From: 薛欣颖
Date: Wednesday, 31 May 2017 at 06:56
To: "Neale Ranns (nranns)" , vpp-dev
Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale,
Sorry for not replying to your email in time.
192.168.2.20 --192.168.3.20 VPP2VPP1
A brie
Re: [vpp-dev] The count information on virtual interface
Hi Neale, The mpls-tunnel0 display only the tx/rx packets info.But the vxlan_tunnel and gre0 display the tx/rx packets and bytes info. Is this an error? DBGvpp# Name Idx State Counter Count local00down mpls-tunnel0 3 up rx packets 21792 tx packets 2484288 vpp# show int Name Idx State Counter Count local00down vxlan_tunnel0 5 up rx packets39 rx bytes 13489 tx packets 43 tx bytes 15277 DBGvpp# show int Name Idx State Counter Count gre0 3 up rx packets 6111 rx bytes 696654 tx packets 6121 tx bytes 820841 ip4 6111 Thanks, xyxue From: xyxue Date: 2017-05-31 15:29 To: nranns; vpp-dev Subject: Re: Re: [vpp-dev] The count information on virtual interface Hi Neale, I'm sorry. The previous display was caused by my error configuration.The display after change configuration is shown below: DBGvpp# Name Idx State Counter Count local00down mpls-tunnel0 3 up rx packets 21792 tx packets 2484288 Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-31 15:14 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] The count information on virtual interface Hi Xyxue, MPLS tunnels (and all other tunnels/virtual interfaces) should accumulate stats. Are you seeing no stats when the MPLS tunnel is carrying L2 or L3 traffic? Regards, neale From: on behalf of 薛欣颖 Date: Wednesday, 31 May 2017 at 07:28 To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] The count information on virtual interface Hi guys， Whether VPP collect count information on virtual interfaces? I can only see the count information on virtual interfaces associated with VLAN.Some infomation is shown below: vpp# show int Name Idx State Counter Count local00down vxlan_tunnel0 5 up rx packets39 rx bytes 13489 tx packets 43 tx bytes 15277 DBGvpp# Name Idx State Counter Count local00down mpls-tunnel0 3 up Do other virtual interfaces support the count information? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] VPLS VPWS problem
Hi Neale, We tested VPLS and VPWS ,the result :In VPLS the flow was dropped in L2. In VPWS unable to send and receive messages continuously.Sometimes there is no flow receive/send. MPLS L2VPN VPLS The configuration and trace is shown below: PE1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 PE2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 Is the configuration correctly? DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:04:36:289191: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x9 len 76 snaplen 76 mac 66 net 80 sec 0x2736 nsec 0xb5544e1 vlan 0 00:04:36:291446: ethernet-input IP4: 00:50:43:00:02:02 -> 2c:53:4a:02:91:db 00:04:36:291525: l2-input l2-input: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 00:04:36:291582: l2-learn l2-learn: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291643: l2-fwd l2-fwd: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291673: error-drop l2-fwd: Reflection Drop VPWS The configuration and trace is shown below: VPP1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 VPP2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 show trace VPP1 Packet 3 00:03:05:985952: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 124 snaplen 124 mac 66 net 80 sec 0x5b1f nsec 0x35349da1 vlan 0 00:03:05:986527: ethernet-input IP4: 00:10:94:00:00:04 -> 00:03:7f:ff:ff:ff 00:03:05:986683: l2-input l2-input: sw_if_index 1 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 00:03:05:986805: l2-output l2-output: sw_if_index 3 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 data 08 00 45 c0 00 6e 01 10 00 00 ff fd 00:03:05:986932: mpls-tunnel0-output mpls-tunnel0 : 00037fff00109404080045c0006e0110fffd324ac0a80314c0a8 0020: 0214 0040: 0060: c12dada7ee982510513b19e40f04dc7d952391bc 00:03:05:987057: mpls-tunnel0-tx MPLS: tunnel 0 00:03:05:987105: l2-load-balance L2-load-balance: index 22 00:03:05:987162: ethernet-mpls-label-imposition mpls-header:[33:255:0:eos] 00:03:05:987207: mpls-output adj-idx 2 : mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0xb78171c6 : 00
