T6222: VRRP show prefix for long rfc3768-compatibility interfaces allow prefix vrrp (backport #3292) #3295
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.
Change Summary
If we use rfc3768-compatibility with long interface names like eth1.100.200 it converts the VRRP interface name name to
<interface>v<VRID><IP version>
For example
eth2.100.200v10v4
The limit for interface name is 15 symbols and it causes that interface name is ignoring by keepalived
VMAC interface name 'eth2.100.200v10v4' too long or invalid characters - ignoring And it uses the default prefix
vrrp
for such cases. It works fine, but such interfaces are not displayed in the op-modeAllow prefix
vrrp
for the op-mode forshow interfaces
Types of changes
Related Task(s)
Related PR(s)
Component(s) name
Proposed changes
How to test
Before the fix we don't see interface with address
203.0.113.1
But actually address exits
After the fix, the expected interface if showing with the prefix
vrrp
Smoketest result
Checklist:
This is an automatic backport of pull request #3292 done by [Mergify](https://mergify.com).