Skip to content

BGP should work correctly on machines with multiple interfaces #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
danderson opened this issue Mar 4, 2018 · 0 comments
Closed

BGP should work correctly on machines with multiple interfaces #182

danderson opened this issue Mar 4, 2018 · 0 comments
Assignees
@danderson
Labels
enhancement
Milestone
v0.5.0

Comments

@danderson
Copy link
Contributor

The BGP speaker currently uses the Kubernetes node IP as the next-hop for all traffic. This works fine on clusters with single interfaces/IPs, but falls apart in clusters where machines have several NICs and IPs.

A more flexible solution would be to use the BGP session's source IP as the nexthop, and stop getting IPs via the k8s Downward API. That way, the kernel's source IP selection will help us make the correct choice in all cases.
@danderson danderson self-assigned this Mar 4, 2018
@danderson danderson added this to the v0.5.0 milestone Mar 4, 2018
danderson added a commit that referenced this issue Mar 5, 2018
@danderson
Derive router ID from the BGP session's TCP connection. #182
3b3fe5d 
The config can still override the router ID, but if none is specified,
it defaults to whatever the source IP on the BGP session connection is.
danderson added a commit that referenced this issue Mar 5, 2018
@danderson
Use the BGP session's source IP as the next-hop for advertisements. #182
ef171b2 


This makes it possible to have different BGP sessions going over different
interfaces, and have them all attract traffic to a nexthop that should
make sense to the peer router.
@Jean-Daniel Jean-Daniel mentioned this issue Apr 13, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danderson danderson

Labels
enhancement
Projects
None yet
Milestone
v0.5.0
Development

No branches or pull requests
1 participant
@danderson