From owner-freebsd-questions@FreeBSD.ORG Sun Sep 25 07:38:57 2005 Return-Path: X-Original-To: freebsd-questions@FreeBSD.org Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DCA816A421 for ; Sun, 25 Sep 2005 07:38:57 +0000 (GMT) (envelope-from arved@arved.at) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70A8643D58 for ; Sun, 25 Sep 2005 07:38:55 +0000 (GMT) (envelope-from arved@arved.at) Received: from [192.168.1.24] (ische.arved.de [192.168.1.24]) by 21322530218.direct.eti.at (8.13.3/8.13.3) with ESMTP id j8P7csF1081497 for ; Sun, 25 Sep 2005 09:38:54 +0200 (CEST) (envelope-from arved@arved.at) Mime-Version: 1.0 (Apple Message framework v623) In-Reply-To: <200509241832.05620.aksis@idea-anvil.net> References: <1b62a73905092313082d48e984@mail.gmail.com> <200509240433.22883.aksis@idea-anvil.net> <1b62a7390509241448119ab257@mail.gmail.com> <200509241832.05620.aksis@idea-anvil.net> X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2a54ea6ed815ca4875cda54d474c8389@arved.at> Content-Transfer-Encoding: 7bit From: Tilman Linneweh Date: Sun, 25 Sep 2005 09:38:51 +0200 To: freebsd-questions@FreeBSD.org X-Mailer: Apple Mail (2.623) Cc: Subject: Re: New user getting very discouraged with IPv6 problems, cannot get tunnel working completely :( X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Sep 2005 07:38:57 -0000 Am 25.09.2005 um 03:32 schrieb aksis: > On the HE site, after you login, in the Tunnel Details section, there > is an > option to "rebuild" the tunnel, this might fix the problem. Beyond > that I > would email HE, send them the relative info and ask them to look at it. > Additional check your ipv6 routing table that everything is correct. (e.g. the tspc program is not running and messing with your routingtable) Check with tcpdump/ethereal that the ping packets are leaving your site correctly. regards arved