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®
On Sat, Feb 9, 2013 at 4:25 PM, CeDeROM wrote:
> On Sat, Feb 9, 2013 at 3:44 PM, Christoph Moench-Tegeder
> 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 bu
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
On Sat, Feb 9, 2013 at 3:44 PM, Christoph Moench-Tegeder
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 pro
## 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
in message ,
wrote Daniel O'Connor thusly...
>
>
> On 09/02/2013, at 4:46, Jack Vogel 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/com
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 inform
On 09/02/2013, at 20:42, Parv 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
> 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-d
On 09/02/2013, at 4:46, Jack Vogel 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-co
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
11 matches
Mail list logo
