From: Ben Greear <greearb@candelatech.com>
To: Andrius Kasparavicius <andrius@andrius.org>
Cc: netdev@oss.sgi.com
Subject: Re: network interface cards native vlans support in linux kernel?
Date: Fri, 11 Jul 2003 10:11:57 -0700 [thread overview]
Message-ID: <3F0EEFDD.8050300@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307111754220.6646-100000@hl.kauneta.net>
Andrius Kasparavicius wrote:
> on vanilla linux kernel, eepro doesn't work, and with 1496 mtu, 8139too
> works with any mtu (and 1500).
>
> which is recommended to use, e100 or eepro100?
As I mentioned, the e100 (intel's driver) is the one I recommend.
eepro100 does not seem to be updated in the kernel anymore, though if you go figure
out how to install Becker's drivers, he may have it working with vlans
by now.
Ben
>
> Andrius.
>
> On Wed, 9 Jul 2003, Ben Greear wrote:
>
>
>>>is there any problems to include full vlans support?
>>
>>Intel's e100 driver (and all NICs supported by it) support vlans
>>fine, as do most of the GigE NICs. Tulip does not, last I hear, though
>>a work-around patch has been around forever. Realtek worked at one time,
>>not sure about now though...
>
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT 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:[~2003-07-11 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 15:19 network interface cards native vlans support in linux kernel? Andrius Kasparavicius
2003-07-09 15:28 ` Jeff Garzik
2003-09-11 14:57 ` Rask Ingemann Lambertsen
2003-10-22 12:06 ` Rask Ingemann Lambertsen
2003-10-22 17:01 ` Ben Greear
2003-11-12 19:48 ` Rask Ingemann Lambertsen
2003-07-09 17:15 ` Ben Greear
2003-07-09 19:12 ` Andrius Kasparavicius
2003-07-11 14:59 ` Andrius Kasparavicius
2003-07-11 17:11 ` Ben Greear [this message]
2003-07-11 17:18 ` Jeff Garzik
2003-07-11 17:25 ` Ben Greear
2003-07-09 15:33 Hen, Shmulik
2003-07-09 17:13 ` Ben Greear
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=3F0EEFDD.8050300@candelatech.com \
--to=greearb@candelatech.com \
--cc=andrius@andrius.org \
--cc=netdev@oss.sgi.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.