From: Ben Greear <greearb@candelatech.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: "Peter C. Norton" <spacey@lenin.nu>,
Sander Steffann <steffann@nederland.net>,
vlan@Scry.WANfear.com, linux-kernel@vger.kernel.org,
Holger Kiehl <Holger.Kiehl@dwd.de>,
"David S. Miller" <davem@redhat.com>, Lennert <buytenh@gnu.org>,
Gleb Natapov <gleb@nbase.co.il>
Subject: Re: [VLAN] Should VLANs be devices or something else?
Date: Thu, 21 Jun 2001 23:36:43 -0700 [thread overview]
Message-ID: <3B32E77B.8102DA15@candelatech.com> (raw)
In-Reply-To: <200106220627.f5M6RSF415308@saturn.cs.uml.edu>
"Albert D. Cahalan" wrote:
>
> > Should VLANs be devices or some other thing?
>
> What is good for PPP-over-Ethernet is good for VLANs,
> which are basically Ethernet-over-Ethernet.
So, um, for those fortunate enough not to need PPPoE, are they
devices or what?
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-06-22 6:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 8:19 VLAN in kernel? Holger Kiehl
2001-06-19 22:11 ` Should VLANs be devices or something else? Ben Greear
2001-06-19 22:45 ` Dax Kelson
2001-06-19 22:49 ` David S. Miller
2001-06-19 22:52 ` Dax Kelson
2001-06-19 23:16 ` Ben Greear
2001-06-20 0:31 ` Marcell Gal
2001-06-20 1:24 ` [VLAN] " Ben Greear
2001-06-20 8:10 ` Eran Man
2001-06-20 9:32 ` Gleb Natapov
2001-06-20 7:21 ` [VLAN] " Sander Steffann
2001-06-22 6:12 ` Peter C. Norton
2001-06-22 6:27 ` Albert D. Cahalan
2001-06-22 6:36 ` Ben Greear [this message]
2001-06-21 22:10 ` [Vlan-devel] " Guy Van Den Bergh
2001-06-21 22:54 ` Ben Greear
2001-06-22 15:00 ` Matthias Welwarsky
2001-06-22 15:46 ` Chris Wedgwood
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=3B32E77B.8102DA15@candelatech.com \
--to=greearb@candelatech.com \
--cc=Holger.Kiehl@dwd.de \
--cc=acahalan@cs.uml.edu \
--cc=buytenh@gnu.org \
--cc=davem@redhat.com \
--cc=gleb@nbase.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=spacey@lenin.nu \
--cc=steffann@nederland.net \
--cc=vlan@Scry.WANfear.com \
/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.