You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if you're connecting to a misconfigured BGP peer, metallb retries the connection every 2s.
Most BGP implementations implement error backoff, where if the session errors out, they will blindly refuse any new connection attempts for N seconds, to avoid overloading their flimsy CPUs with broken BGP sessions.
This means that if you try connecting metallb to a misconfigured peer, the logs will show the "real" error once, followed by 1-3 minutes of "reading from peer: EOF" errors as metallb keeps retrying.
What you expected to happen:
The logs should do a better job of highlighting the real error.
The text was updated successfully, but these errors were encountered:
Is this a bug report or a feature request?:
Feature request
What happened:
Right now if you're connecting to a misconfigured BGP peer, metallb retries the connection every 2s.
Most BGP implementations implement error backoff, where if the session errors out, they will blindly refuse any new connection attempts for N seconds, to avoid overloading their flimsy CPUs with broken BGP sessions.
This means that if you try connecting metallb to a misconfigured peer, the logs will show the "real" error once, followed by 1-3 minutes of "reading from peer: EOF" errors as metallb keeps retrying.
What you expected to happen:
The logs should do a better job of highlighting the real error.
The text was updated successfully, but these errors were encountered: