VLAN - Revision history

Prabuanand: updated page based on confirmation from Ariadne on IRC #alpine-devel on 2025-06-03 16:36:23 and old changes made by ikke

2025-06-03T17:27:41Z

updated page based on confirmation from Ariadne on IRC #alpine-devel on 2025-06-03 16:36:23 and old changes made by ikke

← Older revision		Revision as of 17:27, 3 June 2025
Line 1:		Line 1:
	~~{{Obsolete\|The information is outdated and is not suitable for systems using [[Ifupdown-ng]]. Installing the vlan package may prevent your network from being configured correctly}}~~		This article shows how to configure a network interface as an IEEE 802.1q VLAN trunk. [[Ifupdown-ng]] includess a [https://github.com/ifupdown-ng/ifupdown-ng/blob/main/executor-scripts/linux/link link executor script] to support VLANs configured in the {{path\|/etc/network/interfaces}} file.

	This article shows how to configure a network interface as an IEEE 802.1q VLAN trunk.

	__TOC__		__TOC__
Line 7:		Line 5:
	==Installation==		==Installation==

	~~First~~, ~~install~~ the {{pkg\|vlan\|arch=}} package. ~~This will give you support for VLANs in~~ the ~~{{path\|/etc/network/interfaces}} file.{{Cmd\|apk add~~ {{pkg\|vlan\|arch=}}}}		In the previous versions of Alpine Linux, support for vlan was provided by the {{pkg\|vlan\|arch=}} package instead of [[Ifupdown-ng]], as busybox-ifupdown lacked necessary features. Installing the {{pkg\|vlan\|arch=}} package will result in the removal of {{pkg\|ifupdown-ng}} package and prevent your network from being configured/working properly.

			== Configuration ==

	~~{{Warning\|Installing~~ the ~~vlan package may result in~~ [[Ifupdown-ng]] being ~~replaced by busybox-ifupdown. If you use ifupdown-ng specific config, this may prevent your network from being configured properly~~.}}		All the configuration on this page assumes [[Ifupdown-ng]] is being used.

	~~==Configuration==~~		{{Note\| If [[ifupdown-ng]] is not available/used, use {{ic\|iface eth0.8 inet static}} instead of {{ic\|iface eth0.8}} and use below address format for IPv4 instead of '''203.0.113.2/24 ''' :{{Cat\|/etc/network/interfaces\|address 203.0.113.2
			netmask 255.255.255.0}}}}

	Edit the {{path\|/etc/network/interfaces}} file as follows:{{Cat\|/etc/network/interfaces\|auto eth0.8		Edit the {{path\|/etc/network/interfaces}} file as follows:{{Cat\|/etc/network/interfaces\|auto eth0.8
	iface eth0.8 ~~inet static~~		iface eth0.8
	address 192.168.0.2		address 192.168.0.2/24
	~~netmask 255.255.255.0~~
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0		vlan-raw-device eth0
	vlan_id 8}}		vlan_id 8}}

	~~With the ''vlan'' package installed,~~ {{ic\|ifup}} will find the trailing .8 in eth0.8 and will create a VLAN interface with vid 8 over eth0.		The command {{ic\|ifup}} will find the trailing .8 in eth0.8 and will create a VLAN interface with vid 8 over eth0.

	Alternatively with vlan8 over eth0:{{Cat\|/etc/network/interfaces\|auto vlan8		Alternatively with vlan8 over eth0:{{Cat\|/etc/network/interfaces\|auto vlan8
	iface vlan8 ~~inet static~~		iface vlan8
	address 192.168.0.2		address 192.168.0.2/24
	~~netmask 255.255.255.0~~
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0}}		vlan-raw-device eth0}}
Line 33:		Line 32:

	== Example with bridges associated with VLANs over bonding with differing MTUs on the various VLANs ==		== Example with bridges associated with VLANs over bonding with differing MTUs on the various VLANs ==

	This serves as an example of some of the more complicated networking possible. Particularly, this would work well for a hypervisor attached to a dedicated storage VLAN. Less complicated implementations can be achieved by merely removing the non-applicable parts as follows:{{Cat\|/etc/network/interfaces\|auto lo		This serves as an example of some of the more complicated networking possible. Particularly, this would work well for a hypervisor attached to a dedicated storage VLAN. Less complicated implementations can be achieved by merely removing the non-applicable parts as follows:{{Cat\|/etc/network/interfaces\|auto lo
	iface lo inet loopback		iface lo inet loopback
Line 58:		Line 58:

	auto br10		auto br10
	iface br10 ~~inet static~~		iface br10
	address 192.168.10.1/24		address 192.168.10.1/24
	bridge_ports bond0.10		bridge_ports bond0.10
	bridge_stp off		bridge_stp off
	bridge_fd 0.0}}		bridge_fd 0.0}}


	== Example with two interfaces on the same adapter. One with VLAN and one without ==		== Example with two interfaces on the same adapter. One with VLAN and one without ==
Line 71:		Line 70:
	Then we'll add two new routing tables to the config file. One for each network:{{Cmd\|echo "1 rt1" >> /etc/iproute2/rt_tables;echo "2 rt2" >> /etc/iproute2/rt_tables;}}		Then we'll add two new routing tables to the config file. One for each network:{{Cmd\|echo "1 rt1" >> /etc/iproute2/rt_tables;echo "2 rt2" >> /etc/iproute2/rt_tables;}}

	Now we need to edit the file {{path\|/etc/network/interfaces}} as ~~follows~~ {{Cat\|/etc/network/interfaces\|auto lo		Now we need to edit the file {{path\|/etc/network/interfaces}} as follow {{Cat\|/etc/network/interfaces\|auto lo
	iface lo inet loopback		iface lo inet loopback

Line 78:		Line 77:
	auto eth0		auto eth0
	iface eth0		iface eth0
	address 192.168.1.100/24		address 192.168.1.100/24
	gateway 192.168.1.1		gateway 192.168.1.1
	post-up ip route add 192.168.1.0/24 dev eth0 src 192.168.1.100 table rt1		post-up ip route add 192.168.1.0/24 dev eth0 src 192.168.1.100 table rt1
	post-up ip route add default via 192.168.1.1 dev eth0 table rt1 # actual gateway for this interface		post-up ip route add default via 192.168.1.1 dev eth0 table rt1 # actual gateway for this interface
	post-up ip rule add from 192.168.1.100/32 table rt1		post-up ip rule add from 192.168.1.100/32 table rt1
	post-up ip rule add to 192.168.1.100/32 table rt1		post-up ip rule add to 192.168.1.100/32 table rt1

	# second interface with the vlan tag 5		# second interface with the vlan tag 5
Line 97:		Line 96:

	== See also ==		== See also ==
			*[[Configure Networking\|Main Networking page]]
	*[https://github.com/ifupdown-ng/ifupdown-ng/blob/main/doc/interfaces-vxlan.scd VXLAN manual for Ifupdown-ng]		*[https://github.com/ifupdown-ng/ifupdown-ng/blob/main/doc/interfaces-vxlan.scd VXLAN manual for Ifupdown-ng]
	*[[Configure Networking\|Main Networking page]]

	[[Category:Networking]]		[[Category:Networking]]

Prabuanand: changed wikitags, added links to alternates

2025-03-25T04:26:24Z

changed wikitags, added links to alternates

← Older revision		Revision as of 04:26, 25 March 2025
Line 1:		Line 1:
	{{Obsolete\|The information is outdated and is not suitable for systems using ~~ifupdown~~-ng. Installing the vlan package may prevent your network from being configured correctly}}		{{Obsolete\|The information is outdated and is not suitable for systems using [[Ifupdown-ng]]. Installing the vlan package may prevent your network from being configured correctly}}

	This article shows how to configure a network interface as an IEEE 802.1q VLAN trunk.		This article shows how to configure a network interface as an IEEE 802.1q VLAN trunk.
Line 6:		Line 6:

	==Installation==		==Installation==
	~~First, install the ''vlan'' package. This will give you support for VLANs in the {{path\|/etc/network/interfaces}} file.~~
	~~{{Cmd\|apk add {{pkg\|vlan\|arch=}}}}~~

	{{Warning\|Installing the vlan package may result in ~~ifupdown~~-ng being replaced by busybox-ifupdown. If you use ifupdown-ng specific config, this may prevent your network from being configured properly.}}		First, install the {{pkg\|vlan\|arch=}} package. This will give you support for VLANs in the {{path\|/etc/network/interfaces}} file.{{Cmd\|apk add {{pkg\|vlan\|arch=}}}}

			{{Warning\|Installing the vlan package may result in [[Ifupdown-ng]] being replaced by busybox-ifupdown. If you use ifupdown-ng specific config, this may prevent your network from being configured properly.}}

	==Configuration==		==Configuration==
	Edit the {{path\|/etc/network/interfaces}} file:
	~~<pre>~~		Edit the {{path\|/etc/network/interfaces}} file as follows:{{Cat\|/etc/network/interfaces\|auto eth0.8
	auto eth0.8
	iface eth0.8 inet static		iface eth0.8 inet static
	address 192.168.0.2		address 192.168.0.2
Line 19:		Line 19:
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0		vlan-raw-device eth0
	vlan_id 8		vlan_id 8}}

	~~</pre>~~
	With the ''vlan'' package installed, {{ic\|ifup}} will find the trailing .8 in eth0.8 and will create a VLAN interface with vid 8 over eth0.		With the ''vlan'' package installed, {{ic\|ifup}} will find the trailing .8 in eth0.8 and will create a VLAN interface with vid 8 over eth0.

	Alternatively with vlan8 over eth0:		Alternatively with vlan8 over eth0:{{Cat\|/etc/network/interfaces\|auto vlan8
	~~<pre>~~
	auto vlan8
	iface vlan8 inet static		iface vlan8 inet static
	address 192.168.0.2		address 192.168.0.2
	netmask 255.255.255.0		netmask 255.255.255.0
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0		vlan-raw-device eth0}}
	~~</pre>~~

	A static IP address was used in the examples shown above, but DHCP can be used as well.		A static IP address was used in the examples shown above, but DHCP can be used as well.

	== Example with bridges associated with VLANs over bonding with differing MTUs on the various VLANs ==		== Example with bridges associated with VLANs over bonding with differing MTUs on the various VLANs ==
	This serves as an example of some of the more complicated networking possible. Particularly, this would work well for a hypervisor attached to a dedicated storage VLAN. Less complicated implementations can be achieved by merely removing the non-applicable parts.		This serves as an example of some of the more complicated networking possible. Particularly, this would work well for a hypervisor attached to a dedicated storage VLAN. Less complicated implementations can be achieved by merely removing the non-applicable parts as follows:{{Cat\|/etc/network/interfaces\|auto lo
	~~<pre>~~
	auto lo
	iface lo inet loopback		iface lo inet loopback

Line 68:		Line 62:
	bridge_ports bond0.10		bridge_ports bond0.10
	bridge_stp off		bridge_stp off
	bridge_fd 0.0		bridge_fd 0.0}}
	~~</pre>~~

	== Example with two interfaces on the same adapter. One with VLAN and one without ==		== Example with two interfaces on the same adapter. One with VLAN and one without ==

	Since Linux doesn't allow multiple default gateways we need to use a second routing table using iproute2		Since Linux doesn't allow multiple default gateways we need to use a second routing table using iproute2:{{Cmd\|apk add {{pkg\|iproute2\|arch=}}}}

	{{Cmd\|~~apk add {{pkg\|~~iproute2~~\|arch=}}~~}}		Then we'll add two new routing tables to the config file. One for each network:{{Cmd\|echo "1 rt1" >> /etc/iproute2/rt_tables;echo "2 rt2" >> /etc/iproute2/rt_tables;}}

	~~Then~~ we~~'ll add two new routing tables~~ to the ~~config~~ file~~. One for each network~~		Now we need to edit the file {{path\|/etc/network/interfaces}} as follows {{Cat\|/etc/network/interfaces\|auto lo

	{{~~Cmd~~\|~~echo "1 rt1" >>~~ /etc/~~iproute2~~/~~rt_tables;echo "2 rt2" >> /etc/iproute2/rt_tables;~~}}

	~~Now we need to edit~~ {{~~path~~\|/etc/network/interfaces}}

	~~<pre>~~
	auto lo
	iface lo inet loopback		iface lo inet loopback

Line 94:		Line 81:
	gateway 192.168.1.1		gateway 192.168.1.1
	post-up ip route add 192.168.1.0/24 dev eth0 src 192.168.1.100 table rt1		post-up ip route add 192.168.1.0/24 dev eth0 src 192.168.1.100 table rt1
	post-up ip route add default via 192.168.1.1 dev eth0 table rt1 # ~~the~~ actual gateway for this interface		post-up ip route add default via 192.168.1.1 dev eth0 table rt1 # actual gateway for this interface
	post-up ip rule add from 192.168.1.100/32 table rt1		post-up ip rule add from 192.168.1.100/32 table rt1
	post-up ip rule add to 192.168.1.100/32 table rt1		post-up ip rule add to 192.168.1.100/32 table rt1
Line 103:		Line 90:
	address 192.168.5.100/24		address 192.168.5.100/24
	post-up ip route add 192.168.5.0/24 dev eth0.5 src 192.168.5.100 table rt2		post-up ip route add 192.168.5.0/24 dev eth0.5 src 192.168.5.100 table rt2
	post-up ip route add default via 192.168.5.1 dev eth0.5 table rt2 # ~~the~~ actual gateway for this interface		post-up ip route add default via 192.168.5.1 dev eth0.5 table rt2 # actual gateway for this interface
	post-up ip rule add from 192.168.5.100/32 table rt2		post-up ip rule add from 192.168.5.100/32 table rt2
	post-up ip rule add to 192.168.5.100/32 table rt2		post-up ip rule add to 192.168.5.100/32 table rt2}}
	~~</pre>~~
			Note that if you want to add a third interface this way, you'll have to add another routing table.

			== See also ==

	~~Note that if you want to add a third interface this way, you'll have to add another routing table~~		*[https://github.com/ifupdown-ng/ifupdown-ng/blob/main/doc/interfaces-vxlan.scd VXLAN manual for Ifupdown-ng]
			*[[Configure Networking\|Main Networking page]]

	[[Category:Networking]]		[[Category:Networking]]

Ikke: Add warning about information being outdated

2024-12-10T11:53:05Z

Add warning about information being outdated

← Older revision		Revision as of 11:53, 10 December 2024
Line 1:		Line 1:
			{{Obsolete\|The information is outdated and is not suitable for systems using ifupdown-ng. Installing the vlan package may prevent your network from being configured correctly}}

	This article shows how to configure a network interface as an IEEE 802.1q VLAN trunk.		This article shows how to configure a network interface as an IEEE 802.1q VLAN trunk.

Line 7:		Line 9:
	{{Cmd\|apk add {{pkg\|vlan\|arch=}}}}		{{Cmd\|apk add {{pkg\|vlan\|arch=}}}}

			{{Warning\|Installing the vlan package may result in ifupdown-ng being replaced by busybox-ifupdown. If you use ifupdown-ng specific config, this may prevent your network from being configured properly.}}
	==Configuration==		==Configuration==
	Edit the {{path\|/etc/network/interfaces}} file:		Edit the {{path\|/etc/network/interfaces}} file:

Zcrayfish: /* Configuration */ Fixed second example config. (address and netmask CANNOT be combined)

2024-01-29T18:59:13Z

Configuration: Fixed second example config. (address and netmask CANNOT be combined)

← Older revision		Revision as of 18:59, 29 January 2024
Line 24:		Line 24:
	<pre>		<pre>
	auto vlan8		auto vlan8
	iface vlan8		iface vlan8 inet static
	address 192.168.0.2~~/24~~		address 192.168.0.2
			netmask 255.255.255.0
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0		vlan-raw-device eth0

Zcrayfish: /* Configuration */ space -> tab

2024-01-29T18:57:34Z

Configuration: space -> tab

← Older revision		Revision as of 18:57, 29 January 2024
Line 13:		Line 13:
	iface eth0.8 inet static		iface eth0.8 inet static
	address 192.168.0.2		address 192.168.0.2
	netmask 255.255.255.0		netmask 255.255.255.0
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0		vlan-raw-device eth0

Zcrayfish: /* Configuration */ Fixed first example config. (address and netmask CANNOT be combined)

2024-01-29T18:57:15Z

Configuration: Fixed first example config. (address and netmask CANNOT be combined)

← Older revision		Revision as of 18:57, 29 January 2024
Line 12:		Line 12:
	auto eth0.8		auto eth0.8
	iface eth0.8 inet static		iface eth0.8 inet static
	address 192.168.0.2~~/24~~		address 192.168.0.2
			netmask 255.255.255.0
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0		vlan-raw-device eth0

Zcrayfish: Spelling/grammar, template usage... Remove the note at the top of the article about an ancient version of Alpine; anyone using such an old version is totally on their own!

2024-01-29T18:39:57Z

Spelling/grammar, template usage... Remove the note at the top of the article about an ancient version of Alpine; anyone using such an old version is totally on their own!

← Older revision		Revision as of 18:39, 29 January 2024
Line 3:		Line 3:
	__TOC__		__TOC__

	~~{{Note\| Alpine Linux v2.4 or later is required}}~~
	==Installation==		==Installation==
	First, install the ''vlan'' package. This will give you support for ~~vlans~~ in the ''/etc/network/interfaces'' file.		First, install the ''vlan'' package. This will give you support for VLANs in the {{path\|/etc/network/interfaces}} file.
	{{Cmd\|apk add vlan}}		{{Cmd\|apk add {{pkg\|vlan\|arch=}}}}

	==Configuration==		==Configuration==
	Edit the ''/etc/network/interfaces'' file:		Edit the {{path\|/etc/network/interfaces}} file:
	<pre>		<pre>
	auto eth0.8		auto eth0.8
Line 19:		Line 18:

	</pre>		</pre>
	With the ''vlan'' package installed, ifup will find the trailing .8 in eth0.8 and will create a ~~vlan~~ interface with vid 8 over eth0.		With the ''vlan'' package installed, {{ic\|ifup}} will find the trailing .8 in eth0.8 and will create a VLAN interface with vid 8 over eth0.

	~~Alternativly~~ with vlan8 over eth0:		Alternatively with vlan8 over eth0:
	<pre>		<pre>
	auto vlan8		auto vlan8
Line 30:		Line 29:
	</pre>		</pre>

	A static ip address was used in the examples shown above, but ~~dhcp~~ can be used as well.		A static IP address was used in the examples shown above, but DHCP can be used as well.

	== Example with bridges associated with VLANs over bonding with differing MTUs on the various VLANs ==		== Example with bridges associated with VLANs over bonding with differing MTUs on the various VLANs ==
Line 67:		Line 66:
	</pre>		</pre>

	== Example with two interfaces on the same adapter. One with ~~vlan~~ and one without ==		== Example with two interfaces on the same adapter. One with VLAN and one without ==

	Since ~~linux~~ doesn't allow multiple default gateways we need to use a second routing table using iproute2		Since Linux doesn't allow multiple default gateways we need to use a second routing table using iproute2

	{{Cmd\|apk add iproute2}}		{{Cmd\|apk add {{pkg\|iproute2\|arch=}}}}

	Then we'll add two new ~~routig~~ tables to the config file. One for each network		Then we'll add two new routing tables to the config file. One for each network

	{{Cmd\|echo "1 rt1" >> /etc/iproute2/rt_tables;echo "2 rt2" >> /etc/iproute2/rt_tables;}}		{{Cmd\|echo "1 rt1" >> /etc/iproute2/rt_tables;echo "2 rt2" >> /etc/iproute2/rt_tables;}}

	Now we need to edit /etc/network/interfaces		Now we need to edit {{path\|/etc/network/interfaces}}

	<pre>		<pre>
Line 83:		Line 82:
	iface lo inet loopback		iface lo inet loopback

	# the native interface without a ~~vlan~~ (also called untagged)		# the native interface without a VLAN (also called untagged)

	auto eth0		auto eth0

Nailko: config fix

2024-01-29T14:57:56Z

config fix

← Older revision		Revision as of 14:57, 29 January 2024
Line 12:		Line 12:
	<pre>		<pre>
	auto eth0.8		auto eth0.8
	iface eth0.8		iface eth0.8 inet static
	address 192.168.0.2/24		address 192.168.0.2/24
	gateway 192.168.0.1		gateway 192.168.0.1

Arrogance: Arrogance moved page Vlan to VLAN

2023-05-30T07:28:51Z

Arrogance moved page Vlan to VLAN

← Older revision	Revision as of 07:28, 30 May 2023
(No difference)

Ikke at 21:15, 3 May 2023

2023-05-03T21:15:55Z

← Older revision		Revision as of 21:15, 3 May 2023
Line 15:		Line 15:
	address 192.168.0.2/24		address 192.168.0.2/24
	gateway 192.168.0.1		gateway 192.168.0.1
	vlan-raw-device eth0		vlan-raw-device eth0
	vlan_id 8		vlan_id 8

	</pre>		</pre>