Re: Intel 82574 issue reported on Slashdot
On Fri, 2013-02-08 at 10:16 -0800, Jack Vogel wrote: For those that may have run across the story on Slashdot about this NIC, here is our statement: Recently there were a few stories published, based on a blog post by an end-user, suggesting specific network packets may cause the Intel® 82574L Gigabit Ethernet Controller to become unresponsive until corrected by a full platform power cycle. Intel was made aware of this issue in September 2012 by the blogs author. Intel worked with the author as well as the original motherboard manufacturer to investigate and determine root cause. Intel root caused the issue to the specific vendor’s mother board design where an incorrect EEPROM image was programmed during manufacturing. We communicated the findings and recommended corrections to the motherboard manufacturer. It is Intel’s belief that this is an implementation issue isolated to a specific manufacturer, not a design problem with the Intel 82574L Gigabit Ethernet controller. Intel has not observed this issue with any implementations which follow Intel’s published design guidelines. Intel recommends contacting your motherboard manufacturer if you have continued concerns or questions whether your products are impacted. Here is the link: http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement Any questions or concerns may be sent to me. Cheers, Jack Thanks for the info. I'm sure there were some *interesting* debugging sessions during this. Sean ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
In all honesty.. The blog post (and your email) are basically information free, they don't name names and provide no script or downloadable code that will allow end users to check if they are affected. A link with a little bit more information: http://blog.krisk.org/2013/02/packets-of-death.html Daniel O'Connor software and network engineer --Johnny ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
On 09/02/2013, at 20:42, Parv p...@pair.com wrote: Contact your motherboard manufacturer is much more time consuming than Run sysctl... | grep foo | awk ... to see if your system is affected. Gift^WStraight from horse's mouth ... http://blog.krisk.org/2013/02/packets-of-death.html I've already read this. http://www.kriskinc.com/intel-pod I'd really rather a test which reads the EEPROM and tells me if it's a problem rather than hang the interface on a machine :) In any case that isn't the point - this may be a vendor issue but it reflects poorly on Intel that they didn't take proper ownership of the issue. It would be far, far better for their image to say some systems may have the fault, go to http:// to find a way to test for your operating system. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
Am 02/09/13 09:15, schrieb Johnny Eriksson: In all honesty.. The blog post (and your email) are basically information free, they don't name names and provide no script or downloadable code that will allow end users to check if they are affected. A link with a little bit more information: http://blog.krisk.org/2013/02/packets-of-death.html Daniel O'Connor software and network engineer --Johnny We don't even have the tool tcpreplay in the ports mentioned in that BLOG. oh signature.asc Description: OpenPGP digital signature
Re: Intel 82574 issue reported on Slashdot
in message a18965a6-8d17-4919-9947-fe43d2503...@gsoft.com.au, wrote Daniel O'Connor thusly... On 09/02/2013, at 4:46, Jack Vogel jfvo...@gmail.com wrote: recommends contacting your motherboard manufacturer if you have continued concerns or questions whether your products are impacted. Here is the link: http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement Any questions or concerns may be sent to me. In all honesty.. The blog post (and your email) are basically information free, they don't name names and provide no script or downloadable code that will allow end users to check if they are affected. Contact your motherboard manufacturer is much more time consuming than Run sysctl... | grep foo | awk ... to see if your system is affected. Gift^WStraight from horse's mouth ... http://blog.krisk.org/2013/02/packets-of-death.html http://www.kriskinc.com/intel-pod - parv -- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
## O. Hartmann (ohart...@zedat.fu-berlin.de): We don't even have the tool tcpreplay in the ports mentioned in that BLOG. It's in net-mgmt/tcpreplay. Regards, Christoph -- Spare Space ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
On Sat, Feb 9, 2013 at 3:44 PM, Christoph Moench-Tegeder c...@burggraben.net wrote: ## O. Hartmann (ohart...@zedat.fu-berlin.de): We don't even have the tool tcpreplay in the ports mentioned in that BLOG. It's in net-mgmt/tcpreplay. And I managed to build mentioned Ostinato packet crafting utility with no problem on my FreeBSD 9.1-RELEASE AMD64. If they provide package and release (which I already asked from the authors) I will make a port for this tool as well :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
On 02/09/13 09:15, Johnny Eriksson wrote: In all honesty.. The blog post (and your email) are basically information free, they don't name names and provide no script or downloadable code that will allow end users to check if they are affected. A link with a little bit more information: http://blog.krisk.org/2013/02/packets-of-death.html Daniel O'Connor software and network engineer --Johnny ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Did anyone check to see if the Intel announcement had a 2 at 0x47f? :) I do have a machine with these controllers that had a bridge hang in a very odd fashion a while back, but it didn't repeat. It wasn't a SuperMicro board, which is what some posters were saying were affected. I would imagine a large ping packet (as used to test MTU) should inoculate any affected interface if issued at boot, I don't think our padding lines up with the problem. Once an interface sees a packet with anything else at 0x47f, it's no longer affected, so there's a narrow window of vulnerability in affected NICs. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
On Sat, Feb 9, 2013 at 4:25 PM, CeDeROM cede...@tlen.pl wrote: On Sat, Feb 9, 2013 at 3:44 PM, Christoph Moench-Tegeder c...@burggraben.net wrote: ## O. Hartmann (ohart...@zedat.fu-berlin.de): We don't even have the tool tcpreplay in the ports mentioned in that BLOG. It's in net-mgmt/tcpreplay. And I managed to build mentioned Ostinato packet crafting utility with no problem on my FreeBSD 9.1-RELEASE AMD64. If they provide package and release (which I already asked from the authors) I will make a port for this tool as well :-) There it goes http://www.freebsd.org/cgi/query-pr.cgi?pr=175993 have fun! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
On 09/02/2013, at 4:46, Jack Vogel jfvo...@gmail.com wrote: recommends contacting your motherboard manufacturer if you have continued concerns or questions whether your products are impacted. Here is the link: http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement Any questions or concerns may be sent to me. In all honesty.. The blog post (and your email) are basically information free, they don't name names and provide no script or downloadable code that will allow end users to check if they are affected. Contact your motherboard manufacturer is much more time consuming than Run sysctl... | grep foo | awk ... to see if your system is affected. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
