excessive Quagga package restart when IP change
Already mentioned on this thread one year ago :
Quagga/OSPF services must NOT restart when IP change is detected to avoid 1) losing whole routing table and 2) blocking all other networks during restart phase.
Updated by Kill Bill almost 7 years ago
Updated by Chris Buechler almost 7 years ago
- Project changed from pfSense to pfSense Packages
- Subject changed from Quagga package restart when IP change to excessive Quagga package restart when IP change
- Category changed from Routing to Quagga OSPF
the issue will be addressed at some point. The complication is you can't just not restart in that circumstance, as there are a variety of situations where that would break things (binding to dynamic interfaces for instance). It needs much more logic about when to restart and when not to. In the mean time, for those who don't need it to restart, that patch is the answer. It's not committed because it'll break things for other people's circumstances.