are you aware that vpp doesn’t do LDP? VPP is dataplame, and expect that external control plane is present and takes care for programming mpls fib.
— Damjan > On 17 Jun 2018, at 15:11, Gulakh <[email protected]> wrote: > > Hi, > I am having a problem when LDP attempts to setup a session. > According to Wikipedia's LDP page, LDP first exchanges packets on UDP and > then start a session by setting up TCP connection. > > UDP packets from control plane to data plane are sent, but the TCP connection > is not set up. > > Here is what show trace shows: > ================== > UDP > ================== > Packet 8 > > 00:10:18:346891: dpdk-input > GigabitEthernet13/0/0 rx queue 0 > buffer 0x6468: current data 14, length 70, free-list 0, clone-count 0, > totlen-nifb 0, trace 0x7 > ext-hdr-valid > l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 > l3-hdr-offset 14 > PKT MBUF: port 0, nb_segs 1, pkt_len 84 > buf_len 2176, data_len 84, ol_flags 0x0, data_off 128, phys_addr > 0x3fd91a80 > packet_type 0x10 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 > Packet Types > RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers > IP4: 00:0c:29:3a:39:d7 -> 01:00:5e:00:00:02 > UDP: 192.168.1.1 -> 224.0.0.2 > tos 0xc0, ttl 1, length 70, checksum 0xc20e > fragment id 0x152d, flags DONT_FRAGMENT > UDP: 646 -> 646 > length 50, checksum 0x245a > 00:10:18:346913: ip4-input > UDP: 192.168.1.1 -> 224.0.0.2 > tos 0xc0, ttl 1, length 70, checksum 0xc20e > fragment id 0x152d, flags DONT_FRAGMENT > UDP: 646 -> 646 > length 50, checksum 0x245a > 00:10:18:346925: ip4-mfib-forward-lookup > fib 0 entry 6 > 00:10:18:346931: ip4-mfib-forward-rpf > entry 6 itf -1 flags > > > > > ==================== > TCP > ==================== > > Packet 12 > > 00:10:21:474191: dpdk-input > GigabitEthernet13/0/0 rx queue 0 > buffer 0x6441: current data 14, length 60, free-list 0, clone-count 0, > totlen-nifb 0, trace 0xb > ext-hdr-valid > l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 > l3-hdr-offset 14 > PKT MBUF: port 0, nb_segs 1, pkt_len 74 > buf_len 2176, data_len 74, ol_flags 0x0, data_off 128, phys_addr > 0x3fd910c0 > packet_type 0x10 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 > Packet Types > RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers > IP4: 00:0c:29:3a:39:d7 -> 00:0c:29:d6:93:93 > TCP: 1.1.1.1 -> 2.2.2.2 > tos 0xc0, ttl 255, length 60, checksum 0x74f6 > fragment id 0x0000, flags DONT_FRAGMENT > TCP: 646 -> 57413 > seq. 0xbb729c35 ack 0x6382b56c > flags 0x12 SYN ACK, tcp header: 40 bytes > window 28960, checksum 0x5590 > 00:10:21:474204: ip4-input > TCP: 1.1.1.1 -> 2.2.2.2 > tos 0xc0, ttl 255, length 60, checksum 0x74f6 > fragment id 0x0000, flags DONT_FRAGMENT > TCP: 646 -> 57413 > seq. 0xbb729c35 ack 0x6382b56c > flags 0x12 SYN ACK, tcp header: 40 bytes > window 28960, checksum 0x5590 > 00:10:21:474216: ip4-lookup > fib 0 dpo-idx 0 flow hash: 0x00000000 > TCP: 1.1.1.1 -> 2.2.2.2 > tos 0xc0, ttl 255, length 60, checksum 0x74f6 > fragment id 0x0000, flags DONT_FRAGMENT > TCP: 646 -> 57413 > seq. 0xbb729c35 ack 0x6382b56c > flags 0x12 SYN ACK, tcp header: 40 bytes > window 28960, checksum 0x5590 > 00:10:21:474231: ip4-drop > TCP: 1.1.1.1 -> 2.2.2.2 > tos 0xc0, ttl 255, length 60, checksum 0x74f6 > fragment id 0x0000, flags DONT_FRAGMENT > TCP: 646 -> 57413 > seq. 0xbb729c35 ack 0x6382b56c > flags 0x12 SYN ACK, tcp header: 40 bytes > window 28960, checksum 0x5590 > 00:10:21:474233: error-drop > ip4-input: valid ip4 packets > > > what is the problem?? > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9634): https://lists.fd.io/g/vpp-dev/message/9634 Mute This Topic: https://lists.fd.io/mt/22394233/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
