-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
isisd: When operating multiple areas, the system ID behaves abnormally. #16090
Conversation
3f1e9f5
to
5e0c469
Compare
How do you test the code before pushing if it's even failing to compile? |
When clearing the net in one of the areas, the system ID is unconditionally cleared, even if the net does not include the current system ID. Signed-off-by: zhou-run <[email protected]> isisd: When operating multiple areas, the system ID behaves abnormally. When deleting one of the areas, even if the net under the area includes the current system ID, the system ID still remains. Signed-off-by: zhou-run <[email protected]> isisd: fix frrbot styling issues found fix frrbot styling issues found Signed-off-by: zhou-run <[email protected]> isisd: fix frrbot styling issues found fix frrbot styling issues found Signed-off-by: zhou-run <[email protected]> isisd: Resolve compilation issues. The higher version updates 'struct area_addr' to 'struct iso_address'. Signed-off-by: zhou-run <[email protected]> isisd: fix frrbot styling issues found fix frrbot styling issues found Signed-off-by: zhou-run <[email protected]>
Sorry, I have now corrected the compilation error. |
Possible to verify and test this behavior with topotest? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, waiting on topo test ...
Hmmm... I don't see a multi-area topo test at all ... I'm okay with letting this go without a topo test since it's a bug fix rather than new functionality, but I'll wait on @ton31337 to answer before pushing |
When there are multiple areas on the same router, the following two scenarios exist:
Signed-off-by: zhou-run [email protected]