[quagga-dev 10514] Re: Adding "encapsulation dot1q" option to interfaces

Adrian Ban bluelightning at mantech.ro
Fri May 3 06:51:31 BST 2013

There is somewhere a documentation about Quagga which says that adding 
interface functions are outside the scope? I'm curious where is written.
If other Quagga users will ask to add those kind of new features will be 
refused by Quagga maintainers as well because is outside the scope even 
the features will be fully complained with***Unix platforms, 
particularly FreeBSD, Linux, Solaris and NetBSD***?

It's work quite well outside the Quagga and will work quite well inside 
the Quagga because will be the same code as the tools which the OS uses. 
What is in iproute/ifconfig/dlamd will be in Quagga as well. I don't see 
where is the issue.

I think that all of you that you are saying those feature will 
complicate the code of Quagga you didn't take a look into those tools to 
check the code and see how the code is working in my opinion.

I will add this feature anyway and I will make it public and I will be 
curious how it will be accepted by the community.

Best regards.

On 5/3/2013 5:16 AM, Dinesh Dutt wrote:
> For what it is worth, I feel the same way as David, Stephen and Nick.
> I'm not in favor of complicating the quagga code for something that
> works quite well outside quagga and feels outside the scope of quagga.
> Dinesh
> On 05/02/2013 09:54 AM, Stephen Hemminger wrote:
>> I understand the desire for a single management CLI but this seems like
>> adding unnecessary. There a lots of subtleties to interface management and
>> the world is bigger than just simple VLAN's. What about tunnels, what about
>> all the possible VLAN options (like priority and QinQ)? And BSD, Linux, Solaris,
>> et all have different features and options. It also means more work for developers
>> as you duplicate functionality of other tools.
>> IMHO the current Quagga suffers from doing to much in the shell. But I
>> am and old Unix believer who believed 'cat -v considered harmful'.
>> XORP tried to do a unified model, and it ended up being a whole shell.
>> Disclosure:
>> I work for Vyatta which has a full router style CLI. Therefore your change
>> overlaps what we do. There is a open-source version of Vyatta, maybe that
>> would meet your needs.
>> _______________________________________________
>> Quagga-dev mailing list
>> Quagga-dev at lists.quagga.net
>> http://lists.quagga.net/mailman/listinfo/quagga-dev
> _______________________________________________
> Quagga-dev mailing list
> Quagga-dev at lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20130503/39414e5f/attachment-0001.html>

More information about the Quagga-dev mailing list