From owner-freebsd-current@FreeBSD.ORG Tue Mar 10 23:19:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46A8A106566B for ; Tue, 10 Mar 2009 23:19:29 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 2AA1B8FC0C for ; Tue, 10 Mar 2009 23:19:29 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [172.17.2.19] (jn@stealth.jnielsen.net [74.218.226.254]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id n2AN6UVD021366; Tue, 10 Mar 2009 19:06:31 -0400 (EDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-current@freebsd.org Date: Tue, 10 Mar 2009 18:50:51 -0400 User-Agent: KMail/1.9.10 References: <200903101651.08381.lists@jnielsen.net> <49B6DBD2.3030006@protected-networks.net> In-Reply-To: <49B6DBD2.3030006@protected-networks.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903101850.52239.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Michael Butler Subject: Re: IPv6 in -CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 10 Mar 2009 23:19:29 -0000 On Tuesday 10 March 2009 05:29:54 pm Michael Butler wrote: > John Nielsen wrote: > > I'm trying to set up a server running yesterday's -CURRENT as an IPv6 > > router for the local network using a tunnel broker. The handbook and > > other howto documentation I've found seem pretty consistent on the > > necessary steps, but I'm not having any luck. Any time I try to ping6 > > anything I get "ping6: sendmsg: No buffer space available". That and > > the fact that I never see any packets out my external interface > > destined for my broker's tunnel IP make me believe that something is > > broken locally. > > Since this is an IPv6 over IPv4 tunnel, you also have to let the IPv4 > packets out to the tunnel-broker (and back). Check your IPv4 firewall > rules, Thanks! That's the something obvious I was overlooking. I'm used to seeing "permission denied" errors or similar when it's the local firewall. Packets may or may not have been getting to the tunnel broker but ipfw is integrated 6/4 now and my custom ruleset didn't have any ip6 allow rules. Seems to be working now. :) JN