1. Forum
  2. FidoNet
  3. IP Protocol Version 6

  • Route48

    From Michiel van der Vlist@2:280/5555 to All on Thu Mar 23 19:56:32 2023
    Hello All,

    Rumour has is that Route48 is closing down. I wonder how this will affect Fidonet. Especially net 134. The majority of nodes in net 134 uses a tunnel from Route48.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Nigel Reed@1:124/5016 to Michiel van der Vlist on Thu Mar 23 15:44:08 2023
    On Thu, 23 Mar 2023 19:56:32 +0100
    "Michiel van der Vlist" <michiel.van.der.vlist@2:280/5555> wrote:

    Hello All,

    Rumour has is that Route48 is closing down. I wonder how this will
    affect Fidonet. Especially net 134. The majority of nodes in net 134
    uses a tunnel from Route48.

    According to their website, it's already closed.

    There's always tunnelbroker.com which has been pretty reliable for me
    on my home system.
    --
    End Of The Line BBS - Plano, TX
    telnet endofthelinebbs.com 23
    --- SBBSecho 3.20-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Michiel van der Vlist@2:280/5555 to Nigel Reed on Thu Mar 23 22:13:54 2023
    Hello Nigel,

    On Thursday March 23 2023 15:44, you wrote to me:

    Rumour has is that Route48 is closing down. I wonder how this will
    affect Fidonet. Especially net 134. The majority of nodes in net 134
    uses a tunnel from Route48.

    According to their website, it's already closed.

    1:134/101 wirh IPv6 address 2a06:a004:4020:beef:f1d0:1:134:101 is still online...

    There's always tunnelbroker.com which has been pretty reliable for me
    on my home system.

    he.net seems to have issues as well. Their Amsterdam server has bee on and off for a while and now they are no longer accepting new tunnels for that server.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Fri Mar 24 06:47:47 2023
    On 23.3.2023 20.56, Michiel van der Vlist wrote:

    Rumour has is that Route48 is closing down.

    Yes. I got email from them yesterday.

    'Tommi

    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Tommi Koivula@2:221/360 to Nigel Reed on Fri Mar 24 06:48:01 2023
    On 23.3.2023 22.44, Nigel Reed wrote:

    Rumour has is that Route48 is closing down. I wonder how this will
    affect Fidonet. Especially net 134. The majority of nodes in net 134
    uses a tunnel from Route48.

    According to their website, it's already closed.

    The wireguard tunnnel at my phone is still working.

    'Tommi

    --- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Fri Mar 24 14:39:50 2023
    Hello Tommi,

    On Friday March 24 2023 06:47, you wrote to me:

    Rumour has is that Route48 is closing down.

    Yes. I got email from them yesterday.

    I have always wondered about the bussines model of these free tunnel providers. In tha case of SixXs it was clear: there was no bussines model, it was just idealism. And the end was not all that unpredictable: they (Jeroen Massar and Pim van Pelt) just got tired of it.

    In the case of he.net the bussines model was spreading IPv6 so that they could make money on those needing help getting their bussines running on IPv6. There are indications that their free tunnels may not last forever.

    Route48? Frankly I know very little about them. But whatever their bussines model was, it apparently didn't work...

    It would be a nice day when these tunnel provider were no longer needed because we all could get native IPv6 from our regular ISP.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Tommi Koivula@2:221/6 to Michiel van der Vlist on Fri Mar 24 16:25:50 2023
    On 24.3.2023 15.39, Michiel van der Vlist wrote:

    In the case of he.net the bussines model was spreading IPv6 so that
    they could make money on those needing help getting their bussines
    running on IPv6. There are indications that their free tunnels may
    not last forever.

    Route48? Frankly I know very little about them. But whatever their
    bussines model was, it apparently didn't work...

    Don't know about business model, but route48 was nice because they offered tunnel by wireguard. Wireguard doesn't need public ipv4.

    They also had a server in Finland. :)

    'Tommi

    --- FMail-lnx64 2.2.0.0
    * Origin: nntp://news.fidonet.fi (2:221/6.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Fri Mar 24 15:57:27 2023
    Hello Tommi,

    On Friday March 24 2023 16:25, you wrote to me:

    Route48? Frankly I know very little about them. But whatever their
    bussines model was, it apparently didn't work...

    Don't know about business model, but route48 was nice because they
    offered tunnel by wireguard. Wireguard doesn't need public ipv4.

    I am not familiar with Wireguard. Is it something like AYIYA that was offered by SixXs? That also worked behind (CG)NAT.

    They also had a server in Finland. :)

    "had"? Is it down already?

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Nigel Reed on Fri Mar 24 16:55:27 2023
    Hello Nigel,

    Thursday March 23 2023 22:13, I wrote to you:


    According to their website, it's already closed.

    1:134/101 wirh IPv6 address 2a06:a004:4020:beef:f1d0:1:134:101 is
    still online...

    Not any more...

    Same for 1:134/0, 100, 102, 103, 301, 302, 303

    Ergo: the entire net 134 is down except for 1:134/303 that still answers on IPv4.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Fri Mar 24 17:16:34 2023
    Hi Michiel,

    On 2023-03-24 16:55:27, you wrote to Nigel Reed:

    According to their website, it's already closed.

    1:134/101 wirh IPv6 address 2a06:a004:4020:beef:f1d0:1:134:101 is
    still online...

    MvdV> Not any more...

    MvdV> Same for 1:134/0, 100, 102, 103, 301, 302, 303

    MvdV> Ergo: the entire net 134 is down except for 1:134/303 that still answers on
    MvdV> IPv4.

    I can confirm that:

    1:134/0 nc.fido134.net:24554 2a06:a004:4020:beef:f1d0:1:134:0 Error: Connection timed out
    1:134/0 nc.fido134.net:24554 198.48.156.169 Error: Connection timed out 1:134/100 echohub.fido134.net:24554 2a06:a004:4020:beef:f1d0:1:134:100 Error: Connection timed out
    1:134/100 echohub.fido134.net:24554 178.128.187.153 Error: Socket read error.
    1:134/101 binkp.undermine.ca:24554 2a06:a004:4020:beef:f1d0:1:134:101 Error: Connection timed out
    1:134/101 binkp.undermine.ca:24554 198.48.156.169 Error: Connection timed out
    1:134/102 shellshockbbs.ddns.net:24554 2600:70ff:b88a:ab:f1d0:1:134:102 Error: Connection timed out
    1:134/103 bbs.technocentrist.com:24554 172.105.22.6 Error: Connection refused
    1:134/301 i2ibbs.ddns.net:24569 2600:70ff:b88a:ab:f1d0:1:134:301 Error: Connection timed out
    1:134/302 bbs.epochbbs.com:24554 2a06:a004:4020:beef:f1d0:1:134:302 Error: Connection timed out
    1:134/302 bbs.epochbbs.com:24554 172.105.106.228 Error: Socket read error.
    1:134/303 bbs.canerduh.com:24554 2604:3d09:227b:26af:19:a08b:78ab:5e16 Error: Connection timed out
    1:134/303 bbs.canerduh.com:24554 24.64.95.197 Ok.


    Bye, Wilfred.

    --- FMail-lnx64 2.2.0.0
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6 to Michiel van der Vlist on Fri Mar 24 18:22:10 2023
    On 24 Mar 2023 16.57, Michiel van der Vlist wrote:

    >> Route48? Frankly I know very little about them. But whatever their
    >> bussines model was, it apparently didn't work...

    TK> Don't know about business model, but route48 was nice because they
    TK> offered tunnel by wireguard. Wireguard doesn't need public ipv4.

    I am not familiar with Wireguard.

    One of the best available VPN software. I have a wireguard server running at home for remote access.

    See https://www.wireguard.com/

    TK> They also had a server in Finland. :)

    "had"? Is it down already?

    "Have". Still up. :)

    'Tommi

    ---
    * Origin: nntp://news.fidonet.fi (2:221/6.0)
  • From Benny Pedersen@2:230/0 to Michiel van der Vlist on Sun Mar 26 17:17:40 2023
    Hello Michiel!

    23 Mar 2023 19:56, Michiel van der Vlist wrote to All:

    MvdV> Rumour has is that Route48 is closing down. I wonder how this will
    MvdV> affect Fidonet. Especially net 134. The majority of nodes in net 134
    MvdV> uses a tunnel from Route48.

    is microsoft still supporting ppp0 devices ? :)

    my point is tunnel is not that bad, or its just more complicated to
    still use, more and more uses non tunnel setups, to make it more
    simple, what is not desired is that all bots try
    port 21 22 23 25 80 109 110 143 443 465 587 993 995, with all
    kinds of random username and passwords, thay sometimes
    succed, sadly world to live in


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/6.2.6-gentoo-dist (x86_64))
    * Origin: gopher://fido.junc.eu/ (2:230/0)
  • From Victor Sudakov@2:5005/49 to Michiel van der Vlist on Mon Apr 3 15:23:00 2023
    Dear Michiel,

    24 Mar 23 14:39, you wrote to Tommi Koivula:


    It would be a nice day when these tunnel provider were no longer
    needed because we all could get native IPv6 from our regular ISP.

    Hear, hear!

    Still no luck with any federal providers here in Tomsk. Rumour has it some of them can offer you some kind of tunnel (maybe its available for business customers), but noone is offering anything as simple as native IPv6 on my router's Ethernet interface.

    Against this background, the "MTS" mobile operator is advanced. I have a native IPv6 address from them on my Android phone (alongside with a RFC1918 IPv4 address).

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Victor Sudakov@2:5005/49 to Tommi Koivula on Mon Apr 3 15:28:16 2023
    Dear Tommi,

    24 Mar 23 18:22, you wrote to Michiel van der Vlist:


    >> Route48? Frankly I know very little about them. But whatever
    their
    >> bussines model was, it apparently didn't work...

    TK> Don't know about business model, but route48 was nice because
    they
    TK> offered tunnel by wireguard. Wireguard doesn't need public
    ipv4.

    I am not familiar with Wireguard.

    One of the best available VPN software. I have a wireguard server
    running at home for remote access.

    See https://www.wireguard.com/

    It has a major drawback as compared to GRE or IPIP. You cannot bind your side of the tunnel to a specific IP address (external address as related to the tunnel).

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)
  • From Alexey Vissarionov@2:5020/545 to Victor Sudakov on Tue Apr 4 02:08:08 2023
    Good ${greeting_time}, Victor!

    03 Apr 2023 15:28:16, you wrote to Tommi Koivula:

    I am not familiar with Wireguard.
    One of the best available VPN software. I have a wireguard server
    running at home for remote access. See https://www.wireguard.com/
    It has a major drawback as compared to GRE or IPIP. You cannot bind
    your side of the tunnel to a specific IP address (external address
    as related to the tunnel).

    Whether you need to set up multiple tunnels with different links (I guess this is the case), you may use VRF to keep them apart.

    Linux does that just fine.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... :wq!
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Victor Sudakov@2:5005/49 to Alexey Vissarionov on Tue Apr 4 11:50:12 2023
    Dear Alexey,

    04 Apr 23 02:08, you wrote to me:

    I am not familiar with Wireguard.
    One of the best available VPN software. I have a wireguard
    server running at home for remote access. See
    https://www.wireguard.com/
    It has a major drawback as compared to GRE or IPIP. You cannot
    bind your side of the tunnel to a specific IP address (external
    address as related to the tunnel).

    Whether you need to set up multiple tunnels with different links (I
    guess this is the case), you may use VRF to keep them apart.

    Linux does that just fine.

    Yes, I implied a case with two upstream ISPs when you want two tunnels to pass via different ISPs.

    I'm sure there exist some clever solutions, but with GRE or IPIP you could just use simple policy routing because the external src address is fixed.

    Do you suggest placing the two upstream ISPs into different VRFs?

    Victor Sudakov, VAS4-RIPE, VAS47-RIPN
    --- GoldED+/BSD 1.1.5-b20170303-b20170303
    * Origin: Ulthar (2:5005/49)