All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] VLAN patch
Date: Wed, 19 Dec 2001 21:40:52 +0000	[thread overview]
Message-ID: <marc-lartc-100879809222293@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100878327115353@msgid-missing>

On Wed, Dec 19, 2001 at 04:33:37PM -0500, Ryan wrote:
> I understand the use of VLANs on a switch, but is it only useful in Linux
> when your Linux computer is configured as a bridge?

No -- its quite useful for any situation where you might want to communicate
with specific VLANs on a network (or make them).  Feel free to consider having
the IP address of your Samba server on a VLAN address so that the network
traffic isn't 'visible' to other hosts and the workgroup doesn't show up in
everybody's Network Neighbourhood (for a fast example).

This would require (usually) using VLAN capable network cards on the Windows
machines of course.

> Where do you get the vconfig tool?

[scrolls down a little]

> >> I've just downloaded and started reading through the VLAN patch from
> >> http://sourceforge.net/projects/vlan/ ...

That should be enough info ... ;-)
-- 
Michael T. Babcock
CTO, FibreSpeed Ltd.     (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2001-12-19 21:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 17:33 [LARTC] VLAN patch Michael T. Babcock
2001-12-19 17:58 ` Jerome PETAZZONI
2001-12-19 21:33 ` Ryan
2001-12-19 21:40 ` Michael T. Babcock [this message]
2001-12-19 22:13 ` Henrik Nordstrom
2001-12-19 23:48 ` bert hubert
2001-12-20 10:45 ` Jerome Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-100879809222293@msgid-missing \
    --to=mbabcock@fibrespeed.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.