'ip mroute x.y.z.0/len a.b.c.d' does work for multicast RPF #10516
Unanswered
arundesigan
asked this question in
Q&A
Replies: 1 comment 2 replies
-
This is currently broken for multicast RPF lookup. I believe it is on someone's radar to get fixed |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I using the stable/8.1 branch and running into the following issue, basically none of the routes that were added using the ' ip mroute ...' command does not resolve the multicast RPF. For ex.,
frr-vtysh# sh ip rpf
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
C> 10.65.13.0/24 is directly connected, eth0, 01:40:55
C> 11.1.1.0/24 is directly connected, eth6, 01:40:55
C> 12.1.1.0/24 is directly connected, eth5, 01:40:55
S> 14.1.1.0/24 [1/0] via 100.64.0.92, mcast0, weight 1, 01:39:51
S> 15.1.1.0/25 [1/0] via 192.168.1.2, eth1, weight 1, 01:37:48
S> 16.1.1.0/24 [1/0] via 100.64.0.92, mcast0, weight 1, 01:35:11
C> 100.64.0.0/16 is directly connected, mcast0, 01:40:55
C> 192.168.1.0/24 is directly connected, eth1, 01:40:55
C> 192.168.2.0/24 is directly connected, eth2, 01:40:55
C> 192.168.3.0/24 is directly connected, eth3, 01:40:55
C> 192.168.4.0/24 is directly connected, eth4, 01:40:55
frr-vtysh# sh ip rpf 14.1.1.0
% No match for RPF lookup
frr-vtysh# sh ip rpf 15.1.1.1
% No match for RPF lookup
frr-vtysh# sh ip rpf 192.168.1.1
Routing entry for 192.168.1.0/24 using Unicast RIB
Known via "connected", distance 0, metric 0, best
Last update 01:41:21 ago
Beta Was this translation helpful? Give feedback.
All reactions