{"push_id":2629717647,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"52cd2dfebc058882091ed3bdc17e4cfd9c3689e1","before":"d5a91f926b7aec85c9a3c7bcb662822f099e5595","commits":[{"sha":"66f5152f9898ba232373d0103b31d9b93c82c151","author":{"name":"Martin Buck","email":"d2c7389c15280995bacb041e409d786e23d28d42@ruag.com"},"message":"pimd: Fix nexthop determination when sending towards RP\n\nWhen sending a PIM join upwards on the RP-based tree, it may get dropped on\nthe last hop before the RP if the RP is reachable via a connected route\n(i.e. there's no associated nexthop). pimd needs to put the nexthop IP\naddress into the PIM join payload and fails to do that if that route has a\nnexthop of 0.0.0.0. So whenever we look up a route to determine the nexthop\nor we receive a nexthop tracking update from Zebra, use the destination\naddress as the nexthop address for connected routes.\n\nFixes #2326.\n\nSigned-off-by: Martin Buck <mb-tmp-tvguho.pbz@gromit.dyndns.org>","distinct":true,"url":"https://api.github.com/repos/LabNConsulting/frr/commits/66f5152f9898ba232373d0103b31d9b93c82c151"},{"sha":"52cd2dfebc058882091ed3bdc17e4cfd9c3689e1","author":{"name":"Russ White","email":"d1818e90f775d1fa111cabb0c1a59ce802530221@riw.us"},"message":"Merge pull request #2347 from gromit1811/pim-connected-nexthop-fix\n\npimd: Fix nexthop determination when sending towards RP","distinct":true,"url":"https://api.github.com/repos/LabNConsulting/frr/commits/52cd2dfebc058882091ed3bdc17e4cfd9c3689e1"}]}
{"actor":{"display_login":"louberger"}}