for convenience, ping 192.168.123.2 -s 2000.
the 2 fragment is the following:
(could not see 1500-length frag at 192.168.123.2 by wireshark, only the 
598-length)

Packet 2

00:05:34:358149: dpdk-input
  TenGigabitEthernet6/0/0 rx queue 0
  buffer 0x1268e: current data 14, length 1500, free-list 0, clone-count 0, 
totlen-nifb 0, trace 0x1
                  ext-hdr-valid 
                  l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 
  PKT MBUF: port 0, nb_segs 1, pkt_len 1514
    buf_len 2176, data_len 1514, ol_flags 0x180, data_off 128, phys_addr 
0x1009a400
    packet_type 0x11 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
    rss 0x0 fdir.hi 0x0 fdir.lo 0x0
    Packet Offload Flags
      PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid
      PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid
    Packet Types
      RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
      RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers
  IP4: 00:25:7c:30:05:f0 -> 00:a0:c9:00:00:00
  UDP: 172.16.0.4 -> 172.16.0.3
    tos 0x00, ttl 64, length 1500, checksum 0xf86a
    fragment id 0x047f, flags MORE_FRAGMENTS
  UDP: 4789 -> 4789
    length 1530, checksum 0x0000
00:05:34:358153: ip4-input-no-checksum
  UDP: 172.16.0.4 -> 172.16.0.3
    tos 0x00, ttl 64, length 1500, checksum 0xf86a
    fragment id 0x047f, flags MORE_FRAGMENTS
  UDP: 4789 -> 4789
    length 1530, checksum 0x0000
00:05:34:358155: nat44-out2in
  NAT44_OUT2IN: sw_if_index 1, next index 3, session index -1
00:05:34:358156: nat44-out2in-reass
  NAT44_REASS: sw_if_index 1, next index 1, status translated
00:05:34:358159: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  UDP: 172.16.0.4 -> 172.16.0.3
    tos 0x00, ttl 64, length 1500, checksum 0xf86a
    fragment id 0x047f, flags MORE_FRAGMENTS
  UDP: 4789 -> 4789
    length 1530, checksum 0x0000
00:05:34:358162: ip4-local
    UDP: 172.16.0.4 -> 172.16.0.3
      tos 0x00, ttl 64, length 1500, checksum 0xf86a
      fragment id 0x047f, flags MORE_FRAGMENTS
    UDP: 4789 -> 4789
      length 1530, checksum 0x0000
00:05:34:358163: ip4-reassembly
  reass id: 33, op id: 0 first bi: 75406, data len: 1480, ip/fragment[0, 1479]
                         new range: [0, 1479], off 0, len 1480, bi 75406


Packet 4

00:05:34:358188: dpdk-input
  TenGigabitEthernet6/0/0 rx queue 0
  buffer 0x126dc: current data 14, length 598, free-list 0, clone-count 0, 
totlen-nifb 0, trace 0x3
                  ext-hdr-valid 
                  l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 
  PKT MBUF: port 0, nb_segs 1, pkt_len 612
    buf_len 2176, data_len 612, ol_flags 0x180, data_off 128, phys_addr 
0x1009b780
    packet_type 0x211 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
    rss 0x0 fdir.hi 0x0 fdir.lo 0x0
    Packet Offload Flags
      PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid
      PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid
    Packet Types
      RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet
      RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers
      RTE_PTYPE_L4_UDP (0x0200) UDP packet
  IP4: 00:25:7c:30:05:f0 -> 00:a0:c9:00:00:00
  UDP: 172.16.0.4 -> 172.16.0.3
    tos 0x00, ttl 64, length 598, checksum 0x1bf0
    fragment id 0x0480
  UDP: 4789 -> 4789
    length 578, checksum 0x0000
00:05:34:358189: ip4-input-no-checksum
  UDP: 172.16.0.4 -> 172.16.0.3
    tos 0x00, ttl 64, length 598, checksum 0x1bf0
    fragment id 0x0480
  UDP: 4789 -> 4789
    length 578, checksum 0x0000
00:05:34:358189: nat44-out2in
  NAT44_OUT2IN: sw_if_index 1, next index 1, session index -1
00:05:34:358190: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  UDP: 172.16.0.4 -> 172.16.0.3
    tos 0x00, ttl 64, length 598, checksum 0x1bf0
    fragment id 0x0480
  UDP: 4789 -> 4789
    length 578, checksum 0x0000
