From owner-freebsd-net@FreeBSD.ORG Mon Jun 25 19:05:34 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 6C59416A47C for ; Mon, 25 Jun 2007 19:05:34 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 441C313C465 for ; Mon, 25 Jun 2007 19:05:34 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id C303B19EC; Mon, 25 Jun 2007 15:05:33 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Mon, 25 Jun 2007 15:05:33 -0400 X-Sasl-enc: Xr/qqFTZWJ+krzHcTbWLDUZ4JqkIeYaT0emxDB8Au8Rx 1182798333 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 41A7F14201; Mon, 25 Jun 2007 15:05:33 -0400 (EDT) Message-ID: <468011FC.4050308@FreeBSD.org> Date: Mon, 25 Jun 2007 20:05:32 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (X11/20070407) MIME-Version: 1.0 To: Eric F Crist References: <39D6F9D8-3A2C-4AD7-9FA4-0024E304194A@secure-computing.net> In-Reply-To: <39D6F9D8-3A2C-4AD7-9FA4-0024E304194A@secure-computing.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 19:05:34 -0000 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