[lxc-users] Connecting container to tagged VLAN
Guido Jäkel
G.Jaekel at DNB.DE
Wed Jan 27 23:38:56 UTC 2016
Dear Joshua,
you wrote, that there's a trunk on eth1 and eth2. But for eth2, i can't see any VLAN (501 ?) detrunking as with eth1 & eth1.500. In the other hand you wrote, that eth2 is working. Are you shure, that you realy receive this trunk of 3 VLANs on your both eth's?
I'm using a (working) comparable setup: On the host, eth0 is used for host management on a detrunked port. On eth1, there's a trunk with the needed VLANs for different network for a staged environment. On eth1, there is a VLAN decoder for each of the needed VLANs. And this is attached to a seperate software bridge for each VLAN. A container's outside veth is attached for the appropriate bridge - this is done in a start script by a calculated configuration statement based on the container's name. But the lxc host is located on plain hardware, not in a VM.
On 27.01.2016 23:19, Joshua Schaeffer wrote:
> On Wed, Jan 27, 2016 at 2:39 PM, Fajar A. Nugraha <list at fajar.net> wrote:
>>
>>
>> Is eth1 connected to your switch as trunk? If no (e.g. you have the same
>> settings for eth1 and eth2 on the switch side),
>>
>
> Both ports are connected as trunk. As far as the switch side goes each
> ports is configured the same. Trunked for VLAN 10, 500 and 501. Native VLAN
> is 10.
>
> eth2 already works. I set it up for testing outside of all containers (i.e.
> on the host only). From the host:
>
More information about the lxc-users
mailing list