From owner-freebsd-net@FreeBSD.ORG Mon Jun 25 23:20:21 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 3CB0916A41F for ; Mon, 25 Jun 2007 23:20:21 +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 0539713C44B for ; Mon, 25 Jun 2007 23:20:20 +0000 (UTC) (envelope-from ecrist@secure-computing.net) Received: from [192.168.1.2] (unknown [209.240.66.157]) (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 7A11A1702D; Mon, 25 Jun 2007 18:20:20 -0500 (CDT) In-Reply-To: <468011FC.4050308@FreeBSD.org> References: <39D6F9D8-3A2C-4AD7-9FA4-0024E304194A@secure-computing.net> <468011FC.4050308@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7731B558-35C7-4E22-A40D-8BCE208AFD6A@secure-computing.net> Content-Transfer-Encoding: 7bit From: Eric F Crist Date: Mon, 25 Jun 2007 18:20:18 -0500 To: "Bruce M. Simpson" X-Mailer: Apple Mail (2.752.3) Cc: 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: Mon, 25 Jun 2007 23:20:21 -0000 On Jun 25, 2007, at 2:05 PMJun 25, 2007, Bruce M. Simpson wrote: > Is your routing table correct? My default route entry for IPv6 just > looks like this: > > default fe80::%gif0 > UGS gif0 > > and gif0 just looks like this: > > gif0: flags=8051 mtu 1280 > tunnel inet a.b.c.d -> x.x.x.x > inet6 fe80::XXX:XXX:XXXX%gif0 prefixlen 64 scopeid 0x8 > inet6 2001:ZZZ:ZZZ::ZZZZ:ZZZZ prefixlen 128 > > In the output you posted, the next-hop of 2001:4980:1::5 will need > to be resolved via NDP (hence the LW flags). > > You already have a 1:1 endpoint mapping due to the use of the gif > IPIP header, so the upstream shouldn't need any other tag to demux > your traffic. You shouldn't need to do anything special with > Ethernet in your configuration. > > Hope this helps. > > BMS > Bruce, My problem isn't getting out to 2001:4980:1::5, it's getting to my LAN, the 2001:4980:1:111::/64 network. My gateway, the machine from which I posted the routing and ifconfig information, is able to ping across the tunnel, and to the internet just fine. Nothing is able to get from the gateway to my LAN, however. Is it a problem with the fxp driver, or perhaps my setup with the ethernet bridging? Thanks again. ----- Eric F Crist Secure Computing Networks