From owner-freebsd-net@FreeBSD.ORG Fri Jun 29 12:12:56 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 005A116A41F; Fri, 29 Jun 2007 12:12:55 +0000 (UTC) (envelope-from ecrist@secure-computing.net) Received: from snipe.secure-computing.net (snipe.secure-computing.net [209.240.66.149]) by mx1.freebsd.org (Postfix) with ESMTP id BF17E13C46C; Fri, 29 Jun 2007 12:12:55 +0000 (UTC) (envelope-from ecrist@secure-computing.net) Received: from [10.0.0.14] (unknown [74.95.66.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ecrist@secure-computing.net) by snipe.secure-computing.net (Postfix) with ESMTP id B914A1702D; Fri, 29 Jun 2007 07:12:54 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: References: <39D6F9D8-3A2C-4AD7-9FA4-0024E304194A@secure-computing.net> <468011FC.4050308@FreeBSD.org> <7731B558-35C7-4E22-A40D-8BCE208AFD6A@secure-computing.net> <468063F6.2050303@FreeBSD.org> <8AA398FC-A753-4BB8-A93F-224FDDCE41BA@secure-computing.net> <46818609.3080202@freebsd.org> <4681AA8D.8050009@freebsd.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <88EDD0D7-B5C9-4DA7-B27C-CAE662CDFA36@secure-computing.net> Content-Transfer-Encoding: 7bit From: Eric F Crist Date: Fri, 29 Jun 2007 07:12:53 -0500 X-Mailer: Apple Mail (2.752.3) Cc: "Bruce A. Mah" , "Bruce M. Simpson" , freebsd-net@freebsd.org Subject: Re: IPv6 Woes... 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: Fri, 29 Jun 2007 12:12:56 -0000 [cut it out] I just wanted everyone to know that my IPv6 Woes have been resolved. As it turns out, there a couple of things that were killing my setup. First, I had fat-fingered the IP6 alias on my gateway - works great there. Secondly, my ISP fat-fingered the network address for my subnet in their routing tables. Third, and last, there is (still) a routing problem on the high-level at Verizon/Alter/UUnet that has yet to be resolved. Thanks a lot for all your help! ----- Eric F Crist Secure Computing Networks