Fix dynamic neighbor connect failed with auth-password(TCP-MD5) and wildcard mask #2861
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to use dynamic neighbor to accept all bgp clients, so I using the following config. BUT, all the bgp clients can not connect to gobgp.
I used
tcpdump -M
to capture the traffic, and I found the MD5 authentication was correct. At the end, I found the problem turned out to be the use of::/0
. In the current code, when the IPv4 or IPv6 mask is 0 (such as wildcard mask),TCP_MD5SIG
will be used rather thanTCP_MD5SIG_EXT
, it cause the issue.I've fixed it.