00:05:34:358190: ip4-local
    UDP: 172.16.0.4 -> 172.16.0.3
      tos 0x00, ttl 64, length 598, checksum 0x1bf0
      fragment id 0x0480
    UDP: 4789 -> 4789
      length 578, checksum 0x0000
00:05:34:358191: ip4-udp-lookup
  UDP: src-port 4789 dst-port 4789
00:05:34:358192: vxlan4-input
  VXLAN decap from vxlan_tunnel0 vni 100 next 1 error 0
00:05:34:358196: l2-input
  l2-input: sw_if_index 5 dst 4e:20:08:3e:15:e9 src 00:25:7c:30:05:ef
00:05:34:358201: l2-learn
  l2-learn: sw_if_index 5 dst 4e:20:08:3e:15:e9 src 00:25:7c:30:05:ef bd_index 1
00:05:34:358206: l2-fwd
  l2-fwd:   sw_if_index 5 dst 4e:20:08:3e:15:e9 src 00:25:7c:30:05:ef bd_index 1
00:05:34:358207: l2-output
  l2-output: sw_if_index 4 dst 4e:20:08:3e:15:e9 src 00:25:7c:30:05:ef data 08 
00 45 00 02 24 2e 48 00 b9 40 01
00:05:34:358208: tapcli-0-output
  tapcli-0
  IP4: 00:25:7c:30:05:ef -> 4e:20:08:3e:15:e9
  ICMP: 192.168.123.3 -> 192.168.123.2
    tos 0x00, ttl 64, length 548, checksum 0xd281
    fragment id 0x2e48 offset 1480, flags 
  ICMP unknown 0xc0 checksum 0xc2c3




王传国

山东华辰泰尔信息科技股份有限公司 研发中心
电    话:0531-62325309 88877658-8019
手    机:18615184689
传    真:0531-88870859
网    址:http://www.huachentel.com
地    址:山东省济南市高新区舜华路2000号舜泰广场8号楼西区17层
邮    编:250101
 
发件人: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco)
发送时间: 2018-11-16 16:59
收件人: 王传国; vpp-dev
主题: RE: [vpp-dev] NAT44 && VXLAN tunnel && ip reassembly && ip frag can not 
work correctly at vpp stable/1810
Hi,
 
Could you please provide packet trace?
 
Matus
 
 
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of ???
Sent: Friday, November 16, 2018 9:54 AM
To: vpp-dev <vpp-dev@lists.fd.io>
Subject: [vpp-dev] NAT44 && VXLAN tunnel && ip reassembly && ip frag can not 
work correctly at vpp stable/1810
 
Hi all,
    ping 192.168.123.2 -s 6000      from 192.168.123.3 that out of remote 
vxlan-tunnel-endpoint     failed when the NAT44 config was added!
And not NAT44 -> correct;           add NAT44 -> faild!


Who can help? Maybe, this is a bug.
#########################################
set int state TenGigabitEthernet6/0/0 up
set int ip addr TenGigabitEthernet6/0/0 172.16.0.3/24

create bridge-domain 11 learn 1 forward 1 uu-flood 1 flood 1 arp-term 1
loopback create
set int l2 bridge loop0 11 bvi
set int ip address loop0 192.168.123.1/24
set int state loop0 up

tap connect lstack address 192.168.123.2/24
set int l2 bridge tapcli-0 11
set int state tapcli-0 up

nat44 add interface address TenGigabitEthernet6/0/0
set interface nat44 in loop0 out TenGigabitEthernet6/0/0
nat44 add static mapping local 192.168.123.2 22 external 
TenGigabitEthernet6/0/0 22 tcp
nat44 forwarding enable




王传国

山东华辰泰尔信息科技股份有限公司 研发中心
电    话:0531-62325309 88877658-8019
手    机:18615184689
传    真:0531-88870859
网    址:http://www.huachentel.com
地    址:山东省济南市高新区舜华路2000号舜泰广场8号楼西区17层
邮    编:250101
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11300): https://lists.fd.io/g/vpp-dev/message/11300
Mute This Topic: https://lists.fd.io/mt/28239004/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
  • [... 王传国
    • ... Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) via Lists.Fd.Io
      • ... 王传国
        • ... Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) via Lists.Fd.Io
          • ... 王传国
            • ... Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) via Lists.Fd.Io
              • ... 王传国
                • ... Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) via Lists.Fd.Io
                • ... 王传国

Reply via email to