[nSLUG] nSLUG Digest, Vol 572, Issue 1

chris thompson ct8ball at gmail.com
Fri May 29 21:24:39 ADT 2015


Thanks for the responses guys, the bad news is that the thing ate it this
morning... but the good news, we are now sourcing a new 48 port(Cisco)
hurray!

On Fri, May 29, 2015 at 11:55 AM <nslug-request at nslug.ns.ca> wrote:

> Send nSLUG mailing list submissions to
>         nslug at nslug.ns.ca
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://nslug.ns.ca/mailman/listinfo/nslug
> or, via email, send a message with subject or body 'help' to
>         nslug-request at nslug.ns.ca
>
> You can reach the person managing the list at
>         nslug-owner at nslug.ns.ca
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of nSLUG digest..."
>
>
> Today's Topics:
>
>    1. Re:  Ranting / VLAN Tagging (Stephen Gregory)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 28 May 2015 13:51:00 -0400
> From: Stephen Gregory <nslug at kernelpanic.ca>
> To: Nova Scotia Linux User Group <nslug at nslug.ns.ca>
> Subject: Re: [nSLUG] Ranting / VLAN Tagging
> Message-ID:
>         <CAJ5K_5rF+rA3aZjTZq+NQbdjYyXMj=
> MyPNnf_MC0WfspDpSXHQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, May 28, 2015 at 9:10 AM, chris thompson <ct8ball at gmail.com> wrote:
> > So I'm fighting my way through configuring VLAN tagging on various
> > equipment,
>
> > if you kind folks could provide any type of insight I would be greatly
> > appreciated.
>
> On every switch I have configured a port can pass both tagged VLANS,
> and one untagged VLAN. The untagged vlan usually has a name like
> default. On some gear vlan 1 is always enabled as untagged on all
> tagged ports unless another untagged port is configured. (Cisco
> Catalyst 2900 stuff had this limitation.) The standard practice is/was
> to not use vlan 1 by explicitly configuring all ports to use a
> different vlan or vlans
>
> So:
> configure port 12 for vlan 200 untagged (aka default or access vlan).
> configure port 18 for vlan 250 tagged.
> test ping from port 12 to port 18
>
> the expected result is untagged traffic on port 12 should not go to port
> 18.
>
> then:
> configure port 12 for vlan 250 untagged
> configure port 18 for vlan 250 tagged
> test ping from port 12 to port 18
>
> the expected result is tagged vlan 250 traffic should appear on port 18.
> Unless your server on port 18 is configured for vlan 250 your server
> will no respond to the ping, but tcpdump / wireshark should see the
> traffic.
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> nSLUG mailing list
> nSLUG at nslug.ns.ca
> http://nslug.ns.ca/mailman/listinfo/nslug
>
>
> ------------------------------
>
> End of nSLUG Digest, Vol 572, Issue 1
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nslug.ns.ca/pipermail/nslug/attachments/20150530/d1a684ee/attachment.html>


More information about the nSLUG mailing list