From: Ben Greear <greearb@candelatech.com>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: Andrius Kasparavicius <andrius@andrius.org>, netdev@oss.sgi.com
Subject: Re: network interface cards native vlans support in linux kernel?
Date: Wed, 09 Jul 2003 10:13:11 -0700 [thread overview]
Message-ID: <3F0C4D27.20907@candelatech.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A014C93B9@hasmsx403.iil.intel.com>
Hen, Shmulik wrote:
> Do you mean "native" as in hardware acceleration offloading?
> If that's the case than the 8021q vlan module handshakes with the device driver to check for support and that's it. No need to do any settings on the device. In case there is no offloading support, the vlan module will take care of all stripping/inserting of the vlan tag into place.
> On the other hand, if the device cannot handle 1504 byte packets, it defines itself as "vlan challenged" and you can't use vlan on it at all.
Even challenged ones can work if you set your MTU (and all peer MTUs) to 4 less than normal,
ie 1496.
Ben
>
>
--
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-09 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 15:33 network interface cards native vlans support in linux kernel? Hen, Shmulik
2003-07-09 17:13 ` Ben Greear [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 15:19 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
2003-07-11 17:18 ` Jeff Garzik
2003-07-11 17:25 ` 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=3F0C4D27.20907@candelatech.com \
--to=greearb@candelatech.com \
--cc=andrius@andrius.org \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@intel.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.