Quagga and IPv6 routes ?
-
Hi,
how good prepared it Quagga OSPF package ? I did not found posts in forum search for it.
- I can see that quagga itself can handles IPv6 routes.
- I can see the "redistribute connected" and "redistribute kernel" networks in my table.
- If I tried to "redistribute default route" but got no IPv6 default route in my table.
- And more worse when I tried to set default static route "::0/0" to area 0.0.0.0
Quagga OSPF crashed and won't startup again till I removed it again.
Bests
Reiner
-
Quagga has a separate daemon for IPv6 routes that takes a separate config file that we do not yet support or write out.
It will take a little work to get that going, either by someone in the community doing the work, or someone funding the work.
http://www.nongnu.org/quagga/docs/docs-info.html#SEC65
-
Quagga has a separate daemon for IPv6 routes that takes a separate config file that we do not yet support or write out.
It will take a little work to get that going, either by someone in the community doing the work, or someone funding the work.
http://www.nongnu.org/quagga/docs/docs-info.html#SEC65
ah ok…
-
It would be nice to have first only a basic "text area" support for not yet supported daemons and files like ospf6d.conf, bgpd.conf which saves the text area field 1:1 to config files.
-
In 2nd step it would be great to get a mechanism as in OpenBGBd package to use the automated setup or the manually edited text area for ospfd.conf and if it makes sense zebra.conf (if the file is edited manually (within webinterface) it's saved into quagga package section and no autoconfig is done).
-
The example folder contains following files - and I guess also all needed daemons are installed when quagga package is selected?
babeld.conf, bgpd.conf, ospf6d.conf, ospfd.conf, ripd.conf, ripngd.conf, vtysh.conf, zebra.conf
I think that would be a good balance between an simple automated setup and to let complicated setup run without the need to install the package manually (and therefore let the firewall in an non-easy updateable state)? And it should not be much complicated to create.
What do you think about this?
Bests
Reiner
-
-
Free text config area sounds like a good idea.
As the saying goes: patches accepted :-) (or, preferably, github pull requests)
So long as the new functionality doesn't break the old functionality, it's all fine.
I haven't had time/funding/drive to work on this yet, but if someone else does, feel free.