From owner-freebsd-current@FreeBSD.ORG Sat Feb 9 20:15:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CABDD27C; Sat, 9 Feb 2013 20:15:10 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by mx1.freebsd.org (Postfix) with ESMTP id A2F50147; Sat, 9 Feb 2013 20:15:10 +0000 (UTC) Received: by mail-pb0-f44.google.com with SMTP id wz12so201450pbc.3 for ; Sat, 09 Feb 2013 12:15:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RKvXNRPcYWKcuBPxy/tOz4M0k5dwUEKxXpNBJe++Awg=; b=dhYee/onyDLIJLYcOPJz3OXkExGwAUR1jD8lGWvOCbWYf8VbKdRWeeAJN6BRhKHO+6 78BCxEzBGpkFg8yD/cKNnuIKhUcrl0pyIA5aBgcODWDpm8FDsiPpLdujD2PTr42oNnKq UjyAMjIcFnWd0J1zCnqnT34SOBq8id841eZGx0PHN38eNTDG2iZSW+VzEJMfUBqtEYfp +reu1kPUch29ldk7iMIIKWPVJymlTM67SAYUbVFSq8ujLUSznw5RXJhs7+1DEDkt6hwm jcJe3KXOlkGC/a1WLNN+GBAntpuQDoG9RyWCdfqr0UAn+6sqdUIfdgKoM+ltm6RLUzp0 sTxQ== X-Received: by 10.66.81.231 with SMTP id d7mr28464986pay.27.1360434411550; Sat, 09 Feb 2013 10:26:51 -0800 (PST) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id xa2sm2155412pbc.23.2013.02.09.10.26.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 09 Feb 2013 10:26:50 -0800 (PST) Message-ID: <511694B0.4060805@gmail.com> Date: Sat, 09 Feb 2013 10:25:52 -0800 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130202 Thunderbird/17.0.2 MIME-Version: 1.0 To: Johnny Eriksson Subject: Re: Intel 82574 issue reported on Slashdot References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Net , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 20:15:10 -0000 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-unsubscribe@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