os-frr: add neighbor local-as no-prepend/replace-as options
@Monviech is already working on this.
Since Aug 30, 2026.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
Neighbor-level local-as was added in #5308, but FRR's no-prepend and replace-as modifiers are not exposed in the BGP neighbor UI.
Without those modifiers, FRR prepends the Local AS to received AS-Paths and still uses the real AS in outbound updates. That is often not the desired behavior for ASN migrations or provider peering such as AWS Direct Connect.
Describe the solution you'd like
Add an optional per-neighbor Local AS Options field in Routing -> BGP neighbor configuration, supporting:
no-prependno-prepend replace-as
Example FRR config:
router bgp 65000 neighbor 203.0.113.2 remote-as 64496 neighbor 203.0.113.2 local-as 65123 no-prepend replace-as
Describe alternatives you've considered
Manual vtysh configuration. That is not a proper solution because OPNsense regenerates FRR config and those changes may be lost.
Additional context
Follow-up to #5307 / #5308. FRR already supports these modifiers natively; this only exposes them in the plugin UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.