From owner-freebsd-net@FreeBSD.ORG Sun Oct 8 05:30:26 2006 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC70C16A403 for ; Sun, 8 Oct 2006 05:30:26 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97D2443D49 for ; Sun, 8 Oct 2006 05:30:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k985UQ8N074356 for ; Sun, 8 Oct 2006 05:30:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k985UQde074355; Sun, 8 Oct 2006 05:30:26 GMT (envelope-from gnats) Date: Sun, 8 Oct 2006 05:30:26 GMT Message-Id: <200610080530.k985UQde074355@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Astrodog Cc: Subject: Re: kern/95665: [if_tun] "ping: sendto: No buffer space available" with TUN interface (easily reproducable with test program) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Astrodog List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 05:30:26 -0000 The following reply was made to PR kern/95665; it has been noted by GNATS. From: Astrodog To: bug-followup@FreeBSD.org, johan@nocrew.org Cc: Subject: Re: kern/95665: [if_tun] "ping: sendto: No buffer space available" with TUN interface (easily reproducable with test program) Date: Sun, 8 Oct 2006 00:22:20 -0500 I can reproduce this problem with some ease. It occurs when the buffer for tun0 fills up, because the NIC is unable to send the packets as quickly as the program is generating them. This is fairly common on slow or dodgy NICs, when combined with tun/gif/etc. There is not a real fix, because the outgoing NIC used by tun can change, so any attempt to make it aware of the buffer, and throttle accordingly would be painfully hacked together. To confirm that this is actually the issue, increase the size of the buffer. You should see a larger number of packets make it through.