On Tue, Dec 16, 2014 at 03:46:59PM -0600, Tim Nelson wrote:
> ----- Original Message -----
> > iiuc, you have the following types of packets on eth0:
> >
> > x.x.x.x/24
> > y.y.y.y/24
> > z.z.z.z/24
> > vlan2:a.a.a.a/24
> > vlan3:b.b.b.b/24
> >
> > So, you need x.x.x.x/24, y.y.y.y/24, and z.z.z.z/24 to get routed
> > into vlan3. Does traffic need to go the other way? Is there
> > broadcast or multicast traffic to worry about?
> >
>
> Greetings Jason-
>
> Specifically, I have:
>
> eth0: x.x.x.x/24
> eth0.2: y.y.y.y/29
> eth0.3: z.z.z.z/24
>
> After bridging eth0 and eth0.3, devices on eth0.3 will utilize the
> same address space as that present on eth0 native (x.x.x.x/24). Of
> course, traffic to/from eth0.2 would continue to be functional.
> Traffic *does* need to operate in both directions, and yes there will
> be broadcast traffic originating from eth0.3, as a DHCP request, which
> would be answered by a DHCP server on the eth0 native connected
> network.
I'm sure I'm missing something, but a quick test in a VM worked:
[root@triton] # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00163e1c9a87 no eth126
eth126.3
eth126.3 did not have an ip address. eth126 did, but you have to set
both interfaces promiscuous and 0.0.0.0. Then, assign an IP in the
range z.z.z.z/24 to br0.
hth,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
