netdev - Re: change the way e1000 is handling short VLAN frames

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Sep 2007 17:29:47 -0400
From:	jamal <hadi@...erus.ca>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
Cc:	Ben Greear <greearb@...delatech.com>,
	Emil Micek <emil.micek@...jasek.cz>,
	netdev mailing list <netdev@...r.kernel.org>,
	Jesse <jesse.brandeburg@...el.com>
Subject: Re: change the way e1000 is handling short VLAN frames

On Fri, 2007-21-09 at 14:18 -0700, Ben Greear wrote:

> As for using the software stack, I don't think we are padding to 68 in
> the soft vlans either...

Should be much easier than changing firmware or an ASIC.

> It would be nice to have an ethtool to turn off hw vlans for other reasons,
> like sniffing vlan tags, at least...

Hrm, no hardware out there will pass on tags to the stack as metadata?

On Fri, 2007-21-09 at 14:21 -0700, Kok, Auke wrote:

> I don't actually see the "SHOULD" part you are referring to. 

the "optional" part;-> MAY?

> AFAIK the RX side is fully covered 

so you can handle both 64B and 68B?

> and only on TX the hardware sends out 64b padded vlan packets, which
> is permitted. The spec never says that it is required to send out 68b padded vlan
> packets - only permits either choice.

The CISCO i pointed to seems to be only capable of 68B. So if the CISCO
sends to you, it would work, but you sending to the CISCO or to Emil's
CMTS you have challenges, no?


cheers,
jamal

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html