diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2015-05-19 18:04:07 -0700 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2015-05-19 18:04:07 -0700 |
| commit | 2c19a6ec62c6ed4450d237a467734fd24455a983 (patch) | |
| tree | ae5661345b3cb23515421323b34aac05a022b95e /ospfd/ospf_packet.c | |
| parent | 91ba2c8be3d46460f2b03a46c14f1f9283c91cb4 (diff) | |
Changing router-id inline isnt handled correctly in the current implementation.
At the minimum, the OSPF_LSA_SELF logic isnt foolproof, and it may hit assert
in ospf_refresh_unregister_lsa on a router-id change.
Once OSPF has created and flooded LSAs, its not a good idea to change
router-id inline. Tying it to restart has at least two benefits:
- Implementation can remain sane by not having to re-adjust neighbors and LSAs,
based on the new router-id.
- Works as a deterrent for the user to not meddle with the router-id unless
really needed.
Diffstat (limited to 'ospfd/ospf_packet.c')
0 files changed, 0 insertions, 0 deletions