From owner-freebsd-net@FreeBSD.ORG Tue Sep 25 00:01:57 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B18A1065672 for ; Tue, 25 Sep 2012 00:01:57 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id B3A898FC15 for ; Tue, 25 Sep 2012 00:01:56 +0000 (UTC) Received: by vbmv11 with SMTP id v11so8568846vbm.13 for ; Mon, 24 Sep 2012 17:01:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=97hV/U5IUm4SSFteS+LOg7R2muCtwrqn8ej8UmHVjQM=; b=tB94oecBEB0SkhqDRMPwff+mfqAf397rVh1/JcoPcmq4WWNB1FqG9g41LEwQ0Isfg7 +f5fnKA87rsJraED4KSz2KOvKFSspF72QYLcYhIPfMRpKyCn+SiXVs/v0tBvg408N7Du sdB1w4ETwKkiQcyHnWWv19gIXxkSf2sMxlLgNn85G7J3fAQPgWYRF5SZaDfMdL/FAiwd 4CojentIjKJmTltyw+CcZkZJNIzG5VLRJuHwOkljvHyWS4gI7PDMDBAhIusOVAJV9Cig j9jWe5AcsrkjKclTHN2HCgyValAa67fOywloqBLlph3MvSRrSAaeYK4eL6npFvDrD+K8 W65g== MIME-Version: 1.0 Received: by 10.221.13.202 with SMTP id pn10mr8234301vcb.57.1348531309673; Mon, 24 Sep 2012 17:01:49 -0700 (PDT) Received: by 10.58.207.114 with HTTP; Mon, 24 Sep 2012 17:01:49 -0700 (PDT) In-Reply-To: <5060884C.3050709@monkeybrains.net> References: <5060884C.3050709@monkeybrains.net> Date: Mon, 24 Sep 2012 20:01:49 -0400 Message-ID: From: Ryan Stone To: "Rudy (bulk)" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net Subject: Re: ping: sendto: No buffer space available X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2012 00:01:57 -0000 Can you get the output of netstat -I emX -d? You don't need to run that when the problem is happening -- you just need to run it on the machine after it exhibits the issue without any reboots in the interim. I suspect that you are seeing the em TX queue fill up. If so you should see output drops reported by the em interface.