Page MenuHomeVyOS Platform

BGP IPv6 multipath support
Open, LowPublicFEATURE REQUEST

Details

Difficulty level
Hard (possibly days)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)

Event Timeline

syncer added a subscriber: syncer.

Daniil, please take a look and merge

Apparently this doesn't work because of the ancient Quagga version.

syncer changed the subtype of this task from "Task" to "Feature Request".Oct 19 2018, 9:27 AM
syncer changed the visibility from "Subscribers" to "Public (No Login Required)".Oct 19 2018, 9:34 AM
syncer added a project: VyOS 1.3 Equuleus.

must be reviewed and adjusted to FRR

It may be supported but the syntax in the Pull-request is wrong and does not work for FRR, it needs to be adjusted.

Frankly, I can see why FRR doesn't want it to be modifiable at runtime. If you are decreasing the number, it would force a big routing table rebuild, and tracking whether the user increased or decreased it to decide if command should be allowed or not is more trouble than it's worth.

Maybe it should be an option outside of the BGP tree, not sure.

zsdc changed Difficulty level from Unknown (require assessment) to Hard (possibly days).Mar 11 2021, 2:13 PM
zsdc set Is it a breaking change? to Unspecified (possibly destroys the router).

Needs to migrate "maximum-paths" to afi and add ipv6 (1.3)

vyos@r1.3# set protocols bgp 65001 maximum-paths 
Possible completions:
   ebgp         Maximum ebgp multipaths
   ibgp         Maximum ibgp multipaths

To address-family ipv4|ipv6 as it in the 1.4

vyos@r-roll01# set protocols bgp 65001 address-family ipv4-unicast maximum-paths 
Possible completions:
   ebgp         eBGP maximum paths
   ibgp         iBGP maximum paths

vyos@r-roll01# set protocols bgp 65001 address-family ipv6-unicast maximum-paths 
Possible completions:
   ebgp         eBGP maximum paths
   ibgp         iBGP maximum paths