Update the IPv4 for the Hurricane Electric IPv6 Tunnel service for users with non static IPv4
- Linux - amd64, 386, arm, arm64, mips, mipsle, ppc64, ppc64le, s390x
- Windows - 386, amd64
- OS X - 386, amd64
- Dragonfly - amd64
- FreeBSD - 386, amd64, arm
- NetBSD - 386, amd64, arm
- openBSD - 386, amd64
- Solaris - amd64
In most cases this is enough to build:
go get github.com/eservicesgreece/hedynip
It will accept a full path and the file name can be any valid filename
hedynip --config=hedynip.json
hedynip -c hedynip.json
hedynip all --username=<ACCOUNT_USERNAME> --password=<ACCOUNT_PASSWORD>
hedynip a -u <ACCOUNT_USERNAME> - p <ACCOUNT_PASSWORD>
hedynip tunnel --id=<TUNNEL_ID> --username=<ACCOUNT_USERNAME> --password=<ACCOUNT_PASSWORD> or <TUNNEL_UPDATE_KEY>
hedynip t -i <TUNNEL_ID> -u <ACCOUNT_USERNAME> -p <ACCOUNT_PASSWORD> or <TUNNEL_UPDATE_KEY>
if --ip or -m are not provided hedynip will get the IPv4 automatically.
hedynip update --id=<TUNNEL_ID> --ip=<CLIENT IPV4> --username=<ACCOUNT_USERNAME> --password=<ACCOUNT_PASSWORD> or <TUNNEL_UPDATE_KEY>
hedynip update -i <TUNNEL_ID> -m <CLIENT IPV4> -u <ACCOUNT_USERNAME> -p <ACCOUNT_PASSWORD> or <TUNNEL_UPDATE_KEY>
hedynip getmyip
hedynip g
it will read hedynip.json or the configuration file provided by -c, --config
hedynip showconfig
hedynip s
You can add as many tunnel_id tags you want
{
"name": "hedynip",
"version": "1",
"credentials": {
"username": "",
"password": ""
},
"tunnel_id": {
"updatekey": ""
}
}
Example:
{
"name": "hedynip",
"version": "1",
"credentials": {
"username": "myusername",
"password": "mypassword"
},
"000000": {
"updatekey": "xD2YdAnNnhlMwYf3qX7n3Y"
},
"111111": {
"updatekey": "J0QjHjjd8sbtXaseiq3PyY"
}
}
- kingpin | https://github.com/alecthomas/kingpin
- tablewriter | https://github.com/olekukonko/tablewriter
- config | https://github.com/gookit/config
eSGR is not affiliated with or endorsed by Hurricane Electric (https://he.net)