Hi Guy,
Your cofing looks fine. But since you’ve programmed an (S,G) can I please see:
sh ip mfib 10.10.10.34 232.0.0.1
since this is ‘for-us’ traffic you still have to abide by the ‘need a route
back to the sender’ rule. So please;
sh ip fib 10.10.10.34
also;
sh error
is helpful in the game of who-dropped-my-packet.
Thanks,
neale
From: "Guy Doucet -X (gudoucet - FLEXTRONICS CANADA DESIGN SERVICES INC at
Cisco)" <gudou...@cisco.com>
Date: Tuesday, 13 June 2017 at 20:55
To: "Neale Ranns (nranns)" <nra...@cisco.com>, vpp-dev <vpp-dev@lists.fd.io>
Subject: RE: [vpp-dev] problem getting udp_register_dst_port interface to work.
I configured mroute as follows:
vppctl ip mroute 10.10.10.34 232.0.0.1 via TenGigabitEthernet81/0/0 Accept
vppctl ip mroute 10.10.10.34 232.0.0.1 via local Forward
Is this correct?
I get the following output for vppclt sh ip mfib 232.0.0.1
ipv4-VRF:0, fib_index 0
(*, 0.0.0.0/0): flags:D,
fib:0 index:0 locks:1
src:Default Route: flags:D,
Extensions:
Interface-Forwarding:
Interfaces:
RPF-ID:0
multicast-ip4-chain
[@0]: dpo-drop ip4
The full trace back is as follows:
01:22:29:244227: dpdk-input
TenGigabitEthernet81/0/0 rx queue 0
buffer 0xdc70d0: current data 14, length 1428, free-list 0, clone-count 0,
totlen-nifb 0, trace 0x9
PKT MBUF: port 0, nb_segs 1, pkt_len 1442
buf_len 2176, data_len 1442, ol_flags 0x88, data_off 128, phys_addr
0x89bd940
packet_type 0x0
Packet Offload Flags
PKT_RX_L4_CKSUM_BAD (0x0008) L4 cksum of RX pkt. is not OK
PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid
IP4: 00:02:c5:1b:51:08 -> 01:00:5e:00:00:01
UDP: 10.10.10.34 -> 232.0.0.1
tos 0x00, ttl 0, length 1428, checksum 0x792c
fragment id 0x0000, flags DONT_FRAGMENT
UDP: 1234 -> 5001
length 1408, checksum 0x0000
01:22:29:244229: ip4-input-no-checksum
UDP: 10.10.10.34 -> 232.0.0.1
tos 0x00, ttl 0, length 1428, checksum 0x792c
fragment id 0x0000, flags DONT_FRAGMENT
UDP: 1234 -> 5001
length 1408, checksum 0x0000
01:22:29:244231: ip4-mfib-forward-lookup
fib 0 entry 6
01:22:29:244231: ip4-mfib-forward-rpf
entry 6 1 Accept,
Thanks,
Guy
From: Neale Ranns (nranns)
Sent: Tuesday, June 13, 2017 12:20 PM
To: Guy Doucet -X (gudoucet - FLEXTRONICS CANADA DESIGN SERVICES INC at Cisco);
vpp-dev
Subject: Re: [vpp-dev] problem getting udp_register_dst_port interface to work.
Hi Guy,
If that’s the full packet trace, then it looks like the packet was dropped by
an input feature. Use:
sh int feat <INPUT_INTERFACE>
To see what’s configured. Do you have an IP address configured on the input
interface? You’ll need one.
If it’s not that, do you have a route for 232.0.0.1 in the multicast FIB? If so
what is it:
sh ip mfib 232.0.0.1
Regards,
Neale
From: <vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>> on
behalf of "Guy Doucet -X (gudoucet - FLEXTRONICS CANADA DESIGN SERVICES INC at
Cisco)" <gudou...@cisco.com<mailto:gudou...@cisco.com>>
Date: Tuesday, 13 June 2017 at 16:56
To: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] problem getting udp_register_dst_port interface to work.
I am trying to process the following packets using the udp_register_dst_port
interface:
UDP: 10.10.10.34 -> 232.0.0.1
tos 0x00, ttl 0, length 1428, checksum 0x792c
fragment id 0x0000, flags DONT_FRAGMENT
UDP: 1234 -> 5001
length 1408, checksum 0x0000
01:22:29:244229: ip4-input-no-checksum
UDP: 10.10.10.34 -> 232.0.0.1
tos 0x00, ttl 0, length 1428, checksum 0x792c
fragment id 0x0000, flags DONT_FRAGMENT
UDP: 1234 -> 5001
My registration function below is getting called:
#define UDP_DST_PORT_stream 5001
udp_register_dst_port (vm, UDP_DST_PORT_stream,
udp4_test_node.index, 1 /* is_ip4 */);
But I never get a call when packets are received. Any idea what could be going
wrong or how to debug this?
Thanks,
Guy
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
