1. Forum
  2. FidoNet
  3. FN SYSOP

  • Kees van Eeten and IPv4

    From Michiel van der Vlist@2:280/5555 to All on Mon May 13 13:19:47 2019
    * Originally in ENET.SYSOP
    * Crossposted in FN_SYSOP

    Hello All,

    The system of Kees van Eeten, 2:280/0 AKA 2:280:5003 has been unreachable via IPv4 for about a week. That it took so long to notice is beause those having IPv6 don't have any problems.

    I can not reach Kees at the moment. So I created a work around via Fest-IP.net.
    2:280/0 and 2:280/5003 can now be connected on IPv4 via:


    de4.portmap64.net:24554 (binkp only)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Kees van Eeten@2:280/5003.4 to Michiel van der Vlist on Mon May 13 16:27:22 2019
    Hello Michiel!

    13 May 19 13:19, you wrote to All:

    MvdV> The system of Kees van Eeten, 2:280/0 AKA 2:280:5003 has been
    MvdV> unreachable via IPv4 for about a week. That it took so long to notice is
    MvdV> beause those having IPv6 don't have any problems.

    MvdV> I can not reach Kees at the moment. So I created a work around via
    MvdV> Fest-IP.net.
    MvdV> 2:280/0 and 2:280/5003 can now be connected on IPv4 via:


    MvdV> de4.portmap64.net:24554 (binkp only)

    Interesting ;)

    A different IPv4 address was issued. That address is now entered into DNS.
    Pending normal progagation, the new address will show itself within the
    coming few hours.


    Kees

    --- GoldED-NSF/LNX 1.1.5-b20100318
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Tue May 14 19:19:00 2019
    On 05-13-19 13:19, Michiel van der Vlist wrote to All <=-

    The system of Kees van Eeten, 2:280/0 AKA 2:280:5003 has been
    unreachable via IPv4 for about a week. That it took so long to notice
    is beause those having IPv6 don't have any problems.

    Sign of the times? :D It could happen to me, because my IPv4 is via OpenVPN. I have scripts that monitor the tunnel and reset it if necessary, which has made it a lot more reliable.


    ... Don't say during sex: "Now I know why he dumped you..."
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Michiel van der Vlist@2:280/5555.1 to Tony Langdon on Tue May 14 14:15:59 2019
    Hello Tony,

    On Tuesday May 14 2019 19:19, you wrote to me:

    The system of Kees van Eeten, 2:280/0 AKA 2:280:5003 has been
    unreachable via IPv4 for about a week. That it took so long to
    notice is beause those having IPv6 don't have any problems.

    Sign of the times? :D It could happen to me, because my IPv4 is via OpenVPN. I have scripts that monitor the tunnel and reset it if
    necessary, which has made it a lot more reliable.

    Tunnels are less robust than native connections. So what we see occasionally is that nodes that use IPv6 via a tunnel loose their IPv6 connection because the tunnel collapses. IPv4 renains functional. Your situation: native IPv6 with tunneled IPv4 is still an exception, but with the coming of DS-Lite that may change in the not too distant future. Sign of the times? Yes, I'd say so.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Michiel's laptop (2:280/5555.1)
  • From Michiel van der Vlist@2:280/5555.1 to All on Tue May 14 15:04:15 2019
    * Originally in ENET.SYSOP
    * Crossposted in FN_SYSOP
    Hello All,

    Monday May 13 2019 13:19, I wrote to you:

    The system of Kees van Eeten, 2:280/0 AKA 2:280:5003 has been
    unreachable via IPv4 for about a week. That it took so long to notice
    is beause those having IPv6 don't have any problems.

    I can not reach Kees at the moment. So I created a work around via Fest-IP.net.

    The problem is solved. 280/0 and 280/5003 can be connected in the "normal" way again via fido.ddutch.nl.

    2:280/0 and 2:280/5003 can now be connected on IPv4 via:

    de4.portmap64.net:24554 (binkp only)

    The 4 to 6 proxy served its purpose, but is no longer needed. It will be removed tomorrow.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: Michiel's laptop (2:280/5555.1)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Wed May 15 08:02:00 2019
    On 05-14-19 14:15, Michiel van der Vlist wrote to Tony Langdon <=-

    Tunnels are less robust than native connections. So what we see occasionally is that nodes that use IPv6 via a tunnel loose their IPv6 connection because the tunnel collapses. IPv4 renains functional. Your situation: native IPv6 with tunneled IPv4 is still an exception, but
    with the coming of DS-Lite that may change in the not too distant
    future. Sign of the times? Yes, I'd say so.

    Yeah, I'm just ahead of the pack, because I do things my way. It's a lot cheaper to get multiple IPv4 this way than natively through my ISP.


    ... C:\BELFRY is where I keep my .BAT files. ^^^oo^^^
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)