Just how do I set up VLAN forwarding?

I have a DAAP server with numerous VLAN user interfaces. I would love to get website traffic sent on every one of the VLANs. Sent from eth0 to eth1.010 * I've obtained the button set up to be a trunk port with the proper VLANs, and also I made it possible for / proc/sys/net/ ipv4/ip _ onward

Yet that does not appear to be sufficing. Exists anything else I require to do?

Below is my ifconfig results, as you can see the VLAN user interfaces aren't actually obtaining any kind of website traffic:

eth0      Link encap:Ethernet  HWaddr 00:14:d1:10:ca:fc  
          inet addr:192.168.1.20  Bcast:172.21.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:536 errors:0 dropped:0 overruns:0 frame:0
          TX packets:259 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:264232 (258.0 KiB)  TX bytes:37425 (36.5 KiB)
          Interrupt:20 Base address:0xe000 

eth1      Link encap:Ethernet  HWaddr 00:1c:c4:31:28:22  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:303 errors:0 dropped:0 overruns:0 frame:0
          TX packets:202 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:225213 (219.9 KiB)  TX bytes:47118 (46.0 KiB)
          Interrupt:17 

eth1.0101 Link encap:Ethernet  HWaddr 00:1c:c4:31:28:22  
          inet addr:172.17.1.20  Bcast:172.17.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:9076 (8.8 KiB)

eth1.0102 Link encap:Ethernet  HWaddr 00:1c:c4:31:28:22  
          inet addr:172.18.1.20  Bcast:172.18.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:9076 (8.8 KiB)

eth1.0103 Link encap:Ethernet  HWaddr 00:1c:c4:31:28:22  
          inet addr:172.19.1.20  Bcast:172.19.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:9076 (8.8 KiB)

eth1.0104 Link encap:Ethernet  HWaddr 00:1c:c4:31:28:22  
          inet addr:172.20.1.20  Bcast:172.20.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:9076 (8.8 KiB)

eth1.0105 Link encap:Ethernet  HWaddr 00:1c:c4:31:28:22  
          inet addr:172.21.1.20  Bcast:172.21.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:9076 (8.8 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:113 errors:0 dropped:0 overruns:0 frame:0
          TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:20777 (20.2 KiB)  TX bytes:20777 (20.2 KiB)

Below is my/ etc/network/interfaces submit:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# Automagically configured network interfaces
auto eth0
auto eth1.0101
auto eth1.0102
auto eth1.0103
auto eth1.0104
auto eth1.0105

iface eth0 inet static
   address 192.168.1.20
   netmask 255.255.0.0
   gateway 192.168.1.3
   network 172.21.0.0
   broadcast 172.21.255.255

iface eth1.0101 inet static
   address 172.17.1.20
   netmask 255.255.255.0


iface eth1.0102 inet static
   address 172.18.1.20
   netmask 255.255.255.0


iface eth1.0103 inet static
   address 172.19.1.20
   netmask 255.255.255.0


iface eth1.0104 inet static
   address 172.20.1.20
   netmask 255.255.255.0


iface eth1.0105 inet static
   address 172.21.1.20
   netmask 255.255.255.0

Thanks for any kind of aid, I've been working with this for a long time.

0
2019-05-05 12:11:56
Source Share
Answers: 3

I have not done this on Ubuntu yet below's my study until now:

You require to stick

vconfig add eth1 101  
vconfig add eth1 102  
vconfig add eth1 103  
vconfig add eth1 104  
vconfig add eth1 105

in a start-up manuscript.

The user interfaces documents would certainly look something similar to this:

auto lo
iface lo inet loopback
auto eth0 eth1 vlan2 vlan3 vlan4 vlan5
iface eth0 inet dhcp

# VLAN 1 - native management VLAN
iface eth1 inet static
        address 10.0.0.1
        netmask 255.255.255.224
        vlan_raw_device eth1

# VLAN 2 - DMZ
iface vlan2 inet static
        address 10.0.0.33
        netmask 255.255.255.224
        vlan_raw_device eth1

# VLAN 3 - Accounting
iface vlan3 inet static
        address 10.0.0.65
        netmask 255.255.255.224
        vlan_raw_device eth1

# VLAN 2 - DMZ
iface vlan2 inet static
        address 10.0.0.33
        netmask 255.255.255.224
        vlan_raw_device eth1

# VLAN 3 - Accounting
iface vlan3 inet static
        address 10.0.0.65
        netmask 255.255.255.224
        vlan_raw_device eth1

# VLAN 4 - Engineering
iface vlan4 inet static
        address 10.0.0.97
        netmask 255.255.255.224
        vlan_raw_device eth1

# VLAN 5 - Sales & Marketing
iface vlan5 inet static
        address 10.0.0.129
        netmask 255.255.255.224
        vlan_raw_device eth1

You will certainly utilize your very own IPs in the user interfaces documents, clearly. Allow us recognize if it functioned.

Referrals : 1. 2

0
2019-05-09 08:26:25
Source

If I'm reviewing your inquiry appropriately, you are seeking linking. Linking forwards all website traffic from one user interface to an additional.

You will certainly require to install bridge - utils plan and also arrangement your arrangement as adheres to :

auto br0
iface br0 inet static
  address 192.168.1.20
  netmask 255.255.0.0
  gateway 192.168.1.3
  bridge_ports eth0 eth1.0101 eth1.0102 eth1.0103 eth1.0104 eth1.0105

No arrangement is needed for the specific ports.

This will certainly set up the ports to be in one bridge and also needs to make every little thing obtainable. You can see the state of the bridge with brctl command.

0
2019-05-08 19:47:29
Source

It functioned! I've obtained a different trouble with DAAP currently, yet I assume it's Avahi connected. I'll attempt to resolve that myself. Many thanks a bunch.

0
2019-05-08 16:45:40
Source