1. Forum
  2. FidoNet
  3. IPV6

  • Involuntary IPv6 only node

    From Michiel Van Der Vlist@1:2320/100 to All on Fri Feb 10 11:38:42 2017
    Hello All,

    It seems we had an involuntary IPv6 only node for a couple of days.

    The system of Bill McGarrity, 1:266/404 was unreachable via IPv4 for a while. Ipv6 kep working though.

    This caused some confusion because some could connect while others could not. It took a while for someone to realise that broken IPv4 was the problem.

    This illustrates why the transtions from IPv4 to IPv6 has to be as short as possible. With IPv4 and IPv6 nest to each other, it can take quit a while to realise there is a problem with one of the two.

    In the IPv4 only era a problem with IPv4 was quickly noticed. Now it isn't...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    # Origin: he.net certified sage (2:280/5555)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Kees Van Eeten@1:2320/100 to Michiel Van Der Vlist on Fri Feb 10 13:08:32 2017
    Hello Michiel!

    10 Feb 17 11:39, you wrote to All:

    MvdV> This illustrates why the transtions from IPv4 to IPv6 has to be as short
    MvdV> as possible. With IPv4 and IPv6 nest to each other, it can take quit a
    MvdV> while to realise there is a problem with one of the two.

    MvdV> In the IPv4 only era a problem with IPv4 was quickly noticed. Now it
    MvdV> isn't...

    You make it look as if almost all connections to Bill's system are made
    using IPv6.

    Kees

    --- GoldED+/LNX 1.1.5
    # Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Tony Langdon@1:2320/100 to Michiel Van Der Vlist on Sun Feb 12 23:35:00 2017
    Michiel van der Vlist wrote to All <=-

    It seems we had an involuntary IPv6 only node for a couple of days.

    The system of Bill McGarrity, 1:266/404 was unreachable via IPv4 for a while. Ipv6 kep working though.

    That was me, until I got my IPv4 tunnel sorted, so it would reconnect if it became non functional. Turns out OpenVPN has a bug on my system, where the tunnel can remain "up", but be incapable of passing traffic. My tunnel router now periodically checks for this condition and resets the VPN when it happens.

    In the IPv4 only era a problem with IPv4 was quickly noticed. Now it isn't...

    Indeed, I have had instances of "what problem"? when IPv6 capable sites break on IPv6. I've also seen the opposite, where IPv6 is borked, which is a pain for me.


    ... Itisdifficulttobeverycreativewithonlyfiftysevencharacters
    --- MultiMail/Win32 v0.49
    # Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)