Hi Juan,
When setting multicast routes one must specify the accepting (or RPF) interface
for the prefix. So, additionally, you need;
ip mroute add 224.0.0.5 via GigabitEthernet0/7/0 Accept
note though that while an interface can be configured to be both and accepting
and forwarding interface (i.e. PIM BiDir) packets will not be replicated back
out of the interface they came in on.
Regards,
Neale
From: <vpp-dev-boun...@lists.fd.io> on behalf of Juan Salmon
<salmonju...@gmail.com>
Date: Wednesday, 7 February 2018 at 06:59
To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Subject: [vpp-dev] Problem in forwarding multicast traffic
Hi,
I want to forward multicast traffic with vpp, but after following commands, the
multicast packet drop with ip4-drop.
ip mroute add 224.0.0.5 via GigabitEthernet0/7/0 Forward
ip mroute add 224.0.0.5 via GigabitEthernet0/8/0 Forward
The sample trace is:
00:27:52:305546: dpdk-input
GigabitEthernet0/7/0 rx queue 0
buffer 0x3492: current data 14, length 64, free-list 0, clone-count 0,
totlen-nifb 0, trace 0x2
PKT MBUF: port 0, nb_segs 1, pkt_len 78
buf_len 2176, data_len 78, ol_flags 0x0, data_off 128, phys_addr 0x7c3d24c0
packet_type 0x0
IP4: 52:54:00:42:80:c8 -> 01:00:5e:00:00:05
OSPF: 192.168.20.151 -> 224.0.0.5
tos 0xc0, ttl 1, length 64, checksum 0x6bc3
fragment id 0x979d
00:27:52:305566: ip4-input
OSPF: 192.168.20.151 -> 224.0.0.5
tos 0xc0, ttl 1, length 64, checksum 0x6bc3
fragment id 0x979d
00:27:52:305570: ip4-mfib-forward-lookup
fib 0 entry 6
00:27:52:305572: ip4-mfib-forward-rpf
entry 6 1 Forward,
00:27:52:305572: ip4-drop
OSPF: 192.168.20.151 -> 224.0.0.5
tos 0xc0, ttl 1, length 64, checksum 0x6bc3
fragment id 0x979d
00:27:52:305574: error-drop
ip4-input: ip4 adjacency drop
Best Regards,
Juan Salmon.
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
