On Tue, Oct 07, 2008 at 11:55:25AM +0200, ard wrote: > I wasn't aware that vlans could be configured using ip. I knew > that with the macvlan in the kernel that they can only be > configured using ip and not vconfig.
I've only spotted a file called iplink_vlan.c appearing in the source a while ago, didn't really know any more about it. The only thing that hit me, when seing the mail talking about vconfig being deprecated, was that a consistent user interface for these features is over due and filing a bug would be a way to get the ball rolling within Debian... Running "ip link help" doesn't give any hints at all about vlans or even the possibility to "add" which apparently exists... > > I have to investigate since when ip and especially the kernel can > understand what vconfig used to do. A test command for knowing if vlan is supported by your iproute command: ip link add testvlan type vlan help Etch's iproute is apparently too old, Lenny is new enough (latest release). Further investigation needed to make sure ip really provides all the vlan functionality that vconfig provides. > > For internal usage I maintain vlan for sarge, etch and sid, > including macvlan config support. So, yes, it's not that easy: > I have to use vconfig *and* (mvconfig|ip) (depending on the > kernel, only a few systems have kernel native macvlan support), > so... > /me sighs... > Yeah, sucks to have to deal with old stuff - specially pre-2.6 kernels. Doesn't look like you'll get away from it soon though. Even if you manage to drop sarge of that list, etchs iproute is not new enough (no idea about when the kernel started to provide vlan config over netlink). On the bright side, it looks like you really have personal interest in getting the mess cleaned up properly so you don't have to maintaining the differences internally in the future. ;) Have a good day! -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
