From: Narbik Kocharians (narbikk@gmail.com)
Date: Sun Jun 24 2007 - 19:37:23 ART
May be this will do the trick, as it tags the Native VLAN for egress traffic
"vlan dot1q tag native"?
On 6/13/07, Douglas M Todd, Jr <dtodd@partners.org> wrote:
>
> Hello:
>
> quick note...
>
> Benefit of having a native vlan:
>
> 1) switches use vlan 1 as the native vlan by default
> All untagged traffic is tagged using this vlan in the d1q header.
> 1a) Thus if you have tagged traffic which is correct, any untagged
> traffic would fall in this vlan (ie., catch all)
> 2) the native vlan only needs to be the same when you connect switch to
> switch. Thus when you configure a router to switch the native vlan for
> the router can be anything you want.
> 3) on a router
> a) encap dot1q vlan# native
> ie, encap dot1q 200 native
> 4) on a switch
> a) switchport trunk native vlan 200
>
> Netmasters class goes over native vlans very well. It's a good primer..
> http://www.netmasterclass.net/site/libpdf.php
>
>
> Irfan Siddiqui wrote:
> > Wonder if someone can advise...
> >
> > What is the benefit of using a native vlan on a trunk. If you don't
> > define a native vlan on a trunk, I believe it uses vlan 1 as the native
> > vlan to pass the untag management traffic..
> >
> > If you do define a native vlan, it will use that vlan to pass all the
> > untagged traffic... and you need to match it on both ends...
> >
> > Also I believe there is a command to the effect that you can configure
> > native vlan to send tagged traffic as well.. dot1q tag native or
> > something....
> >
> >
> > But what is the benefit of configuring a native vlan vs . not
> > configuring one at all..
> >
> > Does it have any other benefit, besides specifying what vlan to send
> > untagged traffic ?
> >
> > Please help. Thanks in advance..
> >
> >
> > **********************************************************************
> > Any opinions expressed in the email are those of the individual and not
> necessarily the company. This email and any files transmitted with it are
> confidential and solely for the use of the intended recipient. If you are
> not the intended recipient or the person responsible for delivering it to
> the intended recipient, be advised that you have received this email in
> error and that any dissemination, distribution, copying or use is strictly
> prohibited.
> >
> > If you have received this email in error, or if you are concerned with
> the content of this email please e-mail to: e-security.support@vanco.info
> >
> > The contents of an attachment to this e-mail may contain software
> viruses which could damage your own computer system. While the sender has
> taken every reasonable precaution to minimise this risk, we cannot accept
> liability for any damage which you sustain as a result of software viruses.
> You should carry out your own virus checks before opening any attachments to
> this e-mail.
> >
> > Vanco UK Ltd Registered in England No: 2296733 Registered Office: John
> Busch House, 277 London Road, Isleworth, Middlesex TW7 5AX
> >
> > Please consider the environment before printing this e-mail
> > **********************************************************************
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
> The information transmitted in this electronic communication is intended
> only for the person or entity to whom 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 recipient is
> prohibited. If you received this information in error, please contact the
> Compliance HelpLine at 800-856-1983 and properly dispose of this
> information.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Narbik Kocharians CCIE# 12410 (R&S, SP, Security) CCSI# 30832
This archive was generated by hypermail 2.1.4 : Sun Jul 01 2007 - 17:24:51 ART