Skip to content

frr: Extend usage of "localip" option to enforce source-ip of BGP tcp session#5363

Open
n3wtype wants to merge 1 commit intoopnsense:masterfrom
n3wtype:fix_5362
Open

frr: Extend usage of "localip" option to enforce source-ip of BGP tcp session#5363
n3wtype wants to merge 1 commit intoopnsense:masterfrom
n3wtype:fix_5362

Conversation

@n3wtype
Copy link
Copy Markdown
Contributor

@n3wtype n3wtype commented Apr 2, 2026

Related issue
#5362

** solved problem **
Previously "localip" was only used for MD5 Authentication purpose. It was not affecting actuall source-ip used to establish BGP and BFD sessions. Using "updatesource" option was not possible to select specific ip-address. This caused undeterministic address selection for interfaces with multiple ip, it required settings outside of FRR (lika SNAT) to enforce expected IP.

** change made **
After change "localip" when defined is also used as value of update-source param in frr. It takes precedense over interface specified in "updatesource" option

…/179 session.

Previously "localip" was only used for MD5 Authentication purpose.
It was not affecting actuall source-ip used to establish BGP and BFD sessions.
Using "updatesource" option was not possible to select specific ip-address.
This caused undeterministic address selection for interfaces with multiple ip,
it  required settings outside of FRR (lika SNAT) to
enforce expected IP.

After change "localip" when defined is also used as value of update-source param in frr.
It takes precedense over interface specified in "updatesource" option
@AdSchellevis
Copy link
Copy Markdown
Member

There might be regressions for people when suddenly assuming different defaults for the same input, which might not be the end of the world, but to improve long term maintainability, we should add a validation and make this explicit for the user. It's not overly complicated, but does mean more work is needed (a migration to enforce the options and a validation to signal the user about this constraint when chosen).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants