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 0x20000001 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: 0x00000000
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: 0x00000000
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: 0x00000000
00000000: 0000000000000000000000000000000000000000000000000000000000000000
00000020: 00000000000000000000000000000000000000000000000000000000
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 0x20000001 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: 0x00000000
00000000: 3a4c48ed59c302fe1ae1c54c080045000054e9fd00003e010c33c0a80314c0a8
00000020: 02140000243e07d20010b3952e5900000000311e0200000000001011
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: 薛欣颖 <xy...@fiberhome.com>
Date: Wednesday, 31 May 2017 at 08:40
To: "Neale Ranns (nranns)" <nra...@cisco.com>, vpp-dev <vpp-dev@lists.fd.io>
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-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: 薛欣颖 <xy...@fiberhome.com>
Date: Wednesday, 31 May 2017 at 08:10
To: "Neale Ranns (nranns)" <nra...@cisco.com>, vpp-dev <vpp-dev@lists.fd.io>
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: 薛欣颖 <xy...@fiberhome.com>
Date: Wednesday, 31 May 2017 at 06:56
To: "Neale Ranns (nranns)" <nra...@cisco.com>, vpp-dev <vpp-dev@lists.fd.io>
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 VPP2----VPP1
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
