Re: vlan on eth0 works eth1-3 do not

Peter Stuge <[email protected]> Wed, 19 Jul 2006 03:33:50 +0200
Newsgroups gmane.linux.drivers.vlan
Message-ID <[email protected]>
On Tue, Jul 18, 2006 at 01:24:27PM +0100, Linux wrote:
> > > eth0: 192.168.20.0/24
> > > eth0.40: 192.168.40.0/24
> > > 
> > > eth3: what IP net?
> > > eth3.40: what IP net?
> > 
> > At the moment they are the same as eth0 as they are bridged.

I'm sorry, that statement is not nearly specific enough for me to be
able to help you. I listed four interfaces, "they" is just confusing.
:)

Bottom line, you have to explain what you want to accomplish for
anyone to be able to help.

I think I've figured out your topology now though..


[..]

> > I then need to tell the bridge that any traffic for the 
> > 172.22/255.255.240.0 range not to be bridged but to go to the
> > routing table, so it flows out of eth1, with iptables again
> > controlling the traffic, I think I can do this with correctly
> > placed ebtables rules.

Unless your Linux box is 192.168.20.1 and 192.168.40.1 this will
require either ethernet or ip NAT.


Let's see if I have understood your setup correctly. Please correct
any errors in my guesses:

Your system has four physical interfaces. eth0, eth2 and eth3 are
trunks. eth1 is not a trunk.

eth1 is on the 172.22.240.0/20 network.

The native VLANs (untagged traffic) on eth0, eth2 and eth3 should be
bridged together and all carry the 192.168.20.0/24 network.

eth0.40, eth2.40 and eth3.40 should also be bridged. These VLANs
carry the 192.168.40.0/24 network.


Please also tell us which IP addresses, if any, you want the Linux
box to have on which interfaces.


Changing the native VLAN on eth[023] to a tagged VLAN would simplify
things a bit. I would suggest doing so if you have control over the
switchports.


//Peter