Page MenuHomeVyOS Platform
Create Task
Maniphest T8435

Add support for BGP AS Number "dot" notation in config
Open, NormalPublicFEATURE REQUEST
Actions

Description

Summary

Currently, VyOS only supports the "plain" notation. This leads to ugly configs like this:

bgp {
    peer-group foo {
        /* AS 64500.10101 */
        remote-as 4227082101
    }
    peer-group bar {
        /* AS 64500.10101 */
        remote-as 4227082101
    }
    /* AS 64500.1 */
    system-as 4227072001
}

It would be much nicer if VyOS had BGP dot notation support:

bgp {
    peer-group foo {
        remote-as 64500.10101
    }
    peer-group bar {
        remote-as 64500.10101
    }
    system-as 64500.1
}

Normal plain notation would of course still be possible.

Use case

Datacenter use cases with large 4-byte AS (reserved range starts at 4200000000).

Details

Version
-
Is it a breaking change?
Perfectly compatible
Issue type
Feature (new functionality)

Related Objects

Event Timeline

rchrist created this task.Mar 26 2026, 4:30 PM
Viacheslav subscribed.Mar 26 2026, 4:39 PM
This comment was removed by Viacheslav.
Viacheslav triaged this task as Normal priority.Mar 26 2026, 4:39 PM
rchrist added a comment.Mar 29 2026, 10:12 AM

Working on this and pretty much done, but blocked by https://vyos.dev/T8443 and https://vyos.dev/T8442

I need to adjust the validation logic to handle mixed AS-notations, and stumbled over these issues.

pasik subscribed.Mar 29 2026, 11:51 AM
rchrist added a comment.Apr 10 2026, 11:45 AM

Relevant:
https://github.com/FRRouting/frr/pull/21450
https://github.com/FRRouting/frr/pull/21406
https://github.com/FRRouting/frr/pull/21486

So it seems like nobody from FRR knows why the limitation that you cannot mix internal and external peers (which became pointless with the introduction of remote-as auto) even existed in the first place.

What should we do now? It seems like the PRs that fix FRRs behaviour would only land in some future to-be-released version.

I'm not really sure how we would handle remote-as auto for peer group members, given the current validation bugs in FRR.