SixXS::Sunset 2017-06-06

heartbeats to own endpoint?
[de] Shadow Hawkins on Tuesday, 18 January 2005 17:49:29
Hi, I have a static server connected to 100MBit bidirectional bandwidth which is already IPv6-connected via sixxs. If I'd add a subnet to it I could use it as a remote tunnel endpoint for my DSL-dialups, thus no longer needing three (or even more) tunnels to the same POP (single point of failure). I guess it's a good idea not to rely on a single connection when handling mail via smtp6. I think it's nice to have my different locations on the same subnet (prefix). I'm looking for a way to let my heartbeats connect to my server without reinventing the whole heartbeat-protocol. Perhaps I'm looking for the server-side-version of heartbeat (aiccu) or another solution to identify, authenticate and authorize two dynamic tunnels. I might trigger a ssh-script which reconfigures the tunnel-interfaces on the server (Linux) by ppp-up but I don't like the idea to leave root-keys (or sudo-enabled keys) on my DSL-gateways. I might create a https-request with a password and call a script via apache, but I'm not really willingly to let apache do anything with root-permissions, actually it's going to be put into chroot. Is there a running solution? How do others handle such a situation?
heartbeats to own endpoint?
[de] Shadow Hawkins on Tuesday, 25 January 2005 20:23:07
There must be implementations out in the wild, I know that Thorsten Glaser has rewritten the heartbeat-protocol in shellscript. Anyway, I wrote my own tunnel-changing client-server-shellscript. At the moment it isn't very well documented, but if you want to check it out, you'll find it here: http://adi.thur.de/files/ipv6tunnel.tgz If you have questions, feel free to ask. I would also appreciate any feedback.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker