• FidoNews submission

    From Alexey Fayans@2:5030/1997 to Alex Galiyev on Fri May 30 10:19:36 2025
    Hello Alex!

    On Thu, 29 May 2025 19:35 -0400, you wrote to me:

    === Start of Windows Clipboard ===
    XLATCHARSET CP850 CP866 850_866.chs
    === End of Windows Clipboard ===
    Thanks for the advice, but it's much easier for one person to change
    their name than for thousands of people to update their configs.

    What else one person should change for other people convenience? Seriously, @CHRS kludge was invented a long time ago, maybe it's time for thousands to start following the standards?


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From ǽѬβá¡ñα â὿Ñó@1:129/14.1 to Alexey Fayans on Fri May 30 04:01:34 2025
    Hello Alexey!

    Friday May 30 2025 05:19, you wrote to me:

    What else one person should change for other people convenience?
    How does my name look now? It's in my native Cyrillic. Everyone, please add charset 866 to your editors. Nonsense.

    Alex

    --- GoldED+/W64-MSVC 1.1.5-b20250409
    * Origin: Glory to Ukraine! Glory to Heroes! Dump Trump! (1:129/14.1)
  • From Alex Galiyev@1:129/14.1 to Ward Dossche on Thu Jun 5 03:35:53 2025
    Hello Ward!

    Wednesday June 04 2025 23:07, you wrote to me:

    I don't know what the problem is with you, but there must be a pill
    Ward, the problem is with you, not me. You're a loser who hasn't achieved anything in his life.

    for it. Be careful you don't take the one to cure constipation.
    Thanks for the concern, but I'll leave the laxatives to you - clearly, you're the one full of it.

    Alex

    --- GoldED+/W64-MSVC 1.1.5-b20250409
    * Origin: Glory to Ukraine! Glory to Heroes! Dump Trump! (1:129/14.1)
  • From Karel Kral@2:423/39 to Ward Dossche on Thu Jun 5 14:08:35 2025
    Hello Ward!

    04 Jun 25 23:07, you wrote to Alex Galiyev:

    \%/@rd

    Few points, related to that thread, but not only for you:

    - if something is not working in fidonet flow, should be fixed. "is for free" defines of course priority, but should not be excuse

    - if I can not figure something out (here how to connect somewhere) and somebody helps me with advice which I do not like, I would say thanks (here to use ipv6)

    - in general: ignoring ipv6 is OK, but is limiting oportunities. If I have non stable [missing] ipv6, I consider it as disadvantage.

    Karel

    --- GoldED+/LNX 1.1.5-b20240209
    * Origin: Plast DATA (2:423/39)
  • From Björn Felten@2:203/2 to Dan Clough on Fri May 30 14:49:36 2025
    Dan Clough -> Björn Felten skrev 2025-05-29 15:49:
    Yes, Massa Gimme-Gimme. I will, of course, immediately see if I can
    give your Very Important Traffic on a depreciated network protocol,
    such as IPv4, higher priority.

    It's not "deprecated" (the proper spelling of what you mean).

    Oh, I'm sorry, Mr. Spelling Police. As this is my third (well actually my fourth since my uni education was with Proper English, not the bastardized US ditto) I'm still trying to keep up with this fourth language. But at least I've never complained about your horrible grammar.

    It's a world-wide standard, in widespread use.

    It was. A standard from 1981, when the web was more than a decade from being introduced and worldwide (sic) internet adoption was still another decade away. Stagnation has never been the way forward. Only redards think so.

    Also, I wasn't asking for
    higher priority, just that your system match what it advertises as it's capabilities. CM/IBN/INA. There aren't any "busy signals".

    What signals were they then? If you had quoted the errors you received, it might have helped you identify the problem.

    Why would it affect them at all? Are you using some kind of deprecated hardware, or something?

    You have no idea about my system, so why even try to tell me how to operate it?

    Strange how your system(s) are so unreliable.

    Not to any of my paying clients or free-of-charge important Fidonet friends, as far as I know. Yes, I know that there still are some IPv4 problems, but it does not seem to be a problem for all of them since they all use IPv6; therefore, my IPv6 theory. If you have any other explanation, I'm all ears.

    --

    Conning people is easy. You just need to overcome their intelligence. But convincing people they've been conned is much harder. You need to overcome their pride.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 6.2; sv-SE; rv:1.9.1.5) Gecko/20091121
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Alexey Fayans@2:5030/1997 to Aleksandr Galiev on Fri May 30 17:31:14 2025
    Hello Aleksandr!

    On Thu, 29 May 2025 23:01 -0400, you wrote to me:

    What else one person should change for other people convenience?
    How does my name look now? It's in my native Cyrillic. Everyone,
    please add charset 866 to your editors. Nonsense.

    Looks good to me. For anyone without native CP866 support there is 866_850.chs for GoldED, but the default one is ugly, I had to create my own (https://pb.bsrealm.net/view/raw/22d8a5ae). GUI viewers/editors shouldn't have any issues too.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Michiel van der Vlist@2:280/5555 to Gerrit Kuehn on Fri May 30 15:55:46 2025
    Hello Gerrit,

    On Thursday May 29 2025 12:00, you wrote to me:

    Who uses IPv6 networks anyways,

    MvdV>> About half the world by now.

    That depends very much on what values you actually look at. Most FTN operators count as "end user", so traffic comparison by volume on the carrier level is maybe not the best metric here. Also, this heavily depends on geography. Just to get an idea (yes, I know this is from
    2022, but you still get the idea): https://labs.ripe.net/author/wilhelm/ipv6-10-years-out-an-analysis-in- users-ta bles-and-traffic/

    Indeed there is no single simple way to measure IPv6 adoptation. My "about half the world buy now" was just a rough indication in respons to Alex' remark that suggested IPv6 was just some niche protocol.

    When we look at Fidonet, the list of IPv6 capable nodes presently has 108 entries. That is much less than half the number of unique entries in the nodelist, but with that we should keep in mind that the IPv6 nodes in the list are all or nearly all active nodes. Contrary to the global nodelist, there is very little dead wood in that list. So maybe the "about half" is not all that far off. Also, some or even many of the systems in Fidonet may be IPv6 capable without the sysop being aware of it. Except for the ones running very old hardware or some archaic OS, the systems themselves are IPv6 capable. Windows has IPv6 enabled by default since W7 and Linux is not far behind. Binkd supports IPv6 from versions above 1.00. Mystic and Sunchronet have followed. But contrary to the client only users, to run a fully fledged IPv6 Fidonet system one has to take some active steps. Like opening a pinhole in the IPv6 firewall. So there may be some Fidonet systems that could run an IPv6 node but still haven't enabled it.

    BTW, I am a bit curious about your use of feste-ip.net in you host name. I an familiar with feste-ip.net, I still have an account with them and I used it to experiment with their IPv4 -> IPv6 port forwarder. To be prepaired in case I ended up behind CGNAT.

    So what is your connection with feste-ip.net? AFAIK you are not running an IOv6 capable node.



    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Alex Galiyev on Fri May 30 16:32:46 2025
    Hello Alex,

    On Thursday May 29 2025 12:56, you wrote to me:


    they're damn slow.

    Nonsense. In fact IPv6 is a bit faster than IPv4. Less overhead.

    Tell this to our Comcast ISP users in Pennsylvania, in order to get
    better speeds, they have to disable ipv6.

    Then Comcast and/or their users are doing something wrong. Native IPv6 is definitely not slower than IPv4.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Dan Clough on Fri May 30 16:34:55 2025
    Hello Dan,

    On Thursday May 29 2025 08:49, you wrote to Björn Felten:

    I could not care less about having/using IPv6. Version 4 works just
    fine.

    IPv4 will not keep "working just fine". In fact for many in the world it already has stopped "working just fine" after their ISP put their IPv4 behind CGNAT.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Björn Felten@2:203/2 to Alexey Fayans on Fri May 30 16:55:56 2025
    Alexey Fayans -> Aleksandr Galiev skrev 2025-05-30 11:31:
    GUI viewers/editors shouldn't have any issues too.

    One 21th century editor available on every computer today, without requiring any knowledge of Fidonet, i.e. Thunderbird, handles it effortlessly, eliminating any issues.

    I can see your Cyrillics without problems, not just in any of the headers; it will not be adequately translated, since they are not designed to use any FTN cludges. DUH!


    --

    Conning people is easy. You just need to overcome their intelligence. But convincing people they've been conned is much harder. You need to overcome their pride.

    ..

    --- Mozilla/5.0 (Windows; U; Windows NT 6.2; sv-SE; rv:1.9.1.5) Gecko/20091121
    * Origin: news://eljaco.se:4119 (2:203/2)
  • From Michiel van der Vlist@2:280/5555 to ǽѬβá¡ñα â὿Ñó on Fri May 30 16:04:21 2025
    Hello ǽѬßá¡ñα â὿Ñó!

    29 May 25 23:01:34, ǽѬßá¡ñα â὿Ñó wrote to Alexey Fayans:

    What else one person should change for other people convenience?

    →→> How does my name look now? It's in my native Cyrillic.

    Looks OK to me.

    Everyone, please add charset 866 to your editors.

    To properly display both your name and Bj→rn's name you really need UTF-8...



    Michiel


    --- gossipEd-windows/386 0.2.7-166-e6853144
    * Origin: (2:280/5555)
  • From Dan Clough@1:135/115 to Björn Felten on Fri May 30 13:05:52 2025
    Björn Felten wrote to Dan Clough <=-

    Yes, Massa Gimme-Gimme. I will, of course, immediately see if I can
    give your Very Important Traffic on a depreciated network protocol,
    such as IPv4, higher priority.

    It's a world-wide standard, in widespread use.

    It was.

    Yes, and it still is, whether you like it or not.

    A standard from 1981, when the web was more than a decade
    from being introduced and worldwide (sic) internet adoption was still another decade away.

    None of that has anything to do with the subject at hand. Classic
    deflection attempt by somebody who's "out of ammo".

    To remind you - we're talking about how your system doesn't answer binkp connection attempts. If your system doesn't accept IPv4 connections,
    you should be indicating that with your nodelist entry.

    Also, I wasn't asking for
    higher priority, just that your system match what it advertises as it's capabilities. CM/IBN/INA. There aren't any "busy signals".

    What signals were they then? If you had quoted the errors you
    received, it might have helped you identify the problem.

    The "error" reported was "Unable to connect to el.jackoff.se" . That's
    it. Your system doesn't answer incoming connection attempts.

    Why would it affect them at all? Are you using some kind of deprecated hardware, or something?

    You have no idea about my system, so why even try to tell me how to operate it?

    Another non-answer. The question is (again): Why does your system not
    accept incoming calls, as advertised?

    Strange how your system(s) are so unreliable.

    Not to any of my paying clients or free-of-charge important Fidonet friends, as far as I know. Yes, I know that there still are some IPv4 problems, but it does not seem to be a problem for all of them since
    they all use IPv6; therefore, my IPv6 theory. If you have any other explanation, I'm all ears.

    I have the explanation. Your system doesn't support incoming IPv4 connections, and yet, your nodelist entry doesn't specify that. Either
    fix your hardware, or update your nodelist entry. Simple, eh?


    ... So easy, a child could do it. Child sold separately.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.25-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Dan Clough@1:135/115 to Michiel van der Vlist on Fri May 30 13:05:52 2025
    Michiel van der Vlist wrote to Dan Clough <=-

    I could not care less about having/using IPv6. Version 4 works just
    fine.

    IPv4 will not keep "working just fine".

    Is that like Al Gore saying the world would end "soon" due to "global
    warming" about 25 years ago?

    In fact for many in the world
    it already has stopped "working just fine" after their ISP put their
    IPv4 behind CGNAT.

    Yeah, well, I can't worry about (or fix) all the world's problems. Many people go to sleep hungry every night too. That sucks, but I can't fix
    that, and I can't worry about every single detail of the world's
    problems either. You can, if you want to.



    ... All hope abandon, ye who enter messages here.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.25-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Michiel van der Vlist@2:280/5555 to Dan Clough on Fri May 30 20:44:39 2025
    Hello Dan,

    On Friday May 30 2025 08:05, you wrote to me:

    IPv4 will not keep "working just fine".

    Is that like Al Gore saying the world would end "soon" due to "global warming" about 25 years ago?

    Irrelevant for the issue at hand.

    In fact for many in the world it already has stopped "working just
    fine" after their ISP put their IPv4 behind CGNAT.

    Yeah, well, I can't worry about (or fix) all the world's problems.
    Many people go to sleep hungry every night too. That sucks, but I
    can't fix that,

    But contrary to all these other problems, this is something you CAN do something about. You CAN upgrade your system to support IPv6. You may perceive it as not needed and you may be lucky and indeed not need it any time soon. IPv4 exhaustion may not be as big a problem in your neck of the woods as it is here. In the beginning your part of the world got a lot of IPv4. More than a fair share. So be it. But what happened to hat pioneer spirit that once made Fidonet great? Fidonet sysops were always eager to try out new technology. so what is stopping you from giving IPv6 a try? It isn't really hard once you get the hang of it. Why not give it a try? Just for the fun of it?

    You are welcome to join the IPv6 echo where you can get all the help you need from the IPv6 gurus in Fidonet.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Alex Galiyev@1:129/14.1 to Michiel van der Vlist on Fri May 30 15:25:20 2025
    Hello Michiel!

    Friday May 30 2025 11:32, you wrote to me:

    Tell this to our Comcast ISP users in Pennsylvania, in order to
    get better speeds, they have to disable ipv6.
    Then Comcast and/or their users are doing something wrong. Native IPv6
    is definitely not slower than IPv4.

    It's definitely slower by design:
    - Bigger headers (40 B vs. 20 B) add per-packet overhead.
    - Path MTU Discovery failures (blocked ICMPv6 "Too Big") lead to drops/retries. - Transitional tunnels (e.g. 6in4, Teredo) introduce extra hops and encapsulation cost.
    - Less hardware offload and OS-stack tuning for IPv6 vs. decades of IPv4 optimizations.

    Alex

    --- GoldED+/W64-MSVC 1.1.5-b20250409
    * Origin: Glory to Ukraine! Glory to Heroes! Dump Trump! (1:129/14.1)
  • From Dan Clough@1:135/115 to Michiel van der Vlist on Fri May 30 14:35:19 2025
    Michiel van der Vlist wrote to Dan Clough <=-

    In fact for many in the world it already has stopped "working just
    fine" after their ISP put their IPv4 behind CGNAT.

    Yeah, well, I can't worry about (or fix) all the world's problems.
    Many people go to sleep hungry every night too. That sucks, but I
    can't fix that,

    But contrary to all these other problems, this is something you CAN do something about. You CAN upgrade your system to support IPv6. You may perceive it as not needed and you may be lucky and indeed not need it
    any time soon. IPv4 exhaustion may not be as big a problem in your neck of the woods as it is here. In the beginning your part of the world got
    a lot of IPv4. More than a fair share. So be it. But what happened to
    hat pioneer spirit that once made Fidonet great? Fidonet sysops were always eager to try out new technology. so what is stopping you from giving IPv6 a try? It isn't really hard once you get the hang of it.
    Why not give it a try? Just for the fun of it?

    My ISP doesn't offer me IPv6. I'm not interested in putzing around to
    get some "workaround" tunnel thing working. Don't have time for such silliness, and there is no "fun of it" for me, as I'm just not
    interested in something which isn't a problem for me.

    You are welcome to join the IPv6 echo where you can get all the help
    you need from the IPv6 gurus in Fidonet.

    Yes, I read the echo. Seems to be mostly a self-congratulatory meeting
    place of mutual celebration/masturbation, with the repetitive posting of
    a list of Fido nodes who offer IPv6 connections. Doesn't interest me.




    ... Apathy Error: Strike any key...or none, for that matter.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.25-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Michiel van der Vlist@2:280/5555 to Alex Galiyev on Fri May 30 23:01:32 2025
    Hello Alex,

    On Friday May 30 2025 10:25, you wrote to me:

    Then Comcast and/or their users are doing something wrong. Native
    IPv6 is definitely not slower than IPv4.

    It's definitely slower by design:

    - Bigger headers (40 B vs. 20 B) add per-packet overhead.

    Hardly noticeable on modern hardware and well compensated by the packages themselves that can be larger.

    - Path MTU Discovery failures (blocked ICMPv6 "Too Big") lead to drops/retries.

    Blocking ICMPV6 is a configuration error, not a design flaw.

    - Transitional tunnels (e.g. 6in4, Teredo) introduce
    extra hops and encapsulation cost.

    Agreed, but those tunnel mechanisms were only meant to facilitate the transition. Should have been fased out long ago. And mostly are. I enjoy native IPv6 from my ISP for about a decade now.

    - Less hardware offload and OS-stack tuning for IPv6 vs. decades of
    IPv4 optimizations.

    IPv6 has been in use for well over a decade now. It has gone through the optimasation fase as well. Add to that the overhead in IPv4 like multiple levels of NAT and other tricks and work around to keep it working despite the IPv4 exhaustion.

    If IPv6 is noticeably slower than IPv4 someone is doing something wrong.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Dan Clough on Fri May 30 23:41:33 2025
    Hello Dan,

    On Friday May 30 2025 09:35, you wrote to me:

    But what happened to hat pioneer spirit that once made Fidonet
    great? Fidonet sysops were always eager to try out new technology.
    so what is stopping you from giving IPv6 a try? It isn't really hard
    once you get the hang of it. Why not give it a try? Just for the fun
    of it?

    My ISP doesn't offer me IPv6.

    And you are stuck with them? If so I do not envy you. Here I have a choice between over a dozen providers distributed over three fysical media. Nearly all of them offer native IPv6.

    I'm not interested in putzing around to get some "workaround" tunnel
    thing working.

    I have played around with tunnels before I got native IPv6 now nearly a decade ago. It was fun and an interesting experience.

    Don't have time for such silliness, and there is no "fun of it" for
    me, as I'm just not interested in something which isn't a problem for
    me.

    If you are no longer interested in trying out new things that seem to have no obvious purpose at first glance, why are you still in Fidonet? Fidonet is like a shipping company without passengers or cargo. But we just keep the ships running for the fun of it. It serves no real purpose any more.

    You are welcome to join the IPv6 echo where you can get all the
    help you need from the IPv6 gurus in Fidonet.

    Yes, I read the echo. Seems to be mostly a self-congratulatory
    meeting place of mutual celebration/masturbation,

    Like most of Fidonet...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Alex Galiyev@1:129/14.1 to Michiel van der Vlist on Fri May 30 17:35:07 2025
    Hello Michiel!

    Friday May 30 2025 18:01, you wrote to me:

    If IPv6 is noticeably slower than IPv4 someone is doing something
    wrong.
    Maybe in Europe IPv6 works better, but here in the U.S. it works significantly slower and unstable.

    Alex

    --- GoldED+/W64-MSVC 1.1.5-b20250409
    * Origin: Glory to Ukraine! Glory to Heroes! Dump Trump! (1:129/14.1)
  • From Michiel van der Vlist@2:280/5555 to Alex Galiyev on Sat May 31 03:14:30 2025
    Hello Alex,

    On Friday May 30 2025 12:35, you wrote to me:


    If IPv6 is noticeably slower than IPv4 someone is doing something
    wrong.

    Maybe in Europe IPv6 works better, but here in the U.S. it works significantly slower and unstable.

    I have difficulty believing that applies to the entire US. The equipment is basically the same and I do not see any mention of it in reports from the various parties. Maybe you had had the bad luck of having to deal with an ISP that has just recently introduced IPv6 and who is still battling the learning curve.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Gerrit Kuehn@2:240/12 to Michiel van der Vlist on Sat May 31 01:59:41 2025
    Hello Michiel!

    30 May 25 10:55, Michiel van der Vlist wrote to Gerrit Kuehn:

    MvdV> When we look at Fidonet, the list of IPv6 capable nodes presently
    MvdV> has 108 entries. That is much less than half the number of unique
    MvdV> entries in the nodelist, but with that we should keep in mind that
    MvdV> the IPv6 nodes in the list are all or nearly all active nodes.

    Just what I said: there are different angles to looks at statistics like these.

    MvdV> Contrary to the global nodelist, there is very little dead wood in
    MvdV> that list. So maybe the "about half" is not all that far off. Also,
    MvdV> some or even many of the systems in Fidonet may be IPv6 capable
    MvdV> without the sysop being aware of it. Except for the ones running
    MvdV> very old hardware or some archaic OS, the systems themselves are
    MvdV> IPv6 capable.

    I always thought "old hardware or some archaic OS" was the very definition of a FTN system these days... ;-)

    MvdV> Windows has IPv6 enabled by default since W7 and
    MvdV> Linux is not far behind.

    I think the question is not so much about the technical support (for Linux or *BSD, IPv6 is available since around 2000). I know a couple of admins who -even if their provider supports IPv6- simply disable it on all machines due to the unnecessary complexity it comes with.

    MvdV> So what is your connection with feste-ip.net? AFAIK you are not
    MvdV> running an IOv6 capable node.

    NM.


    Regards,
    Gerrit

    ... 8:59PM up 175 days, 3:06, 9 users, load averages: 0.53, 0.64, 0.72

    --- msged/fbsd 6.3 2021-12-02
    * Origin: Things I already know (2:240/12)
  • From Nigel Reed@1:124/5016.3 to Alex Galiyev on Fri May 30 21:02:33 2025
    //Hello Alex,//

    on *5/30/2025* at *16:35:07* You wrote in area *FIDONEWS*
    to *Michiel van der Vlist* about *"FidoNews submission"*.

    Hello Michiel!

    Friday May 30 2025 18:01, you wrote to me:

    If IPv6 is noticeably slower than IPv4 someone is doing something wrong.
    Maybe in Europe IPv6 works better, but here in the U.S. it works significantly slower and unstable.

    Alex

    --- GoldED+/W64-MSVC 1.1.5-b20250409
    * Origin: Glory to Ukraine! Glory to Heroes! Dump Trump! (1:129/14.1)

    Where is your evidence of that? Seems pretty much the same.


    bbs@bbs:/sbbs/xtrn/DDAreaChoosers$ ping -6 ns3.sysadmininc.com
    PING ns3.sysadmininc.com (2001:470:1f0e:28a::2) 56 data bytes
    64 bytes from tunnel687396-pt.tunnel.tserv8.dal1.ipv6.he.net (2001:470:1f0e:28a::2): icmp_seq=1 ttl=55 time=1.11 ms
    64 bytes from tunnel687396-pt.tunnel.tserv8.dal1.ipv6.he.net (2001:470:1f0e:28a::2): icmp_seq=2 ttl=55 time=1.35 ms
    64 bytes from tunnel687396-pt.tunnel.tserv8.dal1.ipv6.he.net (2001:470:1f0e:28a::2): icmp_seq=3 ttl=55 time=1.39 ms
    64 bytes from tunnel687396-pt.tunnel.tserv8.dal1.ipv6.he.net (2001:470:1f0e:28a::2): icmp_seq=4 ttl=55 time=1.36 ms
    64 bytes from tunnel687396-pt.tunnel.tserv8.dal1.ipv6.he.net (2001:470:1f0e:28a::2): icmp_seq=5 ttl=55 time=1.44 ms
    ^C
    -+- ns3.sysadmininc.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4006ms
    rtt min/avg/max/mdev = 1.111/1.327/1.437/0.112 ms bbs@bbs:/sbbs/xtrn/DDAreaChoosers$ ping -4 ns3.sysadmininc.com
    PING ns3.sysadmininc.com (107.174.228.105) 56(84) bytes of data.
    64 bytes from ns3.sysadmininc.com (107.174.228.105): icmp_seq=1 ttl=53 time=5.77 ms
    64 bytes from ns3.sysadmininc.com (107.174.228.105): icmp_seq=2 ttl=53 time=6.40 ms
    64 bytes from ns3.sysadmininc.com (107.174.228.105): icmp_seq=3 ttl=53 time=1.36 ms
    64 bytes from ns3.sysadmininc.com (107.174.228.105): icmp_seq=4 ttl=53 time=1.31 ms
    64 bytes from ns3.sysadmininc.com (107.174.228.105): icmp_seq=5 ttl=53 time=1.36 ms


    This is US to US

    bbs@bbs:/sbbs/xtrn/DDAreaChoosers$ ping -6 ns2.sysadmininc.com
    PING ns2.sysadmininc.com (2a04:92c7:2:376::eac5) 56 data bytes
    64 bytes from ns2.sysadmininc.com (2a04:92c7:2:376::eac5): icmp_seq=1 ttl=48 time=109 ms
    64 bytes from ns2.sysadmininc.com (2a04:92c7:2:376::eac5): icmp_seq=2 ttl=48 time=105 ms
    64 bytes from ns2.sysadmininc.com (2a04:92c7:2:376::eac5): icmp_seq=3 ttl=48 time=105 ms
    64 bytes from ns2.sysadmininc.com (2a04:92c7:2:376::eac5): icmp_seq=4 ttl=48 time=105 ms
    64 bytes from ns2.sysadmininc.com (2a04:92c7:2:376::eac5): icmp_seq=5 ttl=48 time=131 ms
    ^C
    -+- ns2.sysadmininc.com ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4004ms
    rtt min/avg/max/mdev = 105.010/111.013/131.118/10.154 ms bbs@bbs:/sbbs/xtrn/DDAreaChoosers$ ping -4 ns2.sysadmininc.com
    PING ns2.sysadmininc.com (130.185.249.215) 56(84) bytes of data.
    64 bytes from ns2.sysadmininc.com (130.185.249.215): icmp_seq=1 ttl=49 time=113 ms
    64 bytes from ns2.sysadmininc.com (130.185.249.215): icmp_seq=2 ttl=49 time=104 ms
    64 bytes from ns2.sysadmininc.com (130.185.249.215): icmp_seq=3 ttl=49 time=104 ms
    64 bytes from ns2.sysadmininc.com (130.185.249.215): icmp_seq=4 ttl=49 time=104 ms
    64 bytes from ns2.sysadmininc.com (130.185.249.215): icmp_seq=5 ttl=49 time=105 ms

    and then US to UK.

    --- WinPoint 415.0
    * Origin: Original *WinPoint* Origin! (1:124/5016.3)
  • From Alex Galiyev@1:129/14.1 to Nigel Reed on Fri May 30 22:45:31 2025
    Hello Nigel!

    Friday May 30 2025 16:02, you wrote to me:

    Where is your evidence of that? Seems pretty much the same.
    Simply sending 56-byte ICMP echo requests is not enough, this cannot serve as evidence.
    You need to send real payloads over a period of a few days to gather some evidence.
    I've worked in MSPs my whole career, so I have real-life experience with how IPv6 works here in Pennsylvania and IT SUCKS.

    Comcast is the worst when it comes to IPV6.

    Alex

    --- GoldED+/W64-MSVC 1.1.5-b20250409
    * Origin: Glory to Ukraine! Glory to Heroes! Dump Trump! (1:129/14.1)
  • From Dan Clough@1:135/115 to Michiel van der Vlist on Sat May 31 01:38:49 2025
    Michiel van der Vlist wrote to Dan Clough <=-

    But what happened to hat pioneer spirit that once made Fidonet
    great? Fidonet sysops were always eager to try out new technology.
    so what is stopping you from giving IPv6 a try? It isn't really hard
    once you get the hang of it. Why not give it a try? Just for the fun
    of it?

    My ISP doesn't offer me IPv6.

    And you are stuck with them? If so I do not envy you. Here I have a choice between over a dozen providers distributed over three fysical media. Nearly all of them offer native IPv6.

    Yes, it is the only realistic option I have. Not uncommon in the USA as
    far as I know. Cable/broadband companies often have their "territory"
    and they are the only provider in that area.

    I'm not interested in putzing around to get some "workaround" tunnel
    thing working.

    I have played around with tunnels before I got native IPv6 now nearly a decade ago. It was fun and an interesting experience.

    I like playing with lots of things, but that doesn't interest me in the slightest.

    Don't have time for such silliness, and there is no "fun of it" for
    me, as I'm just not interested in something which isn't a problem for
    me.

    If you are no longer interested in trying out new things that seem to have no obvious purpose at first glance, why are you still in Fidonet? Fidonet is like a shipping company without passengers or cargo. But we just keep the ships running for the fun of it. It serves no real
    purpose any more.

    Well, that may be your opinion. It serves purposes for me. I enjoy the configuration of FTN software, updating/customizing the BBS, and reading echomail traffic. I mean, we are having this very conversation on
    FidoNet, aren't we?

    You are welcome to join the IPv6 echo where you can get all the
    help you need from the IPv6 gurus in Fidonet.

    Yes, I read the echo. Seems to be mostly a self-congratulatory
    meeting place of mutual celebration/masturbation,

    Like most of Fidonet...

    Not really, it's quite different from most as far as I can see. I mean,
    what "real purpose" does it serve? Just a way for folks to congratulate
    each other on having an IPv6 address? LOL Very silly.



    ... Backup not found: (A)bort (R)etry (P)anic
    === MultiMail/Linux v0.52
    --- SBBSecho 3.25-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Nigel Reed@1:124/5016 to Alex Galiyev on Sat May 31 01:37:47 2025
    Re: FidoNews submission
    By: Alex Galiyev to Nigel Reed on Fri May 30 2025 17:45:31

    Simply sending 56-byte ICMP echo requests is not enough, this cannot serve as evidence.
    You need to send real payloads over a period of a few days to gather some evidence.
    I've worked in MSPs my whole career, so I have real-life experience with how IPv6 works here in Pennsylvania and IT SUCKS.

    bbs@bbs:~$ wget http://ipv4.download.thinkbroadband.com/1GB.zip (ipv4.download.thinkbroadband.com)|80.249.99.148|:80... connected.
    Length: 1073725334 (1024M) [application/zip]
    Saving to: `1GB.zip'
    1GB.zip
    100%[============================>] 1024M 17.4MB/s in 77s
    2025-05-30 20:30:47 (13.2 MB/s)

    bbs@bbs:~$ wget http://ipv6.download.thinkbroadband.com/1GB.zip (ipv6.download.thinkbroadband.com)... 2a02:68:1:7::1|:80... connected.
    Length: 1073725334 (1024M) [application/zip]
    Saving to: `1GB.zip.1'
    1GB.zip.1
    100%[============================>] 1024M 16.0MB/s in 75s

    So a 1GB file was 2 seconds quicker over ipv6 than ipv4 from some random host I found. I suppose this isn't enough of a test either?
    --- SBBSecho 3.27-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Alex Galiyev@1:129/14.1 to Nigel Reed on Sat May 31 03:16:12 2025
    Hello Nigel!

    Friday May 30 2025 20:37, you wrote to me:

    So a 1GB file was 2 seconds quicker over ipv6 than ipv4 from some
    random host I found. I suppose this isn't enough of a test either?
    Nope, this is still not a valid test.

    Alex

    --- GoldED+/W64-MSVC 1.1.5-b20250409
    * Origin: Glory to Ukraine! Glory to Heroes! Dump Trump! (1:129/14.1)
  • From Ward Dossche@2:292/854 to Dan Clough on Fri Jun 6 15:27:36 2025
    Dan,

    You, Bjorn, Ward .... Birds of a feather.

    That's a compliment, you know ...

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Ward Dossche@2:292/854 to Alex Galiyev on Fri Jun 6 15:29:07 2025
    Alex,

    Ward, the problem is with you, not me. You're a loser who hasn't achieved anything in his life.

    OK, if you say so pretending knowing me that well.

    Enjoy the week-end,

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Ward Dossche@2:292/854 to Dan Clough on Sat May 31 16:15:41 2025
    Dan,

    Yes, it is the only realistic option I have. Not uncommon in the USA as far as I know. Cable/broadband companies often have their "territory"
    and they are the only provider in that area.

    With the pile of friends I have overthere it is indeed a case.

    My guess is US-based ISPs have tonnes of IPv4-addresses reserved and think they can get away with not investing in IPv6.

    Now I need to say, I do have IPv6 parallel to IPv4 but when it drops to IPv4 for whatever reason or the other I don't notice until Wilfred calls me after a day or two-three.

    We all know technology renews faster and faster and I wonder if US-based (and Canadian?) ISPs are not playing Russian roulette with their customers...

    Not really, it's quite different from most as far as I can see. I mean, what "real purpose" does it serve? Just a way for folks to congratulate each other on having an IPv6 address? LOL Very silly.

    Well? Aren't you going to congratulate me? 8-)

    \%/@rd

    --- DB4 - 20230201
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Michiel van der Vlist@2:280/5555 to Gerrit Kuehn on Sat May 31 19:45:47 2025
    Hello Gerrit,

    On Friday May 30 2025 20:59, you wrote to me:

    MvdV>> Contrary to the global nodelist, there is very little dead wood
    MvdV>> in that list. So maybe the "about half" is not all that far
    MvdV>> off. Also, some or even many of the systems in Fidonet may be
    MvdV>> IPv6 capable without the sysop being aware of it. Except for
    MvdV>> the ones running very old hardware or some archaic OS, the
    MvdV>> systems themselves are IPv6 capable.

    I always thought "old hardware or some archaic OS" was the very
    definition of a FTN system these days... ;-)

    Today it wouid seem that way. But in the haydays of Fidonet syssop were always eager to try out new technology and even spend considerable amount of mobney on it. ISDN was embraced and so wsa DSL. Now FOIP is the rule rather than te exception. So why the reluctance to embrace IPv6? Contrary to ISDN, it doenn't have to cost anything in most cases. Complexity? Oh c'mon, ISDN was far more complex to install than IPv6.

    MvdV>> Windows has IPv6 enabled by default since W7 and
    MvdV>> Linux is not far behind.

    I think the question is not so much about the technical support (for
    Linux or *BSD, IPv6 is available since around 2000). I know a couple
    of admins who -even if their provider supports IPv6- simply disable it
    on all machines due to the unnecessary complexity it comes with.

    Than these admins have not understood or they are just lazy. Yes, a dusl stack system is moe complex than a single stack IPv4 system. But IPv6 by itself is not more complex than IPv4. On the contrary I would say. IPv6 is less complex. But it is different, there is a learning cuve and one has to "unlearn" some of the "IPv4 think". But once past that, it is relatively easy. And unavoidable in the long run anyway...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Kurt Weiske@1:218/700 to Michiel van der Vlist on Sat May 31 15:24:12 2025
    Michiel van der Vlist wrote to Dan Clough <=-

    If you are no longer interested in trying out new things that seem to have no obvious purpose at first glance, why are you still in Fidonet? Fidonet is like a shipping company without passengers or cargo. But we just keep the ships running for the fun of it. It serves no real
    purpose any more.

    Yes, but they're STEAM SHIPS, not newfangled container ships. We're
    shipping EBOLA MONKEYS around the world, not the latest consumer goods.



    --- MultiMail/Win v0.52
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)
  • From Gerrit Kuehn@2:240/12 to Michiel van der Vlist on Sun Jun 1 01:37:54 2025
    Hello Michiel!

    31 May 25 14:45, Michiel van der Vlist wrote to Gerrit Kuehn:

    MvdV> Now FOIP is the rule rather than te exception. So why the
    MvdV> reluctance to embrace IPv6? Contrary to ISDN, it doenn't have to
    MvdV> cost anything in most cases. Complexity? Oh c'mon, ISDN was far
    MvdV> more complex to install than IPv6.

    ISDN offered benefits: higher bandwidth (i.e., lower transfer costs), channel bundling, using your voice phone while data transmission is running, just to name a few.
    IPv6 offers nothing for most sysops apart from time to spend on understanding it, making it work, keeping it running.

    I think the question is not so much about the technical support (for
    Linux or *BSD, IPv6 is available since around 2000). I know a couple
    of admins who -even if their provider supports IPv6- simply disable
    it on all machines due to the unnecessary complexity it comes with.

    MvdV> Than these admins have not understood or they are just lazy.

    "lazy" is the wrong word here. Not everyone is a retired person in a single household. Having a job, running a family, maintaining a house, vehicles and other things the familiy needs consumes lots of time already. When there is not much time left in the first place, why bother with IPv6?

    MvdV> Yes, a
    MvdV> dusl stack system is moe complex than a single stack IPv4 system.
    MvdV> But IPv6 by itself is not more complex than IPv4. On the contrary I
    MvdV> would say. IPv6 is less complex.

    I beg to differ: I spent the better part of a weekend understanding just the parts I need to get everything running with my DSlite connection (mainly DHCP, DNS, routing). It *is* more complex than IPv4 in many places, running IPv4 and IPv6 together needs even more thinking, firewalling and other security aspects come on top.
    I am thinking about disabling it again on my internal (in-house) network. It provides no benefit.

    MvdV> But it is different, there is a
    MvdV> learning cuve and one has to "unlearn" some of the "IPv4 think".
    MvdV> But once past that, it is relatively easy. And unavoidable in the
    MvdV> long run anyway...

    I do not see any device or OS being sold as "IPv6 only" in the medium-term future. There are way to many installations that require IPv4 compatibility. There is no market for an "IPv6 only" device or software.


    Regards,
    Gerrit

    ... 8:37PM up 176 days, 2:44, 10 users, load averages: 0.69, 0.71, 0.68

    --- msged/fbsd 6.3 2021-12-02
    * Origin: A true lie to believe (2:240/12)
  • From Alexey Fayans@2:5030/1997 to Michiel van der Vlist on Sun Jun 1 05:14:07 2025
    Hello Michiel!

    On Sat, 31 May 2025 14:45 +0200, you wrote to Gerrit Kuehn:

    So why the reluctance to embrace IPv6?

    Because of the way it's implemented worldwide. Once it will be mandatory and primary protocol, I am sure everyone will embrace it.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)