Re: [CentOS] VLAN support?
On Fri, Sep 30, 2011 at 5:39 PM, James A. Peltier jpelt...@sfu.ca wrote: - Original Message - | On Thu, Sep 29, 2011 at 5:35 PM, Michael Crilly mrcri...@gmail.com | wrote: | Not sure if someone has asked this previously, but have you got the | 8021q | kernel module installed and loaded? | | That seems to have happened by itself - and I now see that if the | NetworkManager service is not running the 5.x style ifcfg- files work | with ifup/ifdown. But I still haven't found the documentation | describing that requirement or what the new entries that might be in | the ifcfg-* files mean. | | -- | Les Mikesell | lesmikes...@gmail.com Yes, the 8021q module will load automatically when it sees any ifcfg-* entry that contains ifname.vlandid or for hosts with ifcfg-vlanid and the VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD. Below is the configuration that I use for my VLANs for KVM. # configure a bridge device for NAT VLAN support /etc/sysconfig/network-scripts/ifcfg-NAT DEVICE=NAT BOOTPROTO=none ONBOOT=yes TYPE=Bridge USERCTL=no IPV6INIT=no NM_CONTROLLED=no # configure a VLAN for NAT /etc/sysconfig/network-scripts/ifcfg-vlan303 VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD DEVICE=vlan303 PHYSDEV=em1 BOOTPROTO=none VLAN=yes ONBOOT=yes BRIDGE=NAT NM_CONTROLLED=no TYPE=Ethernet Is there a specific option that you are trying to get information on? I'm looking for documentation for all of the name/values that mean something in these files. Also, anything that relates to the new feature in 6.1 to refer to NICs by bios name conventions. I'd really like to find a way to configure machines when you know the physical NIC locations (card type/slot/port) but nothing else. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VLAN support?
On Thu, Sep 29, 2011 at 5:35 PM, Michael Crilly mrcri...@gmail.com wrote: Not sure if someone has asked this previously, but have you got the 8021q kernel module installed and loaded? That seems to have happened by itself - and I now see that if the NetworkManager service is not running the 5.x style ifcfg- files work with ifup/ifdown. But I still haven't found the documentation describing that requirement or what the new entries that might be in the ifcfg-* files mean. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VLAN support?
On Thu, 2011-09-29 at 14:15 -0500, Les Mikesell wrote: On Wed, Aug 3, 2011 at 11:12 PM, James A. Peltier jpelt...@sfu.ca wrote: | Are there any new tools in CentOS 6 to configure VLAN interfaces | (where | the switch passes multiple tagged VLANs over one physical link to the | host) or is it best to edit /etc/sysconfig/network-scripts/eth?.vlan# | files manually? | So far none that I've found. I use VLANs quite extensively so I'm stuck rolling it with kickstart/puppet or manually when testing. Where is the best place to find documentation on how to set them up manually? When I use the same ifcfg-eth#.vlan# configs as in 5.x, ifup gives me an error about 'Device not managed by NetworkManager' . Don't use NetworkManager, chkconfig NetworkManager off; chkconfig network on will do the trick. I don't know that Networkmanagr can handle tagged vlan interfaces ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VLAN support?
- Original Message - | On Thu, Sep 29, 2011 at 5:35 PM, Michael Crilly mrcri...@gmail.com | wrote: | Not sure if someone has asked this previously, but have you got the | 8021q | kernel module installed and loaded? | | That seems to have happened by itself - and I now see that if the | NetworkManager service is not running the 5.x style ifcfg- files work | with ifup/ifdown. But I still haven't found the documentation | describing that requirement or what the new entries that might be in | the ifcfg-* files mean. | | -- | Les Mikesell | lesmikes...@gmail.com Yes, the 8021q module will load automatically when it sees any ifcfg-* entry that contains ifname.vlandid or for hosts with ifcfg-vlanid and the VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD. Below is the configuration that I use for my VLANs for KVM. # configure a bridge device for NAT VLAN support /etc/sysconfig/network-scripts/ifcfg-NAT DEVICE=NAT BOOTPROTO=none ONBOOT=yes TYPE=Bridge USERCTL=no IPV6INIT=no NM_CONTROLLED=no # configure a VLAN for NAT /etc/sysconfig/network-scripts/ifcfg-vlan303 VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD DEVICE=vlan303 PHYSDEV=em1 BOOTPROTO=none VLAN=yes ONBOOT=yes BRIDGE=NAT NM_CONTROLLED=no TYPE=Ethernet Is there a specific option that you are trying to get information on? -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices http://blogs.sfu.ca/people/jpeltier I will do the best I can with the talent I have ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VLAN support?
On Wed, Aug 3, 2011 at 11:12 PM, James A. Peltier jpelt...@sfu.ca wrote: | Are there any new tools in CentOS 6 to configure VLAN interfaces | (where | the switch passes multiple tagged VLANs over one physical link to the | host) or is it best to edit /etc/sysconfig/network-scripts/eth?.vlan# | files manually? | So far none that I've found. I use VLANs quite extensively so I'm stuck rolling it with kickstart/puppet or manually when testing. Where is the best place to find documentation on how to set them up manually? When I use the same ifcfg-eth#.vlan# configs as in 5.x, ifup gives me an error about 'Device not managed by NetworkManager' . -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VLAN support?
Not sure if someone has asked this previously, but have you got the 8021q kernel module installed and loaded? On 29 September 2011 20:15, Les Mikesell lesmikes...@gmail.com wrote: On Wed, Aug 3, 2011 at 11:12 PM, James A. Peltier jpelt...@sfu.ca wrote: | Are there any new tools in CentOS 6 to configure VLAN interfaces | (where | the switch passes multiple tagged VLANs over one physical link to the | host) or is it best to edit /etc/sysconfig/network-scripts/eth?.vlan# | files manually? | So far none that I've found. I use VLANs quite extensively so I'm stuck rolling it with kickstart/puppet or manually when testing. Where is the best place to find documentation on how to set them up manually? When I use the same ifcfg-eth#.vlan# configs as in 5.x, ifup gives me an error about 'Device not managed by NetworkManager' . -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] VLAN support?
- Original Message - | Are there any new tools in CentOS 6 to configure VLAN interfaces | (where | the switch passes multiple tagged VLANs over one physical link to the | host) or is it best to edit /etc/sysconfig/network-scripts/eth?.vlan# | files manually? | | -- | Les Mikesell | lesmikes...@gmail.com So far none that I've found. I use VLANs quite extensively so I'm stuck rolling it with kickstart/puppet or manually when testing. -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices http://blogs.sfu.ca/people/jpeltier ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] vlan support
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
Re: [CentOS] vlan support
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. -- Les Mikesell [EMAIL PROTECTED] ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] vlan support
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 [EMAIL PROTECTED] 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 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] vlan support
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@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] vlan support
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. === ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vlan support
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. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vlan support
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. -- Les Mikesell [EMAIL PROTECTED] ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
