So far as I know, the decision is not up to me, but to my ISP.
It takes less than a minute to get one.
Wrong... It took me almost two minutes to get a tunnel from he.net. :-)
Why you might ask since I already have a native IPv6 address.
have never gotten any personnel hand experience. So.. I decided to see
for my self.
I may ask some questions if the need arises.
So far as I know, the decision is not up to me, but to my ISP.
Then you know wrong.
With a tunnel like e.g. he.net you get a stable IPv6 address regardless of what your ISP can offer you. It takes less than a minute to get one. If your IPv4 address changes, it takes only seconds to update your IPv6 -- much faster than updating your IPv4 via various TTL settings at all DNS servers involved...
I've had a reliable IPv6 connection for almost 15 years now -- and I'm still
waiting for my ISP to offer me a "native" IPv6 address.
So far as I know, the decision is not up to me, but to my ISP.
Then you know wrong.
With a tunnel like e.g. he.net you get a stable IPv6 address regardless of what your ISP can offer you. It takes less than a minute to get one. If your IPv4 address changes, it takes only seconds to update your IPv6 -- much faster than updating your IPv4 via various TTL settings at all DNS servers involved...
I've had a reliable IPv6 connection for almost 15 years now
And still after 15 years of "reliable ipv6 connection" :
tommi@rpi:~$ telnet -6 eljaco.se 119
Trying 2001:470:27:302::2...
telnet: Unable to connect to remote host: Connection refused
tommi@rpi:~$
tommi@rpi:~$ telnet -6 eljaco.se 119
Trying 2001:470:27:302::2...
telnet: Unable to connect to remote host: Connection refused
tommi@rpi:~$
Incoming IPv6 is used only for certain services here, telnet is not
one of them.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 60 |
Nodes: | 4 (0 / 4) |
Uptime: | 13:53:08 |
Calls: | 516 |
Files: | 7,043 |
D/L today: |
1 files (12K bytes) |
Messages: | 289,411 |