Hi all
ls centos supporting vlan setup?
ls it reliable?
how can I do it?
Thank you
--------------------------------- Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail
Hi all
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.
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. =======================================================================
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? 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.
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. =======================================================================
Les Mikesell wrote:
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.
its my understanding that if you're using vlan tagging on a given link, ALL packets are supposed to be tagged, as the tag is a prefix on the ethernet header. mixing tagged and untagged packets would be very messy.
John R Pierce wrote:
Les Mikesell wrote:
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.
its my understanding that if you're using vlan tagging on a given link, ALL packets are supposed to be tagged, as the tag is a prefix on the ethernet header. mixing tagged and untagged packets would be very messy.
No, 802.1q has a concept of 'native' packets being assigned to a specified single vlan. This has to be understood by each interface that can be configured as a trunk. I just couldn't get the Intel windows proset driver to do it - but that was several years ago.
thank you so much
few questions also
1/ what is different between vconfig and your configure to set it up the vlan?
2/ what is the different vlan and vlan trunking?
thank you again
"Miskell, Craig" Craig.Miskell@agresearch.co.nz wrote:
Hi all
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.
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@centos.org http://lists.centos.org/mailman/listinfo/centos
--------------------------------- Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail
few questions also
1/ what is different between vconfig and your configure to set it up the vlan?
Using the scripts in /etc/sysconfig/network-scripts will use vconfig for you.
2/ what is the different vlan and vlan trunking?
I'm not sure I understand the question, but I'll try and explain something. VLAN trunking is when you have multiple VLANs traversing a physical link, such as between two switches, or in your case (I think), between a switch and a server which you want to have multiple interfaces on (in various VLANs). Each ethernet frame is tagged with the VLAN id, which the receiving end uses to decide what VLAN the frame should be forwarded too.
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. =======================================================================
-
chloe K -
John R Pierce -
Les Mikesell -
Miskell, Craig