Hello there, Would it be possible to request an ebuild for quagga 0.99.x? The current quagga in portage is 0.98.5-r3, which is a beautiful thing as long as your router is only using ethernet cabling. If you use any kind of ephemeral connections like OpenVPN or pptpd whose interfaces can come up and down with new client or peer connections, quagga <0.99 is hopelessly unuseable. Upstream, version 0.99 is out for many months now, and has at least gone through 0.99.1, 0.99.2, and 0.99.3. It formally claims to fix many bugs with interfaces starting and stopping. 0.98 is so bad that I have to use Debian instead of Gentoo for my main Linux router because it has a 0.99 package available. I'd install from downloaded source, but want to do things "the gentoo way" on this machine because it is somewhat critical. Thanks, as always.
those versions you are talking about are all unstable, but even if we would agree to submit such unstable version into the tree, we still need to wait for a proper realms patch. why don't you use Amir's patch regarding this matter, by enabling fix-connected-rt USE flag? it is a workaround, but I understand it is doing its job.
Fortunately, the realms patch developer just updated its patch for 0.99.3. That means we could bump quagga to 0.99.4 version. Amir, if I understand correctly, your patch shouldn't be applied to the new version. Am I wrong or am I right?
It should not be applied, but I would include it, since everyone needing redundant links and redundant routing over several interfaces of the same box, will need it and will be happy to use it if it's included.
fixed in cvs. I've removed amir-connected-route.patch and fix-connected-rt USE flag from this version. I've tested on my BGP router by shutting down an interface to a peer. Nothing bad happened - kernel routes were instantly removed and quagga closed the peer after the timeout. Amir, if you still experience problems, feel free to re-add the patch and the USE flag in -r1.
