0069CC5.6060908@???>
<50069FDB.2060801@???>
In-Reply-To: <50069FDB.2060801@???>
Date: Wed, 18 Jul 2012 12:40:33 +0100
Message-ID: <58BCEC96A4FD4061BC4058B38AE56182@???>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ac1k2bFdEZAJUUnUQT6GI1lPATB/vwAAD9Mg
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
X-Virus-Scanned: clamav-milter 0.97.3 at tegan.project76.net
X-Virus-Status: Clean
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Wed,
18 Jul 2012 11:40:39 +0000
X-SA-Exim-Connect-IP: 2001:ba8:1f1:f1ac::2
X-SA-Exim-Mail-From: js41@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
spamd0.lon.bitfolk.com
X-Spam-Level: **
X-Spam-ASN:
X-Spam-Status: No, score=2.7 required=5.0 tests=DOS_OUTLOOK_TO_MX,
FSL_HELO_NON_FQDN_1,
RDNS_NONE shortcircuit=no autolearn=disabled version=3.3.1
X-Spam-Report: * 0.0 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1
* 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
* 1.4 DOS_OUTLOOK_TO_MX Delivered direct to MX with Outlook headers
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on mail.bitfolk.com)
Subject: Re: [bitfolk] IPv6 tunnel timeout
X-BeenThere: users@???
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
<mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
<mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 11:40:39 -0000
Hi Mike,
It's likely a TCP/UDP timeout on your ADSL router.
Fortunately I don't get that problem as I run OSPF/OSPF6 across my VPN - and
also Nagios :)
Kind regards
Jamie Stallwood
-----Original Message-----
From: users-bounces+vps-bitfolk=project76.net@???
[
mailto:users-bounces+vps-bitfolk=project76.net@lists.bitfolk.com] On Behalf
Of Mike Zanker
Sent: 18 July 2012 12:37
To: users@???
Subject: Re: [bitfolk] IPv6 tunnel timeout
Hi Peet,
On 18/07/2012 12:23, Peet Grobler wrote:
> Check the software you use on both ends, it seems like a dial-on-demand
> scenario going wrong. Grab the man page, see if you can find anything
> about dod or timeouts.
>
> Without you specifying the software you're using for the tunnel, there's
> really not much we can do.
I'm not using any extra software - just the standard initscripts-ipv6
that come with RHEL (and hence CentOS). It's a simple IPv6-in-IPv4
tunnel between the two sit devices.
Unfortunately, initscripts doesn't seem to have a timeout parameter for
tunnel devices.
I've set up a ping every 5 minutes from the VPS which seems to be
keeping it up in the meantime.
Thanks,
Mike
_______________________________________________
users mailing list
users@???
https://lists.bitfolk.com/mailman/listinfo/users
From mike@??? Wed Jul 18 11:46:53 2012
Received: from mail-ee0-f48.google.com ([74.125.83.48])
by mail.bitfolk.com with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16)
(Exim 4.72) (envelope-from <mike@???>) id 1SrSiS-0002tn-MM
for users@???; Wed, 18 Jul 2012 11:46:53 +0000
Received: by eekb57 with SMTP id b57so588531eek.21
for <users@???>; Wed, 18 Jul 2012 04:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zanker.org; s=google;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:content-type:content-transfer-encoding;
bh=MQiapl9hHLa1r7HklJOLWedkOXDi9Od86AOfxZjnSA8=;
b=QBt0cBZhjTDCXAvw99YAf5pddaEtGnb1yFmc0pSXhbeYKKoeW6Y5hoWWL7nUGMSaNT
Gy/WbbMNQk6hmJPVNW7cJ6IBi00VCtVH3vfaJzJgaPy23evu7HmQf5dhPeOfixoBSI6E
AHEFjoeb1v+0df1wgTKKpcAOyoFlrSqrhGxf4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=message-id:date:from:user-agent:mime-version:to:subject:references
:in-reply-to:content-type:content-transfer-encoding
:x-gm-message-state;
bh=MQiapl9hHLa1r7HklJOLWedkOXDi9Od86AOfxZjnSA8=;
b=m6PRAaKX1CD0eog/soicJLJ/Q8oqXTQL+MzMBaoFpz
