1. Forum
  2. FidoNet
  3. IPV6

  • he.net

    From Andrew Leary@1:320/219 to Michiel van der Vlist on Mon Jul 19 06:18:09 2021
    Hello Michiel!

    19 Jul 21 11:38, you wrote to all:

    he.net was always using 2001:407:: for tunnels. It seems they now use

    2001:470:: in my experience... I still have a tunnel registered with he.net but haven't used it lately since my ISP now offers native IPv6.

    2006:70ff::

    Regards,

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Mon Jul 19 19:40:04 2021
    Hi Michiel.

    19 Jul 21 15:19:22, you wrote to Andrew Leary:

    he.net was always using 2001:407:: for tunnels. It seems they now
    use

    2001:470:: in my experience... I still have a tunnel registered with
    he.net but haven't used it lately since my ISP now offers native IPv6.

    The 407 was a typo. I too had a 2001:470:: address for my tunnel. My experience is that yje
    delete tunnels that are no longer kept alive. When I goy native IPv6 I could not kee[ the
    tunnel because the router from my provider does not support tunnels.

    2006:70ff::

    Andrew Savin has a he.net tunnel with a 2006:70ff:: address.

    I wonder if they exausted the 2001:470::/32 block...

    Just created a tunnel to stockholm:

    === Cut ===
    Routed IPv6 Prefixes
    Routed /64:2001:470:28:376::/64
    Routed /48:2001:470:dfeb::/48
    === Cut ===

    So it may depend which endpoint to use...

    I still have one operational tunnel which I created "Nov 14, 2014".. Both /64 and /48. :)

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/360)