-
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
EIGRP Support #275
Comments
Currently being worked: |
This code forms neighbors and passes eigrp updates with routes around. |
hi Donald. i do not know if it is right to announce this problem here or should i create another Issue. any way i post it here. |
@mTaleqani Yes I am aware of this issue. I have not had time to look at this issue, yet. I was hoping @diivious was going to have time to look at it and point out the issue for me :) |
Please check out my branch listed above, EIGRP now installs routes: robot.cumulusnetworks.com# show ip route K>* 0.0.0.0/0 via 10.0.2.2, enp0s3
robot.cumulusnetworks.com# Probably still needs work... and no real testing has been done other than to prove that they have been installed |
hummm... |
@diivious - Try here: I just gave you collaborator permission too on the REP |
a |
@donaldsharp - I have tested it several times and now EIGRP successfully inserts routes into zebra daemon, then i leave it running and after 30 minutes (sometimes after an hour) zebra daemon crashes and a syslog message saying "Warning: closing connection to zebra because of an I/O error!" is printed and zebra daemon is killed and thus all the routes are removed from the kernel, but EIGRP daemon is still running and working. |
@mTaleqani do you have a stack trace? Since Zebra is crashing that implies that eigrp is sending bad data. Do we have any other logs? I'll set this up a bit later today and see what I can make happen. |
@donaldsharp - unfortunately did not get any other logs except the one i mentioned above. |
@mTaleqani - I just found and fixed an issue in the send of data to zebra involved with a route delete. Please give this new version another try. |
@donaldsharp - now route delete does not work for the zebra. i mean if an eigrp route is gone, eigrpd topology table reacts to it and it removes it from it's topology table but that route still alive in zebra daemon :( |
@mTaleqani -> Fixed another issue with the send down of data. Probably still more work ahead :) |
@donaldsharp - now eigrpd and zebra successfully add and remove routes when changes happen to the network. |
@donaldsharp - i made some changes to the one of the eigrpd neighbors (cisco router) and one of the neighbors now advertise the same routes with higher metric. so now both routes are visible in eigrp topology table but none are inserted to the zebra daemon! it is shown in the following pictures : this is the topology that i am using : Conclusion : when both routers advertise the routes with the same metrics, although it is shown in the topology table as "2 Successors", only one of them is inserted to the zebra daemon. but if one of the neighbors advertise the same routes with higher metrics, although they are shown in the topology table and stated as "1 Successor Route", none of them are inserted to the zebra daemon. |
@mTaleqani I just addressed some rib add/del issues, cleaned up some memory leaks. Please give it another whirl |
@donaldsharp - they are all fixed and working like a charm 👍 . when vtysh is called some warnings are printed out but i guess do not affect to vtysh functions. the warnings are shown in the following pictures : there are still some EIGRP features that not working still (probably not implemented yet) : |
@mTaleqani - I fixed the max-path issue last night (untested) and pushed it up. router-id is going to be more work than I want to do. Question to all -> What do we need to do to consider this ready for a PR? |
@donaldsharp - maximum-path still not working. when it is set to 1 there are still 2 eigrp routes in rib. |
@mTaleqani - Yes you are correct, I wrote no code to handle the situation of setting max-paths after we have already brought up neighbors. Save the config and reload and things should work. Hopefully 'good enough' for the moment. I'll take a look at passive-interface while I got some time this afternoon to see what I can scrumble up. |
passive-interface commands are now accepted on the branch but nothing is done about it yet. That code has not been written yet |
Add EIGRP to FRR
The text was updated successfully, but these errors were encountered: