• Re: New rule

    From Dan Clough@1:135/115 to Michiel van der Vlist on Sun Jul 20 18:23:28 2025
    Michiel van der Vlist wrote to Mike Powell <=-

    The use of AI (Artifical Intelligence) to generate message text is >
    discouraged.

    Sadly, we have reached that point in our history where this is
    possible and, on the internet anyway, likely to happen.

    I hope that at least in Fidonet we can manage it. AI can be a usefull tool, even to help people configure their IPv6. But we should not use
    it to generate text in echomail messages.

    I'm assuming your "new rule" is in regard to my recent post to Beeeorn.

    Here I'd thought you'd been around a while. That text is not
    AI-generated, and in fact is about 30 years old. It's been posted a
    million times over those years. It is widely accredited to a dude named
    Guy Macon. Sheesh.

    Don't believe me? See here:

    https://www.youtube.com/watch?v=6x9fI5Ov91M



    ... The future's uncertain, the end is always near.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.29-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Björn Felten@2:203/2 to Mike Powell on Tue Jul 22 22:16:36 2025
    Mike Powell -> MICHIEL VAN DER VLIST skrev 2025-07-21 17:14:
    Speaking about IPv6: how are you doing? Does your provider support it?

    No, they do not at this point. I am guessing it will be one of those things that happens that we are not told about until we just notice it. ;)

    If you take a look at the list, which Michiel has updated for the Fidonews like clockwork every Sunday at 22:00 CET for years, you'll see that around 80% have Native (i.e. from their provider) IPv6.

    You'll also see that the remaining 20% all but one use a tunnel from he.net. So why do you have to wait? Get ready for the future, already.

    --

    You write in English because it is the only language you know.
    I write in English because it is the only language you know.

    ..

    --- 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 Jay Harris@1:229/664 to Michiel van der Vlist on Wed Jul 23 09:47:54 2025
    On 23 Jul 2025, Michiel van der Vlist said the following...

    It is my understanding that in many parts of the rest of the world the situation is different. Many poviders still do not offer IPv6 and there
    is no competition between providers.

    Here in my city in Canada my cable provider (Rogers) supports native IPv6 but Bell Fibe (fibre direct to the house) does not.

    To make things more confusing, if I were to buy cable internet from a reseller (e.g. Teksavvy), they don't support IPv6 over cable. If I were to buy fibre internet from Teksavvy, they do support IPv6 but getting it to work involves using your own router, SFP module & knowing how to configure it.

    So Rogers Cable is the only "plug & play" IPv6 provider in my neighbourhood at the moment.


    Jay

    ... How many bones are in the human hand? A handful of them

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (1:229/664)
  • From Björn Felten@2:203/2 to Jay Harris on Wed Jul 23 18:07:38 2025
    Jay Harris -> Michiel van der Vlist skrev 2025-07-23 15:47:
    So Rogers Cable is the only "plug & play" IPv6 provider in my neighbourhood at the moment.

    How many, if any, of those service providers you mention are directly or indirectly US based?

    Now that it seems you're bravely escaping the grip of the US, do you think your situation will improve? For instanse, with a direct Atlantic cable (with fiber) to the EU?


    --
    Q: What borders stupidity?
    A: Canada and Mexico.
    ..

    --- 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 Nick Boel@1:154/700 to Michiel van der Vlist on Wed Jul 23 17:10:07 2025
    Hey Michiel!

    On Wed, Jul 23 2025 06:48:42 -0500, you wrote:

    It is my understanding that in many parts of the rest of the world
    the situation is different. Many poviders still do not offer IPv6
    and there is no competition between providers.

    Keep in mind, there is a fairly large population - and it's probably a bigger population than the people actually interested in IPv6 even - that have no clue what an IPv4 or IPv6 address is, nor do they care if you try to explain it to them, as long as they can stream their TV shows and connect to the internet.. that is all that matters.

    So to all sysops that still have that bit of pioneer spirit left in> them end who are stuck with a provider that offers no native IPv6 I
    say: Use the service of he.net to join the Fidonet IPv6 club!

    While I agree with this, some sysops can't even configure their BBS or Golded properly. So if you care to hold their hand and walk them through setting up a he.net tunnel, you're more than welcome to and I commend you for doing so.. but don't get upset when you point them to all of your terriffic Fidonews articles and they get mad at you for pointing them to documentation. ;)

    Regards,
    Nick

    ... Sarcasm, because beating people up is illegal.
    --- SBBSecho 3.29-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
  • From Stas Mishchenkov@2:460/5858 to Jay Harris on Thu Jul 24 08:53:12 2025
    Hi Jay!

    Wednesday July 23 2025 09:47, you wrote to Michiel van der Vlist:

    If I were to buy fibre internet from Teksavvy, they do support IPv6
    but getting it to work involves using your own router, SFP module & knowing how to configure it.

    This is how it works for me. My own router, two ISPs at the same time and I know how to set it up. ;)

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nick Boel@1:154/700 to Michiel van der Vlist on Thu Jul 24 17:02:39 2025
    Hey Michiel!

    On Thu, Jul 24 2025 03:26:21 -0500, you wrote:

    Of course. But I hope and expect that different statistics apply to
    the Fidonet community. Joining Fidonet always required above
    technical knowledge and although it may be easier than in the early
    days, the average Fidonet sysop still is not an average internet
    consumer.

    I think at this point applications are accepted as long as applicants can make a binkp connection, and send a netmail. But, I would like to also hope that most of us have some kind of technical knowledge. I bet we'd both be surprised with what is really the case, though. ;)

    He.net has stopped giving away T-shirts many years ago, but I still
    have mine. I was very impressed that they managed to get it deliverd exactly on my birth day. A nice and welcome borthday present. :)

    I believe I was a sage at one point also, but never ordered a T-shirt.. or didn't know how to at the time. Eh well, that was the past and now I have reliable, native IPv6 so I don't have to think about that much any more.

    All in all 100 Fidonet sysops who's node supports IPv6 isn't really
    that bad.

    I agree. While there may be more nodelisted sysops than IPv6 systems, There's definitely less than 100 people that regularly participate in the English speaking side of Fidonet these days. So if the IPv6 list is bigger than that active participants list, I'd say it's doing pretty dang good.

    Considering that there is a substantial amount of dead wood in the nodelist. I regulatly test the systems in the IPv6 list for activity. Contrary to the nodelist in general the vast majority of systems in
    the IPv6 list are active Fidonet systems.

    Agreed here, too.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- SBBSecho 3.29-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
  • From Stas Mishchenkov@2:460/5858 to Michiel van der Vlist on Fri Jul 25 10:18:30 2025
    Hi Michiel!

    Thursday July 24 2025 12:33, you wrote to me:

    This is how it works for me. My own router, two ISPs at the same time
    and I know how to set it up. ;)

    MvdV> So how do you do it?

    By own hands. ;)

    MvdV> A outer with two WAN pots?

    Mikrotik hAP ac3. It can do any port to be WAN port.

    MvdV> You use a he.net tunnel. Does it work over both providers?

    Simultaneously - no.

    MvdV> And the two poviders, none of them supports native IPv6?

    One of them supports IPv6 DHCP and advertise me /64 network. From he.net I get /64 and /48 prefixes.

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Tommi Koivula@2:221/6 to Stas Mishchenkov on Fri Jul 25 19:34:15 2025
    Hello, Stas Mishchenkov.
    On 25/07/2025 9.18 you wrote:

    MvdV>> And the two poviders, none of them supports
    MvdV>> native IPv6?
    One of them supports IPv6 DHCP and advertise me
    /64 network. From he.net I get /64 and /48
    prefixes.

    My two isp's provide me dynamic /64. In addition to that, I have static /64 and /48 from he.net.

    Static is always nice. ;)


    --
    'Tommi

    ---
    * Origin: jamnntpd/lnx (2:221/6.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Fri Jul 25 22:40:28 2025
    Hello Tommi,

    On Friday July 25 2025 19:34, you wrote to Stas Mishchenkov:

    My two isp's provide me dynamic /64.

    Just a /64?

    In addition to that, I have
    static /64 and /48 from he.net.

    Static is always nice. ;)

    My fibre provider gives me a "persistent" IPv6 prefix. Technically it is not static, it is dynamic, but they say by making it "persistent" they follow best practice. It does not chance as long as the router does not change. And indeed it has not changed since my last router change.

    My coax provider offers a dynamic IPv6 pefix. It does not change very often, once or twice a year, but there is no discernable pattern. Sometimes with a firmware update but also sometimes without any traceable trigger.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Dan Clough@1:135/115 to Michiel van der Vlist on Sat Jul 26 08:37:22 2025
    Michiel van der Vlist wrote to Nick Boel <=-

    I think at this point applications are accepted as long as applicants
    can make a binkp connection, and send a netmail.

    Yes that seems to be the case. But once they are accepted, they are seldom checked again. If checked, only for a responding server, not for responding to netmail. So we have many ghost systems in the nodelist...

    I'd say that is the fault of the NC. There are no dead nodes in my Net.

    Still... As I mentioned before, when promoting IPv6 in Fidonet I sometimes run into a brick wall. The first brick wall is that of
    denial. No, denial is not a river in Egypt. (Roy Witt) IPv6 is a hype, there is noo need for it, IPv4 is functioning well and will remain to
    do so, if not for the rest of the century, then at least for the coming decades.

    Is there anything in the above paragraph that isn't true?

    That's correct, it's all true and factual.

    IPv4 exhaustion may not be a serious problem for the incumbents in
    parts of the world where IPv4 was historically issued as if it would
    last forever. But for newcomers getting enough IPv4 to give all their potential customers a globally routable IPv4 address is a serious problem. So serious that some of the newcomers in the fast gowing fibre glass sector here in Europe have stopped doing it.

    So..... here you are talking about "newcomer" ISP's? That doesn't have anything to do with individuals or FidoNet sysops. Are you trying to
    base your whole argument on the problems faced by a "new ISP company"?
    I mean, how many of those are there....? Nothing to do with FidoNet.



    ... So easy, a child could do it. Child sold separately.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.29-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
  • From Nick Boel@1:154/700 to Michiel van der Vlist on Sat Jul 26 09:38:53 2025
    Hey Michiel!

    On Sat, Jul 26 2025 02:06:38 -0500, you wrote:

    Yes that seems to be the case. But once they are accepted, they are
    seldom checked again. If checked, only for a responding server, not
    for responding to netmail. So we have many ghost systems in the
    nodelist...

    At this point, most *Cs should probably be trying to welcome new applicants with open arms, and even try to help them get setup. Long gone are the days of sifting through applications, giving some kind of robot response and once they're able to send/receive netmail, /allowing/ them to join. Now, while unfortunate, we are more at a point of desparation and hanging on to dying technology till the bitter end.

    I agree. While there may be more nodelisted sysops than IPv6
    systems, There's definitely less than 100 people that regularly
    participate in the English speaking side of Fidonet these days.

    Don't forget that these days many if not most messages in Fidonet are written in the Cyrillic alphabet...

    That was implied in the paragraph you replied to, which is why I mentioned the "English speaking side of Fidonet". I was only basing what I had said off what I see personally.

    Still... As I mentioned before, when promoting IPv6 in Fidonet I
    sometimes run into a brick wall. The first brick wall is that of
    denial. No, denial is not a river in Egypt. (Roy Witt) IPv6 is a
    hype, there is noo need for it, IPv4 is functioning well and will
    remain to do so, if not for the rest of the century, then at least
    for the coming decades.

    And you always will run into those walls. This is somewhat comparable to sysops that still wish to run BBS software from the 80s/90s, that don't and will never support things like a TZUTC kludge. It's ultimately their choice.

    For those confronted with te reality of IPv4 exhaustion and the
    shattered brick wall of denial, there is brick wall #2. Hang on to
    IPv4 no matter what tricks it needs.

    Some people don't like change, until they're ultimately forced to do so. If IPv4 is ever fully phased out, my guess is Fidonet will lose another big chunk of nodelisted sysops. Much like when darktech.org and no-ip.com were abandoned, but on a bigger scale.

    IPv4 exhaustion may not be a serious problem for the incumbents in
    parts of the world where IPv4 was historically issued as if it would
    last forever.

    I imagine some of these bigger ISPs, mine included (Spectrum), bought up a ton of IPv4 blocks because they saw all of this coming and could afford to take it all away from smaller ISPs for themselves. Heck, there may even be enough IPv4 addresses at these large ISPs to go around still, but they are hoarding them for their own (current and future) customers.

    While I don't follow the situation very much, nor do I have any experience with it (I have native "dynamic that never changes unless I change hardware" IPv4 that I have always had, as well as native "dynamic that never changes unless I change hardware" IPv6), but do you think these bigger ISPs rent out some IPv4 addresses to smaller ISPs just so they can do said DSLite kind of setups?

    Is this DSLite setup a bunch of private addresses not open to the outside, that run off of one or a few public addresses so they basically disable any incoming traffic so they can make more use of a single IPv4 address?

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- SBBSecho 3.29-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
  • From Wilfred van Velzen@2:280/464 to Dan Clough on Sat Jul 26 17:46:22 2025
    Hi Dan,

    On 2025-07-26 08:37:22, you wrote to Michiel van der Vlist:

    Yes that seems to be the case. But once they are accepted, they are
    seldom checked again. If checked, only for a responding server, not
    for responding to netmail. So we have many ghost systems in the
    nodelist...

    I'd say that is the fault of the NC. There are no dead nodes in my Net.

    Maybe some temporary problems:

    1:135/363 cjsplace.thruhere.net:24554 65.32.142.239 Error: Connection timed out
    1:135/366 localyocalbbs.com:24554 2603:9000:7006:16f4:590c:41dc:56d3:4531 Error: Connection timed out
    1:135/366 localyocalbbs.com:24554 72.185.52.20 Error: Connection timed out


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Björn Felten@2:203/2 to Michiel van der Vlist on Sat Jul 26 17:53:45 2025
    Michiel van der Vlist -> Nick Boel skrev 2025-07-26 09:06:
    MvdV> IPv6 is a hype, there is noo need for it, IPv4 is functioning well and
    MvdV> will remain to do so, if not for the rest of the century, then at least
    MvdV> for the coming decades.

    Almost sounds like the last famous words from flip phone owners when smartphones arrived.


    --

    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 Tommi Koivula@2:221/6 to Michiel van der Vlist on Sat Jul 26 21:48:32 2025
    Hello, Michiel van der Vlist.
    On 25/07/2025 22.40 you wrote:

    Static is always nice. ;)
    My fibre provider gives me a "persistent" IPv6
    prefix. Technically it is not static, it is
    dynamic, but they say by making it "persistent"
    they follow best practice. It does not chance as
    long as the router does not change. And indeed
    it has not changed since my last router change.
    My coax provider offers a dynamic IPv6 pefix. It
    does not change very often, once or twice a
    year, but there is no discernable pattern.
    Sometimes with a firmware update but also
    sometimes without any traceable trigger.

    But not static. ;)


    --
    'Tommi

    ---
    * Origin: jamnntpd/lnx (2:221/6.0)
  • From Tommi Koivula@2:221/6 to Michiel van der Vlist on Sat Jul 26 21:48:32 2025
    Hello, Michiel van der Vlist.
    On 26/07/2025 11.43 you wrote:

    Hello Tommi, On Friday July 25 2025 19:34, you
    wrote to Stas Mishchenkov:
    Static is always nice. ;)
    Not always. It depends... My fibre provider
    (Delta) issues by default a "static" IPv4 address
    to new customers. In the range 100.64.0.0/10.

    I thought we were talking about ipv6..

    --
    'Tommi

    ---
    * Origin: jamnntpd/lnx (2:221/6.0)
  • From Nick Boel@1:154/700 to =?UTF-8?Q?Bj=C3=B6rn?= Felten on Sat Jul 26 16:50:49 2025
    Hey Björn!

    On Sat, Jul 26 2025 10:53:45 -0500, you wrote:

    Almost sounds like the last famous words from flip phone owners
    when smartphones arrived.

    Oddly enough, I still know a couple people with analog flip phones, but other than that, the "retro" aspect has been back for awhile, with Samsung's smart flip phones. Now Google Pixel and Apple have followed suit.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- SBBSecho 3.29-Linux
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
  • From Stas Mishchenkov@2:460/5858 to Michiel van der Vlist on Fri Aug 1 14:41:38 2025
    Hi Michiel!

    Tuesday July 29 2025 09:59, you wrote to me:


    MvdV> How is the physical setup? Having two providers to avois loss of
    MvdV> connection when a vable is cut does not work if the risk of cutting both
    MvdV> cables in the same operation is substantial. Here the various cables are
    MvdV> usually laid close together for easier access. But that increases the
    MvdV> risk of cutting more than one when something goes wrong.

    In my case, this does not work. Different ISPs enter my area from different directions. A power outage is much worse for me, since I do not have the physical ability to provide myself with two independent power supply beams, and a UPS that provides several hours of operation for my equipment would be unacceptably expensive.

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Michiel van der Vlist on Sat Aug 2 15:50:20 2025
    Hi Michiel!

    Saturday August 02 2025 11:18, you wrote to me:

    MvdV>>> How is the physical setup? Having two providers to avois loss
    MvdV>>> of connection when a vable is cut does not work if the risk of
    MvdV>>> cutting both cables in the same operation is substantial. Here
    MvdV>>> the various cables are usually laid close together for easier
    MvdV>>> access. But that increases the risk of cutting more than one
    MvdV>>> when something goes wrong.

    In my case, this does not work. Different ISPs enter my area from
    different directions.

    MvdV> So what are the physical media? DSL? Coax? Fibre?

    The main channel with a capacity of 1 gigabit is fiber optics, the backup channel with a capacity of 100 megabits is twisted pair.

    MvdV> From what I see here, I guess you are still tuning the system and
    MvdV> attempting to make it dual homed.

    I hoped that I had finished the experiments by now.

    MvdV> At the moment IPv6 does not work. When
    MvdV> I try to connect to your systems, my binks first tries the he.net
    MvdV> tunnel. Result: time out. Then your native iPv6 connection. Result: also
    MvdV> time out. Then it tries 193.107.113.122 and it connects. 460/5858 is
    MvdV> unreachable.

    It's strange.

    [15:49:21 brorabbit logs]$ grep -c "incoming session" ./binkd.log |grep -v "\." 2848

    i.e. 2848 incoming IPv6 sessions from midnight.

    But I see the same.

    === Import Windows Clipboard Start ===
    + 02 Aug 15:40:09 [512677] call to 2:280/5555@fidonet
    02 Aug 15:40:09 [512677] trying fido.vlist.eu [2001:1c02:1100:f00:f1d0:2:280:5555]...
    ? 02 Aug 15:42:19 [512677] connection to 2:280/5555@fidonet failed: Connection timed out
    02 Aug 15:42:19 [512677] trying fido.vlist.eu [2001:4c3c:7d02:ff00:f1d0:2:280:5555]:24554...
    ? 02 Aug 15:44:30 [512677] connection to 2:280/5555@fidonet failed: Connection timed out
    02 Aug 15:44:30 [512677] trying fido.vlist.eu [83.80.243.26]:24554...
    02 Aug 15:44:30 [512677] connected
    + 02 Aug 15:44:30 [512677] outgoing session with fido.vlist.eu:24554 [83.80.243.26]
    - 02 Aug 15:44:35 [512677] OPT CRAM-MD5-447ceb9c09876fb42fc83d3402806eee
    + 02 Aug 15:44:35 [512677] Remote requests MD mode
    - 02 Aug 15:44:35 [512677] SYS Nieuw Schnoord
    - 02 Aug 15:44:35 [512677] ZYZ Michiel van der Vlist
    === Import Windows Clipboard End ===

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Michiel van der Vlist on Wed Aug 13 17:55:40 2025
    Hi Michiel!

    Saturday August 02 2025 11:18, you wrote to me:

    MvdV> From what I see here, I guess you are still tuning the system and
    MvdV> attempting to make it dual homed. At the moment IPv6 does not work.
    MvdV> When I try to connect to your systems, my binks first tries the
    MvdV> he.net tunnel. Result: time out. Then your native iPv6 connection.
    MvdV> Result: also time out. Then it tries 193.107.113.122 and it
    MvdV> connects. 460/5858 is unreachable.

    It's not my fall. :(

    [17:54:27 brorabbit ~]$ traceroute -6 2001:1c02:1100:f00:f1d0:2:280:5555 traceroute to 2001:1c02:1100:f00:f1d0:2:280:5555 (2001:1c02:1100:f00:f1d0:2:280:5555), 30 hops max, 80 byte packets
    1 2a0b:db80:86:150::10 (2a0b:db80:86:150::10) 0.934 ms 0.888 ms 0.864 ms
    2 fc00:1::1 (fc00:1::1) 1.914 ms 1.914 ms 1.827 ms
    3 2001:67c:2dfc:fff2::209 (2001:67c:2dfc:fff2::209) 1.969 ms 1.877 ms 1.878 ms
    4 2a02:2518:0:44:0:4800:4:1 (2a02:2518:0:44:0:4800:4:1) 14.059 ms 13.945 ms 13.654 ms
    5 2a02:2518:1:a:544::1 (2a02:2518:1:a:544::1) 28.476 ms 28.361 ms 28.487 ms
    6 2a02:2518:1:23:547::2 (2a02:2518:1:23:547::2) 50.666 ms 48.811 ms 52.636 ms
    7 e0-12.core2.sto1.he.net (2001:470:0:378::1) 50.774 ms 52.605 ms 46.630 ms
    8 * * *
    9 * * *
    10 * * *
    11 libertyglobal-as6830.port-channel9.core2.fra1.he.net (2001:470:0:481::2) 65.960 ms 64.603 ms 64.046 ms
    12 de-fra02a-rc1-lo0-0.v6.aorta.net (2001:730:2d00::5474:80dc) 76.794 ms 73.301 ms 73.399 ms
    13 2001:730:2200::5474:8025 (2001:730:2200::5474:8025) 71.792 ms 71.344 ms 70.105 ms
    14 2001:730:2200::5474:802c (2001:730:2200::5474:802c) 73.334 ms 71.508 ms 68.224 ms
    15 asd-rc0001-cr101-be60-2.core.as9143.net (2001:b88:0:400::1) 67.422 ms 69.203 ms 67.340 ms
    16 mnd-rc0001-cr101-et120-601.core.as33915.net (2001:b88:0:d8c::1) 74.930 ms 73.816 ms 71.364 ms
    17 * * *
    18 2001-1c02-1100-0000-b12b-4a28-c437-79c5.cable.dynamic.v6.ziggo.nl (2001:1c02:1100:0:b12b:4a28:c437:79c5) 82.858 ms 76.933 ms 82.037 ms
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    My he.net addresses will be removed from DNS records.

    Have a nice night.
    Stas Mishchenkov.

    --- Have You daily sexual life? Hide it proper from Your wife! ;)
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Michiel van der Vlist@2:280/5555 to Konstantin Kuzov on Sat Aug 16 16:16:48 2025
    Hello Konstantin,

    On Saturday August 16 2025 02:25, you wrote to me:


    It's not my fall. :(

    MvdV>> I can't find anything wrong at this side either, so it remains
    MvdV>> a mystery why the IPv6 connection with your system is so
    MvdV>> unstable.

    Tunnelbroker nowadays is not what it used to be.

    I do not connect to Stas via a he.net tunnel. He recently got a native IOv6 connection and that is what we were discussing here.

    Amsterdam POP is long over-capacity and you can't even request new
    tunnel there. It has jitter up to 3x times the latency and constant
    packet loss around 3-5% inside HE network.

    Be that as it may be, I have no issues connecting with your system.

    Having said that...

    Couple of months ago it was even worse as there was constant 20-40%
    packet loss for months and couple of days long complete outages. Other more close to me POPs like Stockholm are even worse as despite lower latency jitter and packet loss there even bigger and they often
    partially or completely lose connectivity even to main HE network and becomes isolated.

    It was to be expected that this wonderfull service would not last forever. Time to put pressure on your ISP to go support native IPv6!


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)