On 23 Jun 2023 at 10:30a, Michiel van der Vlist pondered and said...
Indeed no IPv6 for now.
Yep
I see you were running a he.net tunnel. Does it mean you will
have native IPv6? Or is there a problem getting the tunnel back
up?
I may end up with a mix of both, I think I may get some native
allocation with my new ISP in the coming weeks. Not sure... but also looking to have a tunnel running again as I'd like to make use of that too. My hope is it will be possible to do both without too much issue.
Indeed no IPv6 for now.Yep
No change, so I will flag you as "6DWN" in the list for now.
I may end up with a mix of both, I think I may get some native allocation with my new ISP in the coming weeks. Not sure... but also looking to have a tunnel running again as I'd like to make use of tha too. My hope is it will be possible to do both without too much issue
Interesting. With a he.net tunnel you have a fixed IPv6 prefix and that has its advantages. With native IPv6 you may have a (semi) dynamic
prefix. Your milage may vary. Other than that I find native IPv6 much preferable ove a tunnel. He,net offers a fantastic service for a very attractive price, but a tunnel just can not match native IPv6. At least that is my experience.
Please keep us posted.
Please keep us posted.
*** Answering a msg posted in area FN_SYSOP (International Fido
Sysops).
Hello Paul,
On Saturday June 24 2023 12:26, you wrote to me:
On 23 Jun 2023 at 10:30a, Michiel van der Vlist pondered and
said...
Indeed no IPv6 for now.
Yep
No change, so I will flag you as "6DWN" in the list for now.
I see you were running a he.net tunnel. Does it mean you will
have native IPv6? Or is there a problem getting the tunnel back
up?
I may end up with a mix of both, I think I may get some native allocation with my new ISP in the coming weeks. Not sure... but
also looking to have a tunnel running again as I'd like to make
use of that too. My hope is it will be possible to do both
without too much issue.
Interesting. With a he.net tunnel you have a fixed IPv6 prefix and
that has its advantages. With native IPv6 you may have a (semi)
dynamic prefix. Your milage may vary. Other than that I find native
IPv6 much preferable ove a tunnel. He,net offers a fantastic service
for a very attractive price, but a tunnel just can not match native
IPv6. At least that is my experience.
Please keep us posted.
he.net tunnel should be back up, I have added DNS records for the new address.
I'm hoping my new ISP will provide a static IPc6 range that I can use.
As a side note, Google search over ipv6 is broken. They're basically rejecting requests.
I ended up turning my home ipv6 tunnel off until its fixed.
Odd. I suspect this is not really a problem with IPv6 but a problem with the he.net tunnel. A well known issue with he.net tunnels is that geolocation does not work properly and that can mess up things.
The "proper" fix would be that your ISP gives you native IPv6. It has been 11 years since World IPv6 Launch, ISPs that still only offer IPv4 deserve to go belly up. Are you stuck with them?
I couldn't find a way to do so with the Android phones. I ended up
turning my home ipv6 tunnel off until its fixed.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 32:26:44 |
Calls: | 141 |
Files: | 5,058 |
Messages: | 220,694 |