> 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
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
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
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
W dniu 2013-02-09 13:17, O. Hartmann pisze:
We don't even have the tool tcpreplay in the ports mentioned in that
BLOG. oh
base2[/usr/ports]# make search name=tcpreplay
Port: tcpreplay-3.4.4
Path: /usr/ports/net-mgmt/tcpreplay
Info: A tool to replay saved packet capture files
Maint: eha
Hi!
> We don't even have the tool tcpreplay in the ports mentioned in that BLOG.
net-mgmt/tcpreplay is not the same ?
--
p...@opsec.eu+49 171 3101372 7 years to go !
___
freebsd-net@freebsd.org mailing list
http://l
On 2/7/13 12:04 PM, George Neville-Neil wrote:
On Feb 6, 2013, at 12:28 , Alfred Perlstein wrote:
On 2/6/13 4:46 AM, John Baldwin wrote:
On Wednesday, February 06, 2013 6:27:04 am Randall Stewart wrote:
John:
A burst at line rate will *often* cause drops. This is because
router queues are a
Vencat,
There's been a breakdown in communication. I've been working on oce with Adam
and have a bunch of oce hardware. Please cc me on any patches you have. (pr's
are fine, but they won't get my attention)
Thanks,
Josh Paetzel
On Feb 7, 2013, at 3:57 AM, "Duvvuru,Venkat Kumar"
wrote:
> Hi
There's likely something wrong hardware wise. Either with that nic, the cable,
or the port you are plugging it into. The NIC is (correctly) not
autonegotiating 1000TX full duplex for some reason, and when you try to force
it it doesn't work.
Thanks,
Josh Paetzel
On Feb 7, 2013, at 3:53 PM,
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 2013-Feb-07 15:13:27 -0800, "Ronald F. Guilmette"
wrote:
>I just aquired a brand new chepie gigabit PCI ethernet card off eBay.
>The main chip on it appears to be an RTL8110S-32.
...
>I've tried two different CAT6 cables, two different LAN ports on my E2000,
>and I've even tried the card in tw
I want to thank all of the various people who offered help, advice,
and suggestings regarding this problem. It's all really appreciated.
Since I first posted about this issue, I have diligently tried to
isolate/debug the problem. I swapped the card into a totally
different system, also running
On Sat, Feb 9, 2013 at 6:41 AM, Alfred Perlstein wrote:
> On 2/7/13 12:04 PM, George Neville-Neil wrote:
>>
>> On Feb 6, 2013, at 12:28 , Alfred Perlstein wrote:
>>
>>> On 2/6/13 4:46 AM, John Baldwin wrote:
On Wednesday, February 06, 2013 6:27:04 am Randall Stewart wrote:
>
> J
On Feb 10, 2013, at 6:05, Kevin Oberman wrote:
> One idea that popped into my head (and may be completely ridiculous,
> is to make its availability dependent on a kernel option and have
> warning in NOTES about it contravening normal and accepted practice
> and that it can cause serious problems b
14 matches
Mail list logo
