Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by freese60, December 02, 2008, 06:33:59 AM
Quote from: smiffy on May 30, 2010, 08:07:14 PMI'm using the regular Debian Lenny /etc/network/interfaces configuration to set up my tunnel. Works fine. Only problem is that the tunnel appear to 'go away' after about 5-10 minutes, won't answer pings (or anything else.)The tunnel may be woken up again by pinging OUT. In fact, as a work-around, I've set up this little cron job to do a keep-alive:0,5,10,15,20,25,30,35,40,45,50,55 * * * * ping6 -c2 ipv6.he.net > /dev/null 2>&1...which works, but falls under the heading of a 'dirty hack' as far as I'm concerned.Can anyone throw any light on what might be the problem here and how I might resolve it?
Quote from: smiffy on May 31, 2010, 03:27:03 AM@jimb - many thanks for your reply!Hey, I never knew that crontab shortcut. How long have I been writing it longhand? About 20 years... *facepalm*
QuoteThis is an Internet-facing box with an iptables firewall (no NAT.) I Googled for iptables and 6in4 and - surprise surprise - was directed to another of your posts: http://www.tunnelbroker.net/forums/index.php?topic=816.0Just trying to figure out how that fits into my (non-NAT) scheme of things. Given $ipv4_tunnel_end_point, $my_ipv4_address, what would the rule look like to keep the channel open?For the record, I ran an IPv6 portscan on my box, when operational, and the services that normally show for IPv4 also show up for IPv6 (which is what I want - I just want all current services running dual-stack.)
Quote from: ago on May 20, 2010, 07:04:34 AMhttp://deve.loping.net/projects/he-update/
Quote from: broquea on August 11, 2010, 10:42:06 AMIf you are advertising out of eth0, then you need to configure 2001:470:f1yy:a::1/64 on eth0