> Miskell, Craig wrote:
> >>
> >> ls centos supporting vlan setup?
> > If by that you mean 802.1q trunking, then yes.
> >
> >> ls it reliable?
> > Seems to be in my experience, but that's only limited so far.
> >
> >> how can I do it?
> > Create multiple ifcfg files in
> /etc/sysconfig/network-scripts, e.g. for
> > multiple VLANs on eth0:
> > ifcfg-eth0
> > ifcfg-eth0.2
> > ifcfg-eth0.100
> >
> > The number after the decimal is the VLAN id (default (1), 2 and 100
> > respectively above). In each file, add VLAN=yes. And
> don't forget to
> > turn on trunking on the switch to which you're attached.
> The network
> > startup scripts will then do the right thing.
>
> Are the details documented somewhere?
Yep: /usr/share/doc/initscripts-<yourversion>/sysconfig.txt
> Is vlan 1 always native
> (untagged) or can you specify that? I remember having some
> problem with
> Intel NICs on windows not liking native packets at all if any were
> tagged but I don't know if that was a hardware or software issue.
I'm not sure about the vlan 1/untagged nature; it "just worked" here,
and might have something to do with the configuration of the switch
you're connecting to.
Craig
=======================================================================
Attention: The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the
sender immediately.
=======================================================================
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
