Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com]
Sent: Tuesday, October 27, 2009 6:11 PM
To: NT System Admin Issues
Subject: VLAN concepts and applications
Someone was asking VLAN questions, so I decided to re-post this.
I've also updated it to reflect our successfu
o: NT System Admin Issues
Subject: Re: VLAN concepts and applications
This is a great piece of information.
Thank You Ben..
On Tue, Oct 27, 2009 at 9:11 PM, Ben Scott wrote:
Someone was asking VLAN questions, so I decided to re-post this.
I've also updated it to reflect our successful VoIP
This is a great piece of information.
Thank You Ben..
On Tue, Oct 27, 2009 at 9:11 PM, Ben Scott wrote:
> Someone was asking VLAN questions, so I decided to re-post this.
> I've also updated it to reflect our successful VoIP deployment.
>
> PROTOCOL CONCEPTS
>
> We have regular "untagged" Eth
Someone was asking VLAN questions, so I decided to re-post this.
I've also updated it to reflect our successful VoIP deployment.
PROTOCOL CONCEPTS
We have regular "untagged" Ethernet frames. ("Frame" is the
data-link (layer 2) term for what some protocols calls a "packet" or
"datagram".) Th
On Wed, Dec 10, 2008 at 2:31 PM, Matthew W. Ross
<[EMAIL PROTECTED]> wrote:
> What VPN software do you use for your laptop users over the 802.11?
OpenVPN. (http://www.openvpn.net/). Free, Open Source. It's based
on OpenSSL, and has been heavily audited and reviewed by numerous
experts, so I'm
Subject: Re: VLAN concepts and applications
> On Wed, Dec 10, 2008 at 11:11 AM, <[EMAIL PROTECTED]> wrote:
> > The only thing we really do differently is our Access Points are Vlan
> > aware, so we tie the SSID to a vlan. ... Eliminates the extra VPN step.
>
>
On Wed, Dec 10, 2008 at 11:11 AM, <[EMAIL PROTECTED]> wrote:
> The only thing we really do differently is our Access Points are Vlan
> aware, so we tie the SSID to a vlan. ... Eliminates the extra VPN step.
There have been so many vulnerabilities and problems with the
various 802.11 security p
On Wed, Dec 10, 2008 at 10:13 AM, Andy Ognenoff <[EMAIL PROTECTED]> wrote:
> Nice explanation - can I ask what firewall you use with this setup?
A commodity PC running Linux. Linux has native VLAN support in the
kernel, so we just get more network interfaces. Linux also has strong
firewall cap
me of our junior techs who are
not fully up on VLAN technology yet.
Thanks
Greg
-Original Message-
From: Andy Ognenoff [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 10:14 AM
To: NT System Admin Issues
Subject: RE: VLAN concepts and applications
Nice explanation - can I ask
Agreed, thanks. This is has always been one of my cloudy areas.
-Original Message-
From: Sean Rector [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 9:47 AM
To: NT System Admin Issues
Subject: RE: VLAN concepts and applications
Thanks for taking the time to write this
Thanks for taking the time to write this up - it's very informative to a
VLAN novice.
Sean Rector, MCSE
-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 8:39 PM
To: NT System Admin Issues
Subject: VLAN concepts and applications
So
Thanks for taking the time to put this explanation together, and for
posting it for all of us!
Kim
-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 7:39 PM
To: NT System Admin Issues
Subject: VLAN concepts and applications
Someone asked me
9 PM
>To: NT System Admin Issues
>Subject: VLAN concepts and applications
>
> Someone asked me off-list for an explanation of some VLAN stuff.
>They agreed to let me post my response to the list, for discussion,
>review, etc. If anyone has corrections/additions/etc., please
>
Someone asked me off-list for an explanation of some VLAN stuff.
They agreed to let me post my response to the list, for discussion,
review, etc. If anyone has corrections/additions/etc., please
contribute.
PROTOCOL CONCEPTS
We have regular "untagged" Ethernet frames. ("Frame" is the
data-l
14 matches
Mail list logo
