-
Notifications
You must be signed in to change notification settings - Fork 12
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
Ospf container #820
Ospf container #820
Conversation
1955b15
to
7d58db2
Compare
26ab349
to
a555112
Compare
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.
Nice work! I like how the Frr patch(es) are now with the Frr package instead of in our Infix tree.
As we agreed on AFK, we'll merge despite the issues we've seen on one test system.
This avoids full recompiles every time we want to use things like ply.
During debugging of a reconfiguration issue, one hypothesis was that the tracking of callbacks used to determine when a transaction has completed (as sysrepo has no hooks for this) was out of sync, causing us to call `initctl reload` prematurely. This was not the case, but if it ever occurs in the future, make sure that it is a fatal error that won't go unnoticed.
During development of the upcoming ospf_container test, an issue was discovered where zebra's view of the system drifted from the kernel's ditto. Specifically: when transitioning from test-config to one with many virtual interfaces (VLANs VETH pairs etc.), zebra would not process events for all interfaces, which meant OSPF would not pick them up. Our experience matches very well with a bug reported upstream in: FRRouting/frr#13630 > If we delete kernel interface and create it and set its ip in a > short time, in rare cases, interface ip will be lost in zebra which > can be confirmed by vtysh show interface brirf command. This will > lead to abnormal behavior of other protocol daemons, for example, > bgpd does not announce the route corresponding to interface ip even > it was specified by network command. The issue was marked as fixed by PR 13396, which was merged in the 9.0 cycle: FRRouting/frr#13396 Therefore, upgrade FRR to the latest patch release from that major.
With the FRR upgrade to 9.1.2, OSPF sometimes reports neighbors without reporting the routerDesignatedId and routerDesignatedBackupId attributes. Ensure that these attributes are available before trying to copy them to the output.
a555112
to
e057a29
Compare
Aims to test a complex setup with multiple containers, OSPF and NAT
Signed-off-by: Joachim Wiberg <[email protected]>
Signed-off-by: Joachim Wiberg <[email protected]>
Add ABR configuration and a HTTP Container
Signed-off-by: Joachim Wiberg <[email protected]>
Signed-off-by: Joachim Wiberg <[email protected]>
Add "VLAN switches" between each Router, to only pass the tagged traffic between the routers. Add test specification and add to test suite
Signed-off-by: Joachim Wiberg <[email protected]>
Signed-off-by: Joachim Wiberg <[email protected]>
Always return {} if fail to get OSPF status, it may not have started yet.
e057a29
to
a567ae9
Compare
Add it to gitignore to not be added again.
a567ae9
to
de50179
Compare
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.
Excellent! 🥇
This fixes #652 (but larger 0.0.0.1 case is the same), fixes #776 and fixes #743
Description
Checklist
Tick relevant boxes, this PR is-a or has-a: