|
From: SourceForge.net <no...@so...> - 2011-02-24 04:40:06
|
Patches item #2471040, was opened at 2008-12-27 04:47 Message generated for change (Comment added) made by hpa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2471040&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: new services Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: J. Randall Owens (karmannjro) Assigned to: Nobody/Anonymous (nobody) Summary: add HE IPv6 tunnel broker service Initial Comment: This one's a slight change of pace, since it's not actually a dynamic DNS being updated, but rather an IPv6 tunnel broker, Hurricane Electric. I was thinking what might be the best way to cover for it if/when my IP(v4) finally changes, since you have to have your IPv4 address registered with them, so they allow your encapsulated IPv6 traffic through. Then I remembered the time I've spent poking at ddclient's innards, and figured it could almost certainly be modified to suit the need. Here's the output. There was one complication, in that it needs the Digest::MD5 perl module, because they want a hash of the password, but that seems to be a pretty standard module. Seems like the alternative would be to make users find the MD5 of their own passwords, and enter that as their password parameter. The format information, as much as I can get, is at http://ipv4.tunnelbroker.net/ipv4_end.php . I don't yet know whether the SSL is mandatory, as seems to be implied there. Can the ssl option be set per server, or only globally? I wasn't clear on that yet; for now, I have my addition set up as though it can be per server. (Completely untested yet, BTW, so look it over.) The rest of it should be pretty self-documenting, if you look at nic_he_ipv6_tunnel_examples output. The biggest departure is that it uses a tunnel ID number (up to 5 digits, to date) where you would normally put a domain name. Almost like Sitelutions in that way, though. ---------------------------------------------------------------------- Comment By: H. Peter Anvin (hpa) Date: 2011-02-23 20:40 Message: I have updated and bug fixed this patch, the new one is posted in ID 3190845. ---------------------------------------------------------------------- Comment By: J. Randall Owens (karmannjro) Date: 2008-12-29 04:37 Message: One correction to make, I guess the login they expect in the GET URL arguments isn't what an HE user might normally think of as their login, but a long random-looking string of what looks like 32 hex characters (512 bits if so). Just change nic_he_ipv6_tunnel_examples' login text to my_he_ipv6_ID, or something like that. ---------------------------------------------------------------------- Comment By: J. Randall Owens (karmannjro) Date: 2008-12-27 12:37 Message: Oh, to be complete, I'm not sure if it would need a postscript to run to rebuild the tunnel interface. If so, it would be very much OS dependent, and in Linux, even dependent on whether you prefer `ifconfig` or `ip`. So, that might be something to add in the /usr/share/doc/ddclient-*/ examples, but certainly not in the live program. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2471040&group_id=116817 |
