etwork. If
I ping6 something on the home network from the VPS it appears to wake
the tunnel up again.
Is there a way round this (other than having a cron job ping something
every minute or so) - maybe some sort of timeout parameter when setting
up a sit tunnel?
Thanks in advance,
Mike
From peet@??? Wed Jul 18 11:23:01 2012
Received: from mead.hivemind.net ([41.76.209.65])
by mail.bitfolk.com with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
(Exim 4.72) (envelope-from <peet@???>) id 1SrSLL-0001TX-Qh
for users@???; Wed, 18 Jul 2012 11:23:01 +0000
Received: from 196-210-193-230.dynamic.isadsl.co.za ([196.210.193.230]:64804
helo=mac-wifi.peet.za.net)
by mead.hivemind.net with esmtpa (Exim 4.72 #1)
id 1SrSZA-00023R-9R by authid <peet> with plain_courier_authdaemon
for <users@???>; Wed, 18 Jul 2012 13:37:16 +0200
Message-ID: <50069CC5.6060908@???>
Date: Wed, 18 Jul 2012 13:23:49 +0200
From: Peet Grobler <peet@???>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: users@???
References: <50069746.2010401@???>
In-Reply-To: <50069746.2010401@???>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Whitelisted: Authenticated sender, whitelisted
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Wed,
18 Jul 2012 11:23:00 +0000
X-SA-Exim-Connect-IP: 41.76.209.65
X-SA-Exim-Mail-From: peet@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
spamd3.lon.bitfolk.com
X-Spam-Level:
X-Spam-ASN: AS3741 41.76.208.0/21
X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED
shortcircuit=no autolearn=disabled version=3.3.1
X-Spam-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at
http://www.dnswl.org/, * medium trust
* [41.76.209.65 listed in list.dnswl.org]
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:23:01 -0000
On 2012-07-18 1:00 PM, Mike Zanker wrote:
> Is there a way round this (other than having a cron job ping something
> every minute or so) - maybe some sort of timeout
