Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#10420 - [initscripts] VLAN support for Arch default network script

Attached to Project: Arch Linux
Opened by Antonio Bonifati (ant) - Thursday, 15 May 2008, 07:29 GMT
Last edited by Paul Mattal (paul) - Saturday, 06 February 2010, 14:20 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Dale Blount (dale)
Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


There are two different patches posted in the forum here:

which adds virtual lans support to /etc/rc.d/network. I think basic VLAN support should be added to network script (e.g. see my suggestion in the forum above).

A first reason is that is not difficult. Another reason is VLANs are very useful if one wants to build a router/firewall using Arch Linux. Some servers also use management systems which are often setup by using VLAN number 1 on the same network card the system uses to transmit application data (which go on another VLAN).

A third reason it that they are supported by all other main distros including Debian and alike (e.g see, Gentoo (, OpenSuse ( and many others.

Additional info:
* package version: initscripts-2008.03-4
This task depends upon

Closed by  Paul Mattal (paul)
Saturday, 06 February 2010, 14:20 GMT
Reason for closing:  Won't fix
Additional comments about closing:  With the last response from the filer in 10/08 and Tomas suggesting this be done in netcfg, I am closing this in favor of the implementation in netcfg. Please see FS# 15661 for the pending fix for this in netcfg.
Comment by Aaron Griffin (phrakture) - Thursday, 15 May 2008, 17:29 GMT
Doesn't it make more sense that this be part of the 'vconfig' package in extra? Currently the VLAN utilities are not in core, and are also not commonly used, so it makes more sense that this be implemented _outside_ the core distro (in extra, I mean)
Comment by Antonio Bonifati (ant) - Thursday, 15 May 2008, 20:11 GMT
I agree in theory, but in practice how can vlans be configured if /etc/rc.d/network doesn't offer support for them directly?
Consider that this script provides support for dhcp and setting up routes and one may want to configure VLAN devices over a bond interface (bonding is already supported):

Also bridge + vlan can be combined:

If a separate script will be made it'll mean to duplicate efforts already made in /etc/rc.d/network.

What's wrong with offering vlan support in /etc/rc.d/network and requiring those users that want to use them to explicity install vconfig? Or moving vconfig into core? This package is really small, about only 6 K
Comment by Aaron Griffin (phrakture) - Thursday, 15 May 2008, 20:20 GMT
Hmmm, I'm fairly neutral on this. I'll tell you what: if you can patch support into the network daemon, I will think about moving vconfig to core.
Comment by Glenn Matthys (RedShift) - Tuesday, 17 June 2008, 19:29 GMT
What's the status of this issue? Possible resolution Won't implement?
Comment by Aaron Griffin (phrakture) - Friday, 20 June 2008, 16:33 GMT
  • Field changed: Status (Assigned → Waiting on Response)
I'll leave this opening waiting for a patch from an interested party.
Comment by Antonio Bonifati (ant) - Wednesday, 08 October 2008, 17:56 GMT
Hi, I'm attaching a new version of my VLAN patch. I've just tested this on a server with a quite complex network configuration (bonding + vlan + aliases) and it works.

It's not a complicated patch. I'm just adding two functions (vlan_up and vlan_down) and I call them after bond_up and before ifdown respectively.

The patch I've made to ifdown is to ensure that aliased or vlan interfaces (ethX:Y or ethX.Y) are properly brought down. Now ifdown does not take the name of the interface from the name of the variabile that defines its configuration in /etc/rc.conf but from the content of this variabile (its just the first word), which I think it's a better choice.
Comment by Aaron Griffin (phrakture) - Wednesday, 08 October 2008, 22:30 GMT
Thomas, would you mind reviewing. More eyes and all that. I'll take a look at this as soon as I am able.
Comment by Alexander Drozdov (adrozdov) - Sunday, 23 November 2008, 03:26 GMT
Hi all,

I make my solution based on Debian vlan script. As Antonio I create two functions vlan_up and vlan_down, but currently supported two VLAN notations: ethX.Y and ethX.YYYY. Also, notation ethX:Y IS NOT VLAN! It is alias (similar to: ip addr add...) and it is currently work without any changes. My patch is attached to this message. Also latest version avail via link:

Some information I wrote in article in my blog (Russian only, sorry):
Comment by Alexander Drozdov (adrozdov) - Sunday, 23 November 2008, 03:28 GMT
Sorry, forget attach patch. I do it in this message ;)
Comment by Dale Blount (dale) - Friday, 27 February 2009, 15:56 GMT
Fails horribly on current network scripts.

/etc/rc.d/network: line 121: /usr/sbin/iwconfig: No such file or directory
/etc/rc.d/network: line 125: iwgetid: command not found
.100: error fetching interface information: Device not found
/etc/rc.d/network: line 121: /usr/sbin/iwconfig: No such file or directory
/etc/rc.d/network: line 125: iwgetid: command not found
.180: error fetching interface information: Device not found
Comment by Aaron Griffin (phrakture) - Friday, 27 February 2009, 17:33 GMT
Looks like it depends on wireless_tools ?
Comment by Dale Blount (dale) - Friday, 27 February 2009, 17:42 GMT
I thought that too, but that just doesn't make sense. iwconfig has nothing to do with vlans (although I suppose you might be able to vlan a wireless device if you wanted...).
Comment by Dale Blount (dale) - Tuesday, 14 April 2009, 20:27 GMT
I tried the original patch by Antonio and it works (other than the diff is reversed) with the exception of DHCP. Antonio, have you tested/implemented dhcp on a vlan?
Comment by Oluf Lorenzen (Finkregh) - Monday, 02 November 2009, 09:45 GMT
there is another patch (for netcfg)

i think an implementation to netcfg is more transparent (basic networking w/o netcfg, higher granularity /w netcfg). thoughts?
Comment by Thomas Bächler (brain0) - Monday, 02 November 2009, 13:28 GMT
I actually agree with Oluf here. The networking support in initscripts is just for the very basic stuff, advanced networking (like VLAN) should definitely move to netcfg instead.
Comment by Oluf Lorenzen (Finkregh) - Sunday, 17 January 2010, 20:29 GMT
> Status Waiting on Response

sweet, finally ^^