At the following URL I have posted a new ebuild and associated files: http://voidptr.sboost.org/quagga/ If you do not wish to bother with portage overlay the following steps should be sufficient for installing quagga with this ebuild: 1) Place the ebuild in /usr/portage/net-misc/quagga/ 2) Place the 2 patches in /usr/portage/net-misc/quagga/files/ (Keep the bz2!) 3) Place the digest file in /usr/portage/net-misc/quagga/files/ 4) Feel free to copy the changelog ;) either add "net-misc/quagga ~x86" to /etc/portage/package.keywords or specify ACCEPT_KEYWORDS="~x86" during emerge. 5) ACCEPT_KEYWORDS="~x86" emerge -av quagga Please report any problems to voidptr@voidptr.sboost.org Reproducible: Always Steps to Reproduce: 1. 2. 3.
Greetings: I have done as you asked and tried out the updated ebuild (0.98-r1) that you privided. In general, it worked successfully. I had the following specific problem that I had to resolve: The digest that you provided did not seem to be correct. I modified the digest to: MD5 8757b155aa2458f6158ccd330d0e1b39 quagga-0.98.2.tar.gz 2012251 before the ebuild work work. Beyond that, it seems to be working properly. The library naming issues seem to be resolved. I currently have it listening only because if I screw up the routing on the network my phone rings off of the hook with upset users and I'm just not up to dealing with that today. Once everyone leaves for the evening I will let it broadcast its routes and make sure that the other machines are ok with it. As a side note, this machine is doing VLANs on top of a bonded interface and quagga seems to be handling the odd interface names (bond0.20) without any problems.
Hi Scott, Thanks for testing. The cause of that issue: upstream changed the tarball without a version bumb because of: (follow the thread for full details) http://lists.quagga.net/pipermail/quagga-dev/2005-February/002841.html I will change the digests on my website, thanks for reporting. The only problem that you could run into would be: the ipforward detection. I still have to figure out what problem it solved, and if it is still needed. (Any hints on this are welcome aswell)
Greetings: I fully tested quagga (sending and listening) and it seems to work OK. Just FYI, I don't really use quagga to its full extent. I'm just using RIPv2. I don't use the configuration interface. If I can do anything else for you, just holler.
Thanks for your help. The quagga-0.98.2 ebuild has been merged.
