El jue, 26 de 08 de 2004 a las 00:52, Cedric Blancher escribiÃ:
I don't exactly get what you want to achieve. Especially, I don't get
the link between VLAN support and IP/MAC changing... Maybe you can be
more specific.
Ok. Now I understand it. The work with the MACs/IPs it's done at the
switch with the kernel module, so Linux can't be fooled changing the
MACs.
By the way, Linux supports 802.1q VLAN encapsulation. This means you can
connect a Linux box to a VLAN aware switch using a 802.1q trunk to one
of its interfaces, say eth0. Then you can add logical interfaces to each
VLAN carried by your trunk, sau eth0.1, eth0.2, etc. (naming can be
changed to vlan1, vlan2, or more, you have 4 different naming schemes,
see documentation).
Once your logicial interfaces are created, you can see regular trafic
through them, 801.2q traffic being seen through native interface (eth0).
Then you only have to provide routing and filtering between your
interfaces and you're done.
If you feel brave, you can use interface bonding to provide your trunk
additionnal bandwidth or high availibility feature.
That was what I wanted to do. It was less problematic than I believed it
was. I have read some documentation about the 8021q module for the
kernel and now it all seams clearer.
Thanks for your help.
--
Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
jkerouac@bgsec.com
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÃA
The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"
