tree 107e951abc716c2ca15fbcc62bdb0858b35036e8
parent a83a1e9c2f035d3152451dcfc97ab13b4ac427b9
author Pradosh Mohapatra <pmohapat@cumulusnetworks.com> 1389551413 +0000
committer Vincent JARDIN <vincent.jardin@6wind.com> 1392021450 +0100

bgpd: bgpd-set-v4-nexthop-for-v6-peering.patch

BGP: While advertising v4 prefixes over a v6 session, set the correct v4 nexthop.

ISSUE:

For an IPv6 peer, BGPd sets the local router-id as the next-hop's v4 address.
This is incorrect as the router-id may not be a valid next-hop to be included
in UPDATEs that contain v4 prefixes.

PATCH:

Set the v4 address in the next-hop field based on the interface that the
peering is on (directly connected interface or loopback).

Signed-off-by: Pradosh Mohapatra <pmohapat at cumulusnetworks.com>
Reviewed-by: Scott Feldman <sfeldma at cumulusnetworks.com>
Acked-by: Feng Lu <lu.feng@6wind.com>