| 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
| ||
|
Message-ID: <47C459E1.1050803@intel.com> Date: Tue, 26 Feb 2008 10:26:41 -0800 From: "Kok, Auke" <auke-jan.h.kok@...el.com> To: Wolfgang Walter <wolfgang.walter@...dentenwerk.mhn.de> CC: netdev@...r.kernel.org Subject: Re: problems with e1000 and flow control Wolfgang Walter wrote: > Hello, > > it seems that e1000 enables flow-control (rx pause frames) even if the switch > does not advertise flow control. This seems to get a problem as (at least > some) switches then forward pause frames directed to the card from other > hosts. We think there are hosts which indeed do this in the lans of our > student halls. > > I think flow control should be completely disabled by default if the switch > does not advertise it. It still can be forced with ethtool. Are you sure that the switch actually advertises the flow control "disabled" setting properly? Perhaps you can include the e1000 ethtool flow control settings and dmesg output (2.6.24 will print out FC status when link comes up). There's a lengthy argumentation including spec references in the e1000/e1000e driver code on how FC is handled (look for "IEEE 802.3ab"). Can you take a look at that and see what might be happening? Changing this behaviour might give other people issues which is something we need to be very cautious about, obviously :) Cheers, Auke -- 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
Powered by blists - more mailing lists