You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If MultiProtocol is enabled (default) then a BGP session
carries prefixes of both IPv4 and IPv6 families. Our problem is
that with an IPv4 session, FRR can incorrectly pick the
masquerade IPv6 address (instead of the real address) as next hop
for IPv6 prefixes and that won't work. Note that with a dedicated
IPv6 session that can't happen since FRR will use the same
address that was used to stablish the session. Let's
enforce the use of DisableMP for now.
Signed-off-by: Jaime Caamaño Ruiz <[email protected]>
// generate FRRConfiguration for each source FRRConfiguration/node combination
509
-
new:=c.generateFRRConfiguration(
509
+
new, err:=c.generateFRRConfiguration(
510
510
ra,
511
511
frrConfig,
512
512
nodeName,
513
513
selectedNetworks,
514
514
matchedNetworks,
515
515
)
516
+
iferr!=nil {
517
+
returnnil, nil, err
518
+
}
516
519
ifnew==nil {
517
520
// if we got nil, we didn't match any VRF
518
521
returnnil, nil, fmt.Errorf("%w: FRRConfiguration %q selected for node %q has no VRF matching the RouteAdvertisements target VRF or any selected network",
0 commit comments