From owner-freebsd-questions@FreeBSD.ORG  Mon May 28 20:01:50 2007
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 75B2F16A4D1
	for <freebsd-questions@freebsd.org>;
	Mon, 28 May 2007 20:01:50 +0000 (UTC)
	(envelope-from bounces@nabble.com)
Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158])
	by mx1.freebsd.org (Postfix) with ESMTP id 59DD313C487
	for <freebsd-questions@freebsd.org>;
	Mon, 28 May 2007 20:01:50 +0000 (UTC)
	(envelope-from bounces@nabble.com)
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bounces@nabble.com>) id 1HslPZ-0002T8-Ju
	for freebsd-questions@freebsd.org; Mon, 28 May 2007 13:01:49 -0700
Message-ID: <10841206.post@talk.nabble.com>
Date: Mon, 28 May 2007 13:01:49 -0700 (PDT)
From: Ofloo <bulk@ofloo.net>
To: freebsd-questions@freebsd.org
In-Reply-To: <10840247.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: bulk@ofloo.net
References: <10840247.post@talk.nabble.com>
Subject: Re: 6to4 IPv6 problems FreeBSD 6.2 p4
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2007 20:01:50 -0000




Ofloo wrote:
> 
> I use 6to4 IPv6 tunnels, when using applications which use a lot of
> bandwidth (400kb/s), it is not that much but still, the server gets in
> trouble.
> 
> May 28 19:51:21 narf kernel: arpresolve: can't allocate route for
> 192.88.99.1
> May 28 19:51:22 narf kernel: arpresolve: can't allocate route for
> 192.88.99.1
> May 28 20:06:15 narf kernel: arpresolve: can't allocate route for
> 192.88.99.1
> May 28 20:09:02 narf kernel: arpresolve: can't allocate route for
> 192.88.99.1
> 
> The default route does exist though:
> 
> narf# netstat -rn -f inet6 | grep default
> default                           2002:c058:6301::              UGS       
> stf0
> narf#
> 
> when this happens it takes about 10 mins and my ssh IPv6 ssh session is
> closed, after keeping this up for longer the server crashes, .. any
> suggestions ?
> 

Using a different default gateway solved this for now, though I don't think
a server should crash if its gateway is in trouble, ..
-- 
View this message in context: http://www.nabble.com/6to4-IPv6-problems-FreeBSD-6.2-p4-tf3829352.html#a10841206
Sent from the freebsd-questions mailing list archive at Nabble.com.