tree 1d277afb9b346388e1aa244484c3af41dcd6a72e
parent 66d2ead7df2db9144605c973fcd80b88df33f81b
author Pradosh Mohapatra <pmohapat@cumulusnetworks.com> 1378537640 +0000
committer David Lamparter <equinox@opensourcerouting.org> 1401800888 +0200

bgpd: don't compare next-hop to router-id

While announcing a path to a peer, the code currently compares the path's
next-hop with the peer's router-id. This can lead to problems as the router
IDs are unique only within an AS. Suppose AS 1 sends route with next-hop
10.1.1.1. It is possible that the speaker has an established BGP peering
with a router in AS 2 with router ID 10.1.1.1. The route will not be
advertised to that peer in AS 2.

The patch removes this check.

Signed-off-by: Pradosh Mohapatra <pmohapat@cumulusnetworks.com>
Reviewed-by: Dinesh G Dutt <ddutt@cumulusnetworks.com>
Reviewed-by: Shrijeet Mukherjee <shm@cumulusnetworks.com>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>