Quagga Configuration vs Linux


Userlevel 1
I've been configuring a Cumulus switch via the /etc/network/interfaces file, but stumbled upon a few of the same configuration in Quagga. Could I configure swp interfaces, filtering via ACLs and things of the like using Quagga and it have the same effect rather than configuring them via the directory files?

6 replies

Userlevel 5
At the current time, the use of the directory files is still the way to configure those files. That being said the upcoming NCLU release will help in making that simpler. See the doc below.

https://cumulusnetworks.com/media/resources/product-collateral/Cumulus-Networks-NCLU-Overview.pdf

Userlevel 1
Scott Suehle wrote:

At the current time, the use of the directory files is still the way to configure those files. Th...

Thanks Scott
Userlevel 4
NCLU is early access if you want to try it: https://docs.cumulusnetworks.com/display/DOCS/Network+Command+Line+Utility

typically only routing is done in quagga (app for routing). It has L2 functionality (vlans, trunks, bonds, etc). NCLU gives a tab complete cli to etc/network/interfaces and much more 🙂
Userlevel 1
Sean Cavanaugh wrote:

NCLU is early access if you want to try it:


Userlevel 4
To add more info here you can run into weird behaviors.... like when quagga is not running you have no IP addresses applied... or what if the IP in quagga is not the IP applied in /etc/network/interfaces. Troubleshooting may be more difficult as well because things are located in non-standard places. For all those reasons and more, we recommend to leave interface L2/L3 config in the /etc/network/interfaces file. NCLU helps to abstract away where the configuration lives but the config is still actually applied to the /etc/network/interfaces file as we're recommending here.
Userlevel 1
Eric Pulvino wrote:

To add more info here you can run into weird behaviors.... like when quagga is not running you ha...

I will definitely keep that in mind as well as give NCLU a shot. Thanks!

Reply