Hi Brindiya,

Could you please show me the output of:
  sh ip fib 6.6.6.1/32

Thanks,
neale

From: <vpp-dev-boun...@lists.fd.io> on behalf of bindiya Kurle 
<bindiyaku...@gmail.com>
Date: Monday, 29 January 2018 at 10:04
To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Subject: [vpp-dev] Arp doesn't work after classifier configuration

Hi,
my vpp version :
DBGvpp# show version
vpp v18.04-rc0~81-g18e955e .

I am observing whenever I do classifier configuration , arp resolution does not 
work

my configuration:

 set interface state GigabitEthernet1/0/1 up
set interface ip address GigabitEthernet1/0/1 6.6.6.1/24<http://6.6.6.1/24>

classify table mask l3 ip4 src dst l4 udp src_port dst_port match 3
set ip classify intfc GigabitEthernet1/0/1 table-index 0


packet trace:
No packets in trace buffer
------------------- Start of thread 2 vpp_wk_1 -------------------
Packet 1
00:52:47:398359: dpdk-input
  GigabitEthernet1/0/1 rx queue 0
  buffer 0x2241e: current data 0, length 60, free-list 0, clone-count 0, 
totlen-nifb 0, trace 0x0
                  l4-cksum-computed l4-cksum-correct l2-hdr-offset 0
  PKT MBUF: port 1, nb_segs 1, pkt_len 60
    buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 
0xee090800
    packet_type 0x0 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
    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
  ARP: 54:ab:3a:79:85:41 -> ff:ff:ff:ff:ff:ff
  request, type ethernet/IP4, address size 6/4
  54:ab:3a:79:85:41/6.6.6.10<http://6.6.6.10> -> 
ff:ff:ff:ff:ff:ff/6.6.6.1<http://6.6.6.1>
00:52:47:398426: ethernet-input
  ARP: 54:ab:3a:79:85:41 -> ff:ff:ff:ff:ff:ff
00:52:47:398458: arp-input
  request, type ethernet/IP4, address size 6/4
  54:ab:3a:79:85:41/6.6.6.10<http://6.6.6.10> -> 
ff:ff:ff:ff:ff:ff/6.6.6.1<http://6.6.6.1>
00:52:47:398497: error-drop
  arp-input: IP4 destination address not local to subnet

I saw similar issue raised in past vpp-455 but it was fixed long back all 
changes are there in the current code .

still I am seeing the issue .
Can anybody help me out with this issue?

Regards,
Bindiya




_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to