Hi Xyxue, To configure a multicast route with multiple replications, one just needs to add the route with multiple paths (like you would for ECMP on a unicast route).
For example, do: ip mroute 232.1.1.1 via Eth0 Forward ip mroute 232.1.1.1 via Eth1 Forward ip mroute 232.1.1.1 via Eth2 Forward this will then replicate out of the 3 ethernet interfaces. For multicast routes you also need to specify an RPF constraint. This can be one of: 1) Accept only from a given interface: Ip mroute 232.1.1.1 via Eth9 Accept 2) Associate the route with an RPF-ID and which is associated with a LSP (no CLI for that) 3) Accept packets from any interface: ip mroute 232.1.1.1 AA All multicast packets will always undergo lookup in the multicast FIB, so all multicast address (even those in 224.0.0./8) need to be programmed in the multicast FIB in this manner. Just as with unicast routes, if you want VPP to consume those packets do: ip mroute 232.1.1.1 via local The 224.0.0.0/8 entry in the unicast FIB is present in VPP only to prevent against the accidental forwarding of mcast traffic by the unicast FIB. If it weren’t there then the default route would be used, which might mis-forward. Hth, Neale From: <[email protected]> on behalf of 薛欣颖 <[email protected]> Date: Saturday, 3 June 2017 at 08:38 To: vpp-dev <[email protected]> Subject: [vpp-dev] question about mfib Hi guys, In the mfib one ingress interface Correspond to multiple egress interface. Then how can I configure this. In addtion, a multicast message next hop will be 'next0 = IP4_INPUT_NEXT_LOOKUP_MULTICAST' and lookup in mfib: if (PREDICT_FALSE (ip4_address_is_multicast (&ip0->dst_address))) //This multicast message include 224.0.0.0/8 { arc0 = lm->mcast_feature_arc_index; next0 = IP4_INPUT_NEXT_LOOKUP_MULTICAST; } else { arc0 = lm->ucast_feature_arc_index; next0 = IP4_INPUT_NEXT_LOOKUP; if (PREDICT_FALSE (ip0->ttl < 1)) error0 = IP4_ERROR_TIME_EXPIRED; } In the fib I can configure a route about 224.0.0.0/8 .In the mfib I can also configure a route about 224.0.0.5/32 . When I configure a route about 224.0.0.5/32 in mfib. The multicast message start with 224 will lookup in mfib. But it will be dropped. Is that a mistake? DBGvpp# show ip fib ipv4-VRF:0, fib_index 0, flow hash: src dst sport dport proto 0.0.0.0/0 unicast-ip4-chain [@0]: dpo-load-balance: [index:0 buckets:1 uRPF:0 to:[0:0]] [0] [@0]: dpo-drop ip4 0.0.0.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:1 buckets:1 uRPF:1 to:[0:0]] [0] [@0]: dpo-drop ip4 1.1.1.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [index:12 buckets:1 uRPF:11 to:[0:0]] [0] [@4]: ipv4-glean: host-eth2 1.1.1.1/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:13 buckets:1 uRPF:12 to:[0:0]] [0] [@2]: dpo-receive: 1.1.1.1 on host-eth2 224.0.0.0/8 unicast-ip4-chain [@0]: dpo-load-balance: [index:3 buckets:1 uRPF:3 to:[0:0]] [0] [@0]: dpo-drop ip4 240.0.0.0/8 unicast-ip4-chain [@0]: dpo-load-balance: [index:2 buckets:1 uRPF:2 to:[0:0]] [0] [@0]: dpo-drop ip4 255.255.255.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [index:4 buckets:1 uRPF:4 to:[0:0]] [0] [@0]: dpo-drop ip4 In my opinion ,the multicast message which start with 224 is usually the porotocol message, should not have the same process with the multicast message start with 225-239. Please help me point out the problem of my idea. Thanks, xyxue ________________________________
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
