Re: Intel 82574 issue reported on Slashdot

2013-02-11 Thread Sean Bruno
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Ā®

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread 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:

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread Daniel O'Connor
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

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread O. Hartmann
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:

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread Parv
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.

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread Christoph Moench-Tegeder
## 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

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread CeDeROM
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

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread matt
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:

Re: Intel 82574 issue reported on Slashdot

2013-02-09 Thread CeDeROM
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

Re: Intel 82574 issue reported on Slashdot

2013-02-08 Thread Daniel O'Connor
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: