If we receive a hello on an interface from an ip address that is not
associated with that interfaces subnet pim accepts the neighbor:
(config-if)# do test pim receive hello swp1 10.1.1.1 105 333 44244 2000
4000
l11(config-if)# do show ip pim neighbor
Recv flags: H=holdtime L=lan_prune_delay P=dr_priority G=generation_id
A=address_list
T=can_disable_join_suppression
Interface Address Neighbor Uptime Timer Holdt DrPri GenId
Recv
swp1 169.254.0.1 169.254.0.2 00:10:20 01:31 01:45 1
d9d3b9f9 HLPG
swp1 169.254.0.1 10.1.1.1 00:00:11 01:37 01:45 333
0000acd4 HLPG T
swp2 169.254.0.5 169.254.0.6 00:10:18 01:28 01:45 1
d9d3b9f9 HLPG
swp3 169.254.0.9 169.254.0.10 00:10:21 01:31 01:45 1
db1de8a2 HLPG
swp4 169.254.0.13 169.254.0.14 00:10:20 01:27 01:45 1
da9eea61 HLPG
l11(config-if)# do show ip pim designated-router
NonPri: Number of neighbors missing DR Priority hello option
DrPri: Designated Router Priority sent
Interface Address DR Uptime Elections Changes NonPri
DrPri
swp1 169.254.0.1 10.1.1.1 00:00:21 3 3 0
1
swp2 169.254.0.5 169.254.0.6 00:10:28 2 2 0
1
swp3 169.254.0.9 169.254.0.10 00:10:31 2 2 0
1
swp4 169.254.0.13 169.254.0.14 00:10:30 2 2 0
1
The RFC does not explicitly call this situation out, but in general it's
frowned upon for routing protocols. I'm leaning towards calling this a bug
and fixing this issue. Anyone have any different thoughts on the matter?
donald
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
