Hi, On Sun, Feb 07, 2010 at 05:52:29PM +0100, Marco d'Itri wrote: > On Feb 07, Andreas Henriksson <andr...@fatal.se> wrote: > > > Not that I'm aware of. I'd like to hear from the vlan maintainer what he > > thinks about the suggested solution. Maybe you have news since you > > tagged this bug as a blocker for deprecating the vlan (vconfig) > > packages? > No, I have not heard any news from him and I would like to know if we > can arrange together for vconfig to be deprecated or we will have to > work around him.
Sorry, I am not an official debian maintainer, and so the distance to the community is a little far ;-). > > I'd like the vlan people to continue maintaining vlan related stuff even > > if they are merged into the iproute package. > Ard, are you interested? I am maintaining it, al beit inside the company where I am using it. Since I am not a real debian maintainer I usually let the debian bugs be fixed by a sponsor, but I seem to be out of touch with him. > > I'm not personally interested in maintaining anything related to vlan as > > I don't have any use for it and more importantly doesn't have any way to > > do testing. > This is not a great argument, as I am sure that you have no use for many > other iproute features as well. Well, packaging existing software and adding scripting functionality that you can't test are two different things ;-). > > That would be nice. I'd also like to see ifupdown 0.7. In addition to > > the ifupdown maintainers being unresponsive we now also have kfreebsd - > I am not aware of ifupdown having real maintainers, so it cannot be part > of any solution until one will step up for real. So this needs to be > fixed in iproute at least for the time being. For now I am ignoring that fact ;-). > > An additional question to all of this is why the vlan support should be > > provided by iproute and not ifupdown itself? > No objections on my part, but I'd rather have a working solution in time > for squeeze than a perfect solution in three years. I think all scripts should be integrated into ifupdown, since that's a network framework. iproute and vconfig are just tools. If not integrated, they should be modular addons to ifupdown: ifupdown-bonding, -vlan, etc.... As far as I know about everything can be down with iproute. At least the creation of macvlans is done with iproute in the internal version of vlan at my work. For now the future will probably be that I continue the vlan package (at least in a backward compatability mode), but without the vconfig binary. Within the vlan package I continue to maintain the more generic scripts to set stuff like arp_filter. Maybe it is better to just rename vlan to ifupdown-advancedrouting or something like that ;-). Anyway: current functionality of the internal vlan package: - create vlans with either vconfig or ip depending on vconfig being there. - create macvlans with either mvconfig or ip depending on kernel version - set important network settings like arp_announce, arp_filter, or better: generic /proc/sys/net/ipv4/conf/<devicename>/<setting> This functionality is necessary for H.A. level2 failover setups, of which we have a bunch :-). As a matter of fact: there is an official internal ticket at that company that I should fix and upload a new vlan package. But now without the blah: I am willing to maintain any vlan part that allows me to roll out firewalls fast. So if the scripts in iproute are going to replace the vlan package, I will be willing to maintain that. Especially if that means I don't have to take care of debian specific policies ;-). -- .signature not found -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
