• New One

    From Michiel van der Vlist@2:280/5555 to All on Fri Oct 11 16:54:09 2019
    Hello All,

    We have a new one:

    81 2:243/39 Karl Kral Native WEDOS

    Karl, your system still needs a bit of tuning. Sometimes an attempt to connect at IPv6 times out and an IPv4 connect results. Sometimes it takes a while but there is an IPv6 connect anyway. Sometimes there is an IPv6 connect right away.

    I have no idea what this is. It looks like IPv6 needs to be "woken up".

    Suggestions anyone?

    Anyway: Karl, welcome to the Fidonet IPv6 club!


    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 Oct 11 19:41:26 2019
    On Fri, 11 Oct 2019 13:54:08 GMT Michiel van der Vlist <0@5555.280.2> wrote:

    We have a new one:

    81 2:243/39 Karl Kral Native WEDOS

    I believe you mean 2:423/39.

    Karl, your system still needs a bit of tuning. Sometimes an attempt to connect at IPv6 times out and an IPv4 connect results. Sometimes it
    takes a while but there is an IPv6 connect anyway. Sometimes there is an
    IPv6 connect right away.

    I noticed that too. Over 1 minute.

    11 Oct 19:28:14 [14632] Substituted * to f39.n423.z2.binkp.net. for 2:423/39@fidonet by nodelist
    + 11 Oct 19:28:14 [14632] call to 2:423/39@fidonet
    11 Oct 19:28:14 [14632] trying f39.n423.z2.binkp.net. [2a02:2b88:2:1::68e3:1]...
    11 Oct 19:29:18 [14632] connected
    + 11 Oct 19:29:18 [14632] outgoing session with f39.n423.z2.binkp.net:24554 [2a02:2b88:2:1::68e3:1]
    - 11 Oct 19:29:18 [14632] OPT CRAM-MD5-7eaa2f13af5fa559d7c478c3d733e2ee
    + 11 Oct 19:29:18 [14632] Remote requests MD mode
    - 11 Oct 19:29:18 [14632] SYS Plast DATA

    Suggestions anyone?

    -46 :)

    'Tommi

    --- Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
    * Origin: smapinntpd/linux @ nntps://news.fidonet.fi (2:221/6.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Fri Oct 11 19:58:05 2019
    Hello Tommi,

    On Friday October 11 2019 19:41, you wrote to me:

    We have a new one:

    81 2:243/39 Karl Kral Native WEDOS

    I believe you mean 2:423/39.

    Yes. I stand corrected.

    Suggestions anyone?

    -46 :)

    hmm... I was hoping for suggestions that would help him improve his IPv6 connectivity...


    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 Oct 11 21:45:21 2019
    On 11.10.2019 20:58, Michiel van der Vlist : Tommi Koivula :

    81 2:243/39 Karl Kral Native WEDOS

    I believe you mean 2:423/39.

    Yes. I stand corrected.

    You may also want check the spelling of his first name.

    Suggestions anyone?

    -46 :)

    hmm... I was hoping for suggestions that would help him improve his IPv6
    connectivity...

    I know. :)

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.
    * Origin: - nntp://rbb.fidonet.fi - Lake Ylo - Finland - (2:221/360)
  • From Michiel van der Vlist@2:280/5555 to All on Fri Mar 6 21:47:24 2020
    Hello All,

    We have a new one:

    90 1:218/820 Ryan Fantus Native DigitalOcean

    Ryan, welcome to the Fidonet IPv6 club.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Ryan Fantus@1:218/820 to Michiel van der Vlist on Fri Mar 6 13:40:01 2020
    Ryan, welcome to the Fidonet IPv6 club.

    Thanks! Happy to be here.

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
    * Origin: monterey bbs (1:218/820)
  • From Alan Ianson@1:153/757 to Michiel van der Vlist on Fri Mar 6 13:55:54 2020
    Hello Michiel,

    We have a new one:

    There is another at 1:153/146 also.. :)

    Ttyl :-),
    Al

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Michiel van der Vlist@2:280/5555 to Alan Ianson on Fri Mar 6 23:34:57 2020
    Hello Alan,

    On Friday March 06 2020 13:55, you wrote to me:

    There is another at 1:153/146 also.. :)

    Ah, I did't know about that one yet. Thank you for pointing it out.

    91 1:153/146 Erich Bublitz Native LINODE-US

    Erich, welcome to the Fidonet IPv6 club!


    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 All on Mon Nov 16 10:57:24 2020
    Hello All,

    + 10:55 [1308] call to 2:240/5824@fidonet
    10:55 [1308] trying f5824.n240.z2.binkp.net [2001:470:540b:0:ba27:ebff:fef1:42dc]...
    10:55 [1308] connected
    + 10:55 [1308] outgoing session with f5824.n240.z2.binkp.net:24554
    [2001:470:540b:0:ba27:ebff:fef1:42dc]
    - 10:55 [1308] OPT CRAM-MD5-30a0ae251c5d39a0b0976b61e5cce690
    + 10:55 [1308] Remote requests MD mode
    - 10:55 [1308] SYS Imzadi Box
    - 10:55 [1308] ZYZ Christina Nass

    Christina, welcome to the Fidonet IPv6 club.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824 to Michiel van der Vlist on Mon Nov 16 11:40:56 2020
    Hi Michiel,

    Christina, welcome to the Fidonet IPv6 club.

    Thank you! :)
    I might change the IPv6 address soon to one that includes F1D0 :)
    (the DNS name will stay the same, of course)

    Regards,
    Anna

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Imzadi Box (2:240/5824)
  • From Anna Christina Nass@2:240/5824 to Michiel van der Vlist on Mon Nov 16 11:43:51 2020
    Hi,

    I might change the IPv6 address soon to one that includes F1D0 :)
    (the DNS name will stay the same, of course)

    I just saw that the DNS name you used ends in binkp.net...
    Who is administering these records?
    Thank you!

    Regards,
    Anna

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Imzadi Box (2:240/5824)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Mon Nov 16 12:23:38 2020
    Hello Anna,

    On Monday November 16 2020 11:40, you wrote to me:

    Christina, welcome to the Fidonet IPv6 club.

    Thank you! :)

    You'r welcome.

    I might change the IPv6 address soon to one that includes F1D0 :)

    When you do, I will update the list.

    (the DNS name will stay the same, of course)

    Regards,
    Anna

    I am confused... The nodelist says "Christina Nass" and so does your binkp server. How do we call you and how do you want to be listed in the list of IPv6 nodes?

    Is "Anna Christina Nass" OK with you?


    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 Anna Christina Nass on Mon Nov 16 12:28:32 2020
    Hello Anna,

    On Monday November 16 2020 11:43, you wrote to me:

    I just saw that the DNS name you used ends in binkp.net...
    Who is administering these records?

    The domain binkp.net is maintained by Pavel Gulchouk (2:463/68)

    f5824.n240.z2.binkp.net is a CNAME of box.imzadi.de. It is updated daily from the daily nodelist. See FTS-5004.001.

    http://ftsc.org/docs/fts-5004.001


    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 Anna Christina Nass on Mon Nov 16 12:54:36 2020
    Hello Anna,

    BTW your IPv6 address does not ping:

    D:\FIDO\IPV6>ping box.imzadi.de

    Ping box.my.imzadi.de [2001:470:540b:0:ba27:ebff:fef1:42dc] mit 32 Bytes Daten:

    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.

    Ping-Statistik fr 2001:470:540b:0:ba27:ebff:fef1:42dc:
    Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

    You may want to open your IPv6 firewall for PING. (And some other ICMP thingies)


    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 Mon Nov 16 14:26:32 2020

    BTW your IPv6 address does not ping:

    D:\FIDO\IPV6>ping box.imzadi.de

    Ping box.my.imzadi.de [2001:470:540b:0:ba27:ebff:fef1:42dc] mit 32 Bytes
    Daten:

    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.

    Ping-Statistik für 2001:470:540b:0:ba27:ebff:fef1:42dc:
    Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

    You may want to open your IPv6 firewall for PING. (And some other ICMP
    thingies)

    Ping is not needed for binkp connections. Also telnet to her bbs works
    fine.

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
    * Origin: nntps://news.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Mon Nov 16 14:31:30 2020
    Hi Michiel.

    16 Nov 20 14:26:32, I wrote to you:


    BTW your IPv6 address does not ping:

    D:\FIDO\IPV6>ping box.imzadi.de

    Ping box.my.imzadi.de [2001:470:540b:0:ba27:ebff:fef1:42dc] mit 32
    Bytes Daten:

    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.
    Zielprotokoll nicht erreichbar.

    Ping-Statistik für 2001:470:540b:0:ba27:ebff:fef1:42dc:
    Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100%
    Verlust),

    You may want to open your IPv6 firewall for PING. (And some other
    ICMP thingies)

    Ping is not needed for binkp connections. Also telnet to her bbs
    works fine.

    Even it is a Pvt node and no CM flag. :)

    'Tommi

    ... he.net certified sage
    ---
    * Origin: - rbb.fidonet.fi - Finland - (2:221/360)
  • From Alexey Vissarionov@2:5020/545 to Anna Christina Nass on Mon Nov 16 15:30:30 2020
    Good ${greeting_time}, Anna!

    16 Nov 2020 11:43:50, you wrote to Michiel van der Vlist:

    I might change the IPv6 address soon to one that includes F1D0 :)
    (the DNS name will stay the same, of course)
    I just saw that the DNS name you used ends in binkp.net...
    Who is administering these records?

    binkp.net is a sort of DDN, so it _must_ _not_ (*) appear in the nodelist.
    In general, DDNs should not (*) be used for any persistent links.


    (*) as in FTA-1006.

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

    ... :wq!
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Alexey Vissarionov@2:5020/545 to Tommi Koivula on Mon Nov 16 15:33:00 2020
    Good ${greeting_time}, Tommi!

    16 Nov 2020 14:26:32, you wrote to Michiel van der Vlist:

    BTW your IPv6 address does not ping:
    You may want to open your IPv6 firewall for PING. (And some other ICMP
    thingies)
    Ping is not needed for binkp connections. Also telnet to her bbs works fine.

    Blocking ICMP (including ping) is dangerous: this tells possible hackers the administrator of such network is mentally impaired.


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

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Mon Nov 16 13:32:43 2020
    Hello Tommi,

    On Monday November 16 2020 14:26, you wrote to me:


    You may want to open your IPv6 firewall for PING. (And some other
    ICMP thingies)

    Ping is not needed for binkp connections.

    I know it is not needed. But I find it exciting that devices in the LAN can be individually IPv6 pinged from the outside.

    Some say this is a security risk. I think the risk is minimal.

    Note that although ping is not needed, blocking all IPv6 ICMP has negative effects.

    Also telnet to her bbs works fine.

    Good.


    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 Alexey Vissarionov on Mon Nov 16 13:45:53 2020
    Hello Alexey,

    On Monday November 16 2020 15:33, you wrote to Tommi Koivula:

    Blocking ICMP (including ping) is dangerous: this tells possible
    hackers the administrator of such network is mentally impaired.

    Or (s)he is saddled with a broken router from the ISP.

    Which may also be an interesting target for a hacker...


    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 Anna Christina Nass on Mon Nov 16 14:25:37 2020
    Hello Anna,

    Another question pops up:

    I see you use a he.net tunnel.

    he.net is doing a fine job by providing this service. I have used it for many years.

    I see your IPv4 address is from DTAG. DTAG provides native IPv6 to (some?) of its customers. There are two German Fidonet sysops that have native IPv6 from DTAG.

    You do not have native IPv6 from DTAG or is there another reason you use a he.net tunnel?

    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:250/1 to Michiel van der Vlist on Mon Nov 16 14:49:42 2020
    Hallo Michiel,

    I might change the IPv6 address soon to one that includes F1D0 :)
    When you do, I will update the list.

    Okay, thank you!

    Regards,
    Anna
    I am confused... The nodelist says "Christina Nass" and so does your
    binkp server. How do we call you and how do you want to be listed in the list of IPv6 nodes?
    Is "Anna Christina Nass" OK with you?

    Yes, this is my full name and I think it should be changed in the nodelist. That's already on my to-do list :)
    I've changed the BinkP entry :)

    Regards,
    Anna

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Imzadi Box
  • From Anna Christina Nass@2:240/5824 to Alexey Vissarionov on Mon Nov 16 14:54:41 2020
    Hi,

    BTW your IPv6 address does not ping:
    You may want to open your IPv6 firewall for PING. (And some other ICMP
    thingies)

    I've enabled PING6 now for this host...

    Blocking ICMP (including ping) is dangerous: this tells possible hackers the administrator of such network is mentally impaired.

    ...because being "mentally impaired" is nothing that anyone should have to think about me.

    Regards,
    Anna

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Imzadi Box (2:240/5824)
  • From Anna Christina Nass@2:240/5824 to Michiel van der Vlist on Mon Nov 16 14:58:45 2020
    Hallo Michiel,

    I see you use a he.net tunnel.
    I see your IPv4 address is from DTAG. DTAG provides native IPv6 to
    (some?) of its customers. There are two German Fidonet sysops that have native IPv6 from DTAG.
    You do not have native IPv6 from DTAG or is there another reason you use
    a he.net tunnel?

    Yep, this is my configuration :)

    I chose this, as my DTAG DSL connection would indeed offer a Dual-Stack IP connection, but the IPv6 prefix is not fixed and could change at any time - kind of like the IPv4 address.
    And thus I would need dynamic DNS not only for IPv4 but also for IPv6...
    So I chose to stay with my he.net tunnel -- which also allows me to specify reverse DNS servers.
    I don't know if that is even remotely possible for a private DTAG DSL connection...

    Regards,
    Anna

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Imzadi Box (2:240/5824)
  • From Michiel van der Vlist@2:280/5555 to Anna Christina Nass on Mon Nov 16 15:09:09 2020
    Hello Anna,

    On Monday November 16 2020 14:54, you wrote to Alexey Vissarionov:

    I've enabled PING6 now for this host...

    D:\FIDO6\BINKD>ping box.imzadi.de

    Ping box.my.imzadi.de [2001:470:540b:0:ba27:ebff:fef1:42dc] mit 32 Bytes Daten:

    Antwort von 2001:470:540b:0:ba27:ebff:fef1:42dc: Zeit=74ms
    Antwort von 2001:470:540b:0:ba27:ebff:fef1:42dc: Zeit=66ms
    Antwort von 2001:470:540b:0:ba27:ebff:fef1:42dc: Zeit=63ms
    Antwort von 2001:470:540b:0:ba27:ebff:fef1:42dc: Zeit=91ms

    Ping-Statistik fr 2001:470:540b:0:ba27:ebff:fef1:42dc:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
    Ca. Zeitangaben in Millisek.:
    Minimum = 63ms, Maximum = 91ms, Mittelwert = 73ms

    Check!


    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 Anna Christina Nass on Mon Nov 16 15:42:22 2020
    Hello Anna,

    On Monday November 16 2020 14:58, you wrote to me:

    I chose this, as my DTAG DSL connection would indeed offer a
    Dual-Stack IP connection, but the IPv6 prefix is not fixed and could change at any time - kind of like the IPv4 address.

    Aha. How often does it change? I too have dynamic addresses, In theory. My IPv4 address has been stable for almost two years now. It only changes when the MAC address of the CPE changes. It can be stable for years. The IPv6 prefix changes a bit more often and there is no visible pattern. But it is only twice a year or so. Not often enough to bother with dyndns. On the rare occasion that it changes, I just update it manually. For a hobby system it is no big deal if IPv6 is occasionally down for a few hours.

    And thus I would need dynamic DNS not only for IPv4 but also for
    IPv6... So I chose to stay with my he.net tunnel

    For IPv6 it is more difficult than for IPv4. When my ISP started offering native IPv6 some four years ago, I had to make a choice. As it is they only offer native IPv6 if you use their cable modem/router. That router does not support tunnels. The he.net tunnel did a fine job, but I never got more than half the IPv4 speed. With native IPv6 I have the full speed. So I dropped the tunnel and went native IPv6 despite the minor inconvienence of a dynamic IPv6 prefix.

    -- which also allows me to specify reverse DNS servers. I don't know
    if that is even remotely possible for a private DTAG DSL connection...

    I don't have to worry about reverse DNS. My ISP does that for me. ;-)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Anna Christina Nass@2:240/5824 to Michiel van der Vlist on Mon Nov 16 17:36:02 2020
    Hallo Michiel,

    Aha. How often does it change? I too have dynamic addresses, In theory.
    (...)
    For a hobby system it is no big deal if IPv6 is occasionally
    down for a few hours.

    Well, that is true, yes. But I want my setup to be stable and reliable - and thus I went this way and won't change it any time soon :)

    (DynDNS)
    For IPv6 it is more difficult than for IPv4.

    A little, maybe. At least if you use "standard" DynDNS providers.
    Recently, I changed my setup so that I'm my own DynDNS provider for most of
    my needs. Thus, "box.imzadi.de" is a CNAME entry for "box.my.imzadi.de", and the nameserver for the "my.imzadi.de" domain is on my vServer and this gets
    the new IP at every change from my home router.

    The he.net tunnel did a fine job, but I never
    got more than half the IPv4 speed.

    Oh, I don't notice any real slowdown here, it is "fast enough" for my needs :)

    Regards,
    Anna

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Imzadi Box (2:240/5824)
  • From Stas Mishchenkov@2:460/5858 to Anna Christina Nass on Mon Nov 16 20:40:22 2020
    Hi Anna!

    Monday November 16 2020 11:43, you wrote to Michiel van der Vlist:

    I might change the IPv6 address soon to one that includes F1D0 :)
    (the DNS name will stay the same, of course)

    I just saw that the DNS name you used ends in binkp.net...
    Who is administering these records?

    You can register the same on https://binkp.net/

    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 Anna Christina Nass on Mon Nov 16 19:38:57 2020
    Hello Anna,

    On Monday November 16 2020 17:36, you wrote to me:

    For a hobby system it is no big deal if IPv6 is occasionally
    down for a few hours.

    Well, that is true, yes. But I want my setup to be stable and reliable
    - and thus I went this way and won't change it any time soon :)

    In my Fidonews articles I have speculated about he.net's lifetime. Nothing is forever and he.net's free tunnel service will not be the exception. Xs4All sunset was three years ago. Jeroen Massar and Pim van Pelt just got tired of it. There are no indications that he.net will follow any time soon, but one never knows. DynDNS has stopped its free service and now wants money for it.

    My experience is that - expecially with free services - it is always good to have a plan B.

    (DynDNS)
    For IPv6 it is more difficult than for IPv4.

    A little, maybe. At least if you use "standard" DynDNS providers. Recently, I changed my setup so that I'm my own DynDNS provider for
    most of my needs. Thus, "box.imzadi.de" is a CNAME entry for "box.my.imzadi.de", and the nameserver for the "my.imzadi.de" domain
    is on my vServer and this gets the new IP at every change from my home router.

    Ah, you run your own name server. Interesting...

    You could do the same or something similar for IPv6 couldn't you?

    The he.net tunnel did a fine job, but I never
    got more than half the IPv4 speed.

    Oh, I don't notice any real slowdown here, it is "fast enough" for my needs :)

    It was fast enough for my needs too, but it bothered me that I never found out *why* it was slow. Others got much better results.

    Well, I got the T-shirt. And you know what? he.net managed to have it delivered exactly on my birthday. That was nice. ;-)

    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 Anna Christina Nass on Tue Nov 17 00:15:10 2020
    Hello Anna,

    Monday November 16 2020 19:38, I wrote to you:

    Xs4All sunset was three years ago.

    SixXs of course. Mixed up the Xxxses...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Richard Menedetter@2:310/31 to Anna Christina Nass on Tue Nov 17 08:48:06 2020
    Hi Anna!

    16 Nov 2020 14:58, from Anna Christina Nass -> Michiel van der Vlist:

    I don't know if that is even remotely possible for a private DTAG DSL connection...

    Yes ... definitely not doable with the DTAG IPv6.

    CU, Ricsi

    ... Television was not meant to be the sole educator of our children.
    --- GoldED+/LNX
    * Origin: Rumour: NT means Not Tested? (2:310/31)
  • From Richard Menedetter@2:310/31 to Michiel van der Vlist on Tue Nov 17 08:50:08 2020
    Hi Michiel!

    16 Nov 2020 15:42, from Michiel van der Vlist -> Anna Christina Nass:

    I chose this, as my DTAG DSL connection would indeed offer a
    Dual-Stack IP connection, but the IPv6 prefix is not fixed and
    could change at any time - kind of like the IPv4 address.
    Aha. How often does it change? I too have dynamic addresses, In
    theory. My IPv4 address has been stable for almost two years now. It
    only changes when the MAC address of the CPE changes. It can be stable
    for years. The IPv6 prefix changes a bit more often and there is no visible pattern. But it is only twice a year or so. Not often enough
    to bother with dyndns. On the rare occasion that it changes, I just
    update it manually. For a hobby system it is no big deal if IPv6 is occasionally down for a few hours.

    Same here with my Cable connection.
    Dynamic IP that changed 2 times in 22 years ;)

    But I know that DTAG has even a page, where you can trigger an IPv6 network prefix change.
    But they also do it periodically.
    Some of their customers see it as a "privacy" feature.

    CU, Ricsi

    ... Engineering is the art of making what you want from things you can get.
    --- GoldED+/LNX
    * Origin: I always do what the little voices tell me to do. (2:310/31)
  • From Tony Langdon@3:633/410 to Tommi Koivula on Tue Nov 17 18:47:00 2020
    On 11-16-20 14:26, Tommi Koivula wrote to Michiel van der Vlist <=-

    You may want to open your IPv6 firewall for PING. (And some other ICMP
    thingies)

    Ping is not needed for binkp connections. Also telnet to her bbs works fine.

    But from what I recall, IPv6 is even more dependent on properly working ICMP than IPv4, so even if ping is blocked, other ICMP needs to be allowed.


    ... Gone crazy, be back later, please leave message.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Michiel van der Vlist@2:280/5555 to Richard Menedetter on Tue Nov 17 10:31:05 2020
    Hello Richard,

    On Tuesday November 17 2020 08:48, you wrote to Anna Christina Nass:

    I don't know if that is even remotely possible for a private DTAG
    DSL connection...

    Yes ... definitely not doable with the DTAG IPv6.

    Reverse DNS is not needed for binkp connections. (in "Tommi style") :-)

    I get incoming IPv6 from about a dozen systems. Some addresses backresolve and some do not. In my SixXs/he.net time I never bothered to configure reverse DNS...


    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 Tue Nov 17 11:57:48 2020
    On 17.11.2020 10:31, Michiel van der Vlist - Richard Menedetter :

    Hello Richard,

    On Tuesday November 17 2020 08:48, you wrote to Anna Christina Nass:

    I don't know if that is even remotely possible for a private DTAG
    DSL connection...

    Yes ... definitely not doable with the DTAG IPv6.

    Reverse DNS is not needed for binkp connections. (in "Tommi style") :-)

    What's that style?

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
    * Origin: nntps://news.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Tommi Koivula@2:221/360 to Tony Langdon on Tue Nov 17 11:58:40 2020
    On 17.11.2020 18:47, Tony Langdon - Tommi Koivula :

    On 11-16-20 14:26, Tommi Koivula wrote to Michiel van der Vlist <=-

    You may want to open your IPv6 firewall for PING. (And some other ICMP
    thingies)

    Ping is not needed for binkp connections. Also telnet to her bbs works fine.

    But from what I recall, IPv6 is even more dependent on properly working ICMP than IPv4, so even if ping is blocked, other ICMP needs to be allowed.

    So true.

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
    * Origin: nntps://news.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Tue Nov 17 12:08:06 2020
    On 16.11.2020 15:42, Michiel van der Vlist - Anna Christina Nass :

    I don't have to worry about reverse DNS. My ISP does that for me. ;-)

    But you cannot control it.

    + 17 Nov 11:35:28 [7821] incoming session with 2001:1c02:1102:ac00:f1d0:2:280:5555
    + 17 Nov 11:35:28 [7821] addr: 2:280/5555@fidonet

    host 2001:1c02:1102:ac00:f1d0:2:280:5555 5.5.5.5.0.8.2.0.2.0.0.0.0.d.1.f.0.0.c.a.2.0.1.1.2.0.c.1.1.0.0.2.ip6.arpa
    domain name pointer 2001-1c02-1102-ac00-f1d0-0002-0280-5555.cable.dynamic.v6.ziggo.nl.

    See. It is not fido.vlist.eu :)

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
    * Origin: nntps://news.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Tue Nov 17 11:39:22 2020
    Hello Tommi,

    On Tuesday November 17 2020 12:08, you wrote to me:

    I don't have to worry about reverse DNS. My ISP does that for me. ;-)

    But you cannot control it.

    I am not a control freak. ;-)

    + 17 Nov 11:35:28 [7821] incoming session with 2001:1c02:1102:ac00:f1d0:2:280:5555
    + 17 Nov 11:35:28 [7821] addr: 2:280/5555@fidonet

    host 2001:1c02:1102:ac00:f1d0:2:280:5555 5.5.5.5.0.8.2.0.2.0.0.0.0.d.1.f.0.0.c.a.2.0.1.1.2.0.c.1.1.0.0.2.ip6.ar
    pa domain name
    pointer 2001-1c02-1102-ac00-f1d0-0002-0280-5555.cable.dynamic.v6.ziggo .nl.

    See. It is not fido.vlist.eu :)

    I know. It is still better than how you come in:

    - 06 Nov 01:03:24 [1228] incoming from 2001:999:93:5fa::15 (60628)
    + 06 Nov 01:03:24 [2676] Error in getnameinfo(): Der angeforderte Name ist
    gltig und wurde in der Datenbank gefunden. Er
    verfgt jedoch nicht ber die richtigen zugeordneten
    Daten, die ausgewertet werden sollten. (11004)
    + 06 Nov 01:03:24 [2676] incoming session with 2001:999:93:5fa::15
    - 06 Nov 01:03:24 [2676] SYS RBB/2
    - 06 Nov 01:03:24 [2676] ZYZ Tommi Koivula

    No backresolve.. ;-)


    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 Tommi Koivula on Tue Nov 17 11:50:07 2020
    Hello Tommi,

    On Tuesday November 17 2020 11:57, you wrote to me:

    Reverse DNS is not needed for binkp connections. (in "Tommi style")
    :-)

    What's that style?

    Limiting the need for the feature to binkp connections.


    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 Richard Menedetter on Tue Nov 17 12:22:02 2020
    Hello Richard,

    On Tuesday November 17 2020 08:50, you wrote to me:

    But I know that DTAG has even a page, where you can trigger an IPv6 network prefix change. But they also do it periodically.

    Some Belgian providers also seem to change the IPv6 prefix periodically. The policy of my provider (Ziggo) is unclear. It is not periodic anyway. Last time it changed was when there was an unscheduled power failure. The power failure lasted only two hours, but it was in the middle of the night and the power adapter for my cable amplifier did not survive. I only noticed in the mornig and so the cable modem had no signal for six hours.

    Some of their customers see it as a "privacy" feature.

    I am not one of that "some". :-)


    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 Tue Nov 17 12:18:49 2020
    Hi Michiel,

    On 2020-11-17 11:39:22, you wrote to Tommi Koivula:

    MvdV> @CHRS: CP850 2

    MvdV> + 06 Nov 01:03:24 [2676] Error in getnameinfo(): Der angeforderte
    MvdV> Name ist
    MvdV> gltig und wurde in der Datenbank gefunden. Er
    MvdV> verfgt jedoch nicht ber die richtigen
    MvdV> zugeordneten
    MvdV> Daten, die ausgewertet werden sollten. (11004)

    Looks like utf-8 in a CP850 message? :-(

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Tue Nov 17 14:46:53 2020
    On 17.11.2020 12:39, Michiel van der Vlist : Tommi Koivula :

    I don't have to worry about reverse DNS. My ISP does that for me. ;-)

    But you cannot control it.

    I am not a control freak. ;-)

    + 17 Nov 11:35:28 [7821] incoming session with 2001:1c02:1102:ac00:f1d0:2:280:5555
    + 17 Nov 11:35:28 [7821] addr: 2:280/5555@fidonet

    host 2001:1c02:1102:ac00:f1d0:2:280:5555 5.5.5.5.0.8.2.0.2.0.0.0.0.d.1.f.0.0.c.a.2.0.1.1.2.0.c.1.1.0.0.2.ip6.ar pa domain name
    pointer 2001-1c02-1102-ac00-f1d0-0002-0280-5555.cable.dynamic.v6.ziggo .nl.

    See. It is not fido.vlist.eu :)

    I know. It is still better than how you come in:

    - 06 Nov 01:03:24 [1228] incoming from 2001:999:93:5fa::15 (60628)
    + 06 Nov 01:03:24 [2676] Error in getnameinfo(): Der angeforderte Name ist
    gültig und wurde in der Datenbank gefunden. Er
    verfügt jedoch nicht über die richtigen
    zugeordneten
    Daten, die ausgewertet werden sollten. (11004)
    + 06 Nov 01:03:24 [2676] incoming session with 2001:999:93:5fa::15
    - 06 Nov 01:03:24 [2676] SYS RBB/2
    - 06 Nov 01:03:24 [2676] ZYZ Tommi Koivula

    No backresolve.. ;-)

    Guess what, I can't control my ISP's DNS. ;-)

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Tue Nov 17 14:30:36 2020
    Hello Wilfred,

    On Tuesday November 17 2020 12:18, you wrote to me:

    @MSGID: 2:280/464 5fb3b1cf
    @REPLY: 2:280/5555 5fb3aad3
    @PID: GED+LNX 1.1.5-b20161221
    @TID: FMail-lnx64 2.1.0.18-B20170815
    @RFC-X-No-Archive: Yes
    @TZUTC: 0100
    @CHRS: UTF-8 2
    ^^^^

    MvdV>> + 06 Nov 01:03:24 [2676] Error in getnameinfo(): Der angeforderte
    MvdV>> Name ist gltig und wurde in der Datenbank
    MvdV>> gefunden. Er verfgt jedoch nicht ber die
    MvdV>> richtigen zugeordneten Daten, die
    MvdV>> ausgewertet werden sollten. (11004)

    Looks like utf-8 in a CP850 message? :-(

    Nope. It is the other way around. The encoding is CP850, but your Golded flags it as UTF-8 when replying, but does no translation.

    The give away is that it the "funny" characters are only one byte. If it were UTF-8, it would be two byte characters


    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 Tommi Koivula on Tue Nov 17 14:28:06 2020
    Hello Tommi,

    On Tuesday November 17 2020 14:46, you wrote to me:

    Guess what, I can't control my ISP's DNS. ;-)

    Figures. ;-)


    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 Tue Nov 17 14:53:40 2020
    Hi Michiel,

    On 2020-11-17 14:30:36, you wrote to me:

    MvdV>>> + 06 Nov 01:03:24 [2676] Error in getnameinfo(): Der angeforderte
    MvdV>>> Name ist gltig und wurde in der
    MvdV>>> Datenbank
    MvdV>>> gefunden. Er verfgt jedoch nicht ber die
    MvdV>>> richtigen zugeordneten Daten, die
    MvdV>>> ausgewertet werden sollten. (11004)

    Looks like utf-8 in a CP850 message? :-(

    MvdV> Nope. It is the other way around. The encoding is CP850, but your Golded
    MvdV> flags it as UTF-8 when replying, but does no translation.

    MvdV> The give away is that it the "funny" characters are only one byte. If it
    MvdV> were UTF-8, it would be two byte characters

    I was put on the wrong track, because in my editor they look like multbyte characters: "~A"... But when I check the .pkt file it came in, it's clear...


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Tue Nov 17 18:45:08 2020

    Tuesday November 17 2020 14:28, Michiel van der Vlist wrote to Tommi Koivula:

    Hello Tommi,

    On Tuesday November 17 2020 14:46, you wrote to me:

    Guess what, I can't control my ISP's DNS. ;-)

    Figures. ;-)

    In fact I'm using several outbound gateways, so you can see a few different incoming addresses.

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/360)
  • From Richard Menedetter@2:310/31 to Michiel van der Vlist on Tue Nov 17 19:06:54 2020
    Hi Michiel!

    17 Nov 2020 10:31, from Michiel van der Vlist -> Richard Menedetter:

    Reverse DNS is not needed for binkp connections. (in "Tommi style")
    :-)

    Sure ... but it is nice to have ;)

    CU, Ricsi

    ... The words you least want to hear, "Perhaps you had better sit down..."
    --- GoldED+/LNX
    * Origin: Press CTRL-ALT-DEL to continue... (2:310/31)
  • From Richard Menedetter@2:310/31 to Tony Langdon on Tue Nov 17 19:13:00 2020
    Hi Tony!

    17 Nov 2020 18:47, from Tony Langdon -> Tommi Koivula:

    But from what I recall, IPv6 is even more dependent on properly
    working ICMP than IPv4, so even if ping is blocked, other ICMP needs
    to be allowed.

    Indeed!
    Especially IPv6 packet too big messages.
    IPv4 would fragment on the way.
    That is not possible in IPv6 where fragmentation is only allowed on the ends of a connection.
    It relies on the ICMP packet too big arriving at the sender, so he can resend.

    CU, Ricsi

    ... "Like putty in your hands" takes on a new and depressing meaning.
    --- GoldED+/LNX
    * Origin: A big enough hammer fixes anything! (2:310/31)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Wed Nov 18 00:19:37 2020
    Hello Tommi,

    On Tuesday November 17 2020 18:45, you wrote to me:

    Guess what, I can't control my ISP's DNS. ;-)

    Figures. ;-)

    In fact I'm using several outbound gateways, so you can see a few different incoming addresses.

    That, I noticed.


    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 Richard Menedetter on Wed Nov 18 00:20:27 2020
    Hello Richard,

    On Tuesday November 17 2020 19:06, you wrote to me:

    Reverse DNS is not needed for binkp connections. (in "Tommi style")
    :-)

    Sure ... but it is nice to have ;)

    For binkp I say it is overrated. An f1d0 address is just as good or even better I'd say. ;-)

    Other than that, it is my understanding that most of the IPv6 network works pefectly well without reverse DNS. It is rumoured that mail servers are the exception.


    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 Wed Nov 18 09:00:23 2020
    On 18.11.2020 1:20, Michiel van der Vlist wrote:

    Other than that, it is my understanding that most of the IPv6 network
    works pefectly well without reverse DNS. It is rumoured that mail
    servers are the exception.


    Many smtp servers refuse mail from ip addresses without a valid reverse.
    Both ipv4 and ipv6.

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:4.7) Goanna/20201028 Interlink/52.9.7606
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Wed Nov 18 10:36:28 2020
    Hello Tommi,

    On Wednesday November 18 2020 09:00, you wrote to me:

    Other than that, it is my understanding that most of the IPv6
    network works pefectly well without reverse DNS. It is rumoured that
    mail servers are the exception.


    Many smtp servers refuse mail from ip addresses without a valid
    reverse. Both ipv4 and ipv6.

    So I heard too. I haven't encountered any problems myself. Now that you mention smtp servers, I have not yet run into an smtp server that supports IPv6...


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Richard Menedetter@2:310/31 to Michiel van der Vlist on Wed Nov 18 11:46:14 2020
    Hi Michiel!

    18 Nov 2020 00:20, from Michiel van der Vlist -> Richard Menedetter:

    Other than that, it is my understanding that most of the IPv6 network works pefectly well without reverse DNS.

    Yes ... but nice to have means it works without but it still is nice to have ;)
    I stand by that point.

    It is rumoured that mail servers are the exception.

    That is not a rumour!
    If you get back a different domainname you usually get a malus.

    CU, Ricsi

    ... The number of a person's relatives is directly proportional to his fame. --- GoldED+/LNX
    * Origin: Man's horizons are bounded by his vision. (2:310/31)
  • From Tommi Koivula@2:221/360 to Michiel van der Vlist on Wed Nov 18 12:53:18 2020

    Many smtp servers refuse mail from ip addresses without a valid
    reverse. Both ipv4 and ipv6.

    So I heard too. I haven't encountered any problems myself.

    Try sending mail to google smtp servers. It's not that easy.

    Now that you mention smtp servers, I have not yet run into an smtp
    server that supports IPv6...

    I have been running such a thing for many years.

    One of the advantages of HE tunnel is that you have static ipv6 and can run smtp server.

    'Tommi

    ... he.net certified sage
    ---
    * Origin: - rbb.fidonet.fi - Finland - (2:221/360)
  • From Michiel van der Vlist@2:280/5555 to Richard Menedetter on Wed Nov 18 14:40:43 2020
    Hello Richard,

    On Wednesday November 18 2020 11:46, you wrote to me:

    Yes ... but nice to have means it works without but it still is nice
    to have ;) I stand by that point.

    OK...

    It is rumoured that mail servers are the exception.

    That is not a rumour!

    With that I meant I have not run into that problem myself.

    If you get back a different domainname you usually get a malus.

    "different" from what?


    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 Tommi Koivula on Wed Nov 18 14:42:22 2020
    Hello Tommi,

    On Wednesday November 18 2020 12:53, you wrote to me:

    Many smtp servers refuse mail from ip addresses without a valid
    reverse. Both ipv4 and ipv6.

    So I heard too. I haven't encountered any problems myself.

    Try sending mail to google smtp servers. It's not that easy.

    I have never tried and have no plans to try in the foreseeable future. I stay away from Gmail.

    Now that you mention smtp servers, I have not yet run into an
    smtp server that supports IPv6...

    I have been running such a thing for many years.

    One of the advantages of HE tunnel is that you have static ipv6 and
    can run smtp server.

    You need Sage status to unblock port 25. But you have that of course. ;)


    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 Wed Nov 18 16:08:26 2020

    Try sending mail to google smtp servers. It's not that easy.

    I have never tried and have no plans to try in the foreseeable
    future. I stay away from Gmail.

    So you are not communicating anyone that uses gmail? There are also millions on companies that "rely" to google mail services.

    But since you apparently send all your email to your ISP's smarthost, you don't see the problems they may get when trying to send mail via google.

    One of the advantages of HE tunnel is that you have static ipv6
    and can run smtp server.

    You need Sage status to unblock port 25. But you have that of course.
    ;)

    Of course I do. :)

    'Tommi

    ... he.net certified sage
    --- GoldED+/W32-MINGW 1.1.5-b20180707
    * Origin: - rbb.fidonet.fi - Finland - (2:221/360)
  • From Jay Harris@1:229/664 to Michiel van der Vlist on Wed Nov 18 08:50:57 2020
    On 18 Nov 2020, Michiel van der Vlist said the following...

    So I heard too. I haven't encountered any problems myself. Now that you mentionsmtp servers, I have not yet run into an smtp server that
    supports IPv6...

    Google does:

    Name: ASPMX.L.GOOGLE.COM
    Address: 2607:f8b0:400d:c00::1a

    Our Office 365 tenant doesn't seem to support IPv6 yet.

    Jay

    ... Why can't you lie to the x-ray tech? They can see right through you

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Wed Nov 18 15:23:50 2020
    Hello Tommi,

    On Wednesday November 18 2020 16:08, you wrote to me:

    I have never tried and have no plans to try in the foreseeable
    future. I stay away from Gmail.

    So you are not communicating anyone that uses gmail?

    I try to avoid it. With moderate success.

    There are also millions on companies that "rely" to google mail
    services.

    Not my problem. I am penisonado, I no longer have a company, I no longer work for a company, I do not have to make compromises when dealing with companies. ;-)

    But since you apparently send all your email to your ISP's smarthost,

    I don't have a lot of choice. My ISP blocks outgoing port 25, except for mail going to their own smtp server...

    you don't see the problems they may get when trying to send mail via google.

    So... not my problem. ;-)

    You need Sage status to unblock port 25. But you have that of
    course. ;)

    Of course I do. :)

    And like me, you have the T-shirt. :-)

    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 Jay Harris on Wed Nov 18 15:46:47 2020
    Hello Jay,

    On Wednesday November 18 2020 08:50, you wrote to me:

    Google does:

    Name: ASPMX.L.GOOGLE.COM
    Address: 2607:f8b0:400d:c00::1a

    I know of others. But I have not yet made direct contact with them...

    Our Office 365 tenant doesn't seem to support IPv6 yet.

    Now that you mention IPv6, your incoming IPv6 is down:

    + 15:31 [2500] call to 1:229/664@fidonet
    15:31 [2500] trying f664.n229.z1.binkp.net [2607:fea8:ab00:e4f:934f:85c:ad29:d978]...
    ? 15:31 [2500] connection to 1:229/664@fidonet failed: {W32 API error
    10060} Connection timed out
    15:31 [2500] trying f664.n229.z1.binkp.net [173.33.12.16]...
    15:32 [2500] connected
    + 15:32 [2500] outgoing session with f664.n229.z1.binkp.net:24554 [173.33.12.16]
    - 15:32 [2500] OPT CRAM-MD5-4557667780ca8367a8336b8cb2fe96bf
    + 15:32 [2500] Remote requests MD mode
    - 15:32 [2500] SYS Northern Realms
    - 15:32 [2500] ZYZ Warpslide
    - 15:32 [2500] TIME Wed, 18 Nov 2020 09:31:57 -0500
    - 15:32 [2500] VER Mystic/1.12A47 binkp/1.0

    Dynamic IP?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: he.net certified sage (2:280/5555)
  • From Jay Harris@1:229/664 to Michiel van der Vlist on Wed Nov 18 11:43:16 2020
    On 18 Nov 2020, Michiel van der Vlist said the following...

    Now that you mention IPv6, your incoming IPv6 is down:

    Dynamic IP?

    Yeah, my provider changes the prefix from time to time. I'll update this when I get home.

    Jay

    ... He bought a donkey because he thought he might get a kick out of it

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Tony Langdon@3:633/410 to Richard Menedetter on Thu Nov 19 19:16:00 2020
    On 11-17-20 19:13, Richard Menedetter wrote to Tony Langdon <=-

    Indeed!
    Especially IPv6 packet too big messages.
    IPv4 would fragment on the way.
    That is not possible in IPv6 where fragmentation is only allowed on the ends of a connection.
    It relies on the ICMP packet too big arriving at the sender, so he can resend.

    Yeah that makes sense, and even blovking IPv4 ICMP causes strange issues, like without path MTU discovery, senders won't know to adjust packet size.


    ... Can I blame my spelling on Line Noise?
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Richard Menedetter@2:310/31 to Tony Langdon on Thu Nov 19 21:22:52 2020
    Hi Tony!

    19 Nov 2020 19:16, from Tony Langdon -> Richard Menedetter:

    Yeah that makes sense, and even blovking IPv4 ICMP causes strange
    issues, like without path MTU discovery, senders won't know to adjust packet size.

    At least IPv4 can fragment on the way.
    IPv6 is dropped instead of fragmented ... that makes a difference ;)

    CU, Ricsi

    ... A wife who gets breakfast in bed is usually in the hospital.
    --- GoldED+/LNX
    * Origin: Hear both sides before judging. (2:310/31)
  • From Tony Langdon@3:633/410 to Richard Menedetter on Fri Nov 20 18:49:00 2020
    On 11-19-20 21:22, Richard Menedetter wrote to Tony Langdon <=-

    At least IPv4 can fragment on the way.
    IPv6 is dropped instead of fragmented ... that makes a difference ;)

    True, but I have seen a lot of PMTU failures on IPv4 let small amounts of data through (up to just under 1500 bytes), but bulk transfers hang. In any case, blocking ICMP leads to a lot of bad things happening. :)


    ... My kid wanted a watch for Christmas, so we let him.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Jay Harris@1:229/664 to Michiel van der Vlist on Sun Nov 22 17:58:49 2020
    On 22 Nov 2020, Michiel van der Vlist said the following...

    IPv6 is still down...

    I'm showing it as up and available externally with some port scanners.

    Can someone else give it a try?


    Jay

    ... And they said computers would make our lives easier!

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Jay Harris@1:229/664 to Michiel van der Vlist on Sun Nov 22 20:51:22 2020
    On 23 Nov 2020, Michiel van der Vlist said the following...

    www.ipv6scanner.com reports bbs.nrbbs.net as open for IPv4 and Filtered forIPv6...

    *scratches head*

    Ok, a reboot of the modem, router & pi gave me yet another new IPv6 address.

    ipv6scanner.com now shows open/binkp, but who knows for how long.

    Maybe I should dive down the he.net rabbit hole...


    Jay

    ... It's amazing how eagles catch their prey, they're really talon-ted

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Jay Harris@1:229/664 to Michiel van der Vlist on Sun Nov 22 21:02:08 2020
    On 23 Nov 2020, Michiel van der Vlist said the following...

    www.ipv6scanner.com reports bbs.nrbbs.net as open for IPv4 and Filtered forIPv6...

    p.s: May take a bit for dns to update, my current IPv6 address is:

    2607:fea8:ab00:e4f:9cbb:bb1:662b:ad6b


    Jay

    ... Nature reserves are an eagle opportunity employer

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Richard Menedetter@2:310/31 to Jay Harris on Mon Nov 23 08:24:34 2020
    Hi Jay!

    22 Nov 2020 17:58, from Jay Harris -> Michiel van der Vlist:

    IPv6 is still down...
    I'm showing it as up and available externally with some port scanners.
    Can someone else give it a try?

    Yes, still down:
    08:23 [2672] trying f664.n229.z1.binkp.net [2607:fea8:ab00:e4f:934f:85c:ad29:d978]...
    ? 08:24 [2672] connection to 1:229/664@fidonet failed: Connection timed out
    08:24 [2672] trying f664.n229.z1.binkp.net [173.33.12.16]:24554...
    08:24 [2672] connected

    CU, Ricsi

    ... Be quick to listen, slow to speak, and slower to become angry.
    --- GoldED+/LNX
    * Origin: Mistakes are the bridge between inexperience and wisdom (2:310/31)
  • From Jay Harris@1:229/664 to Michiel van der Vlist on Mon Nov 23 09:07:40 2020
    On 23 Nov 2020, Michiel van der Vlist said the following...

    So... it is not your provider that changed the prefix. That would affect thefirst 64 bits. It is within your own local network that the host
    part, the last64 bits have changed. So the issue is a local issue and should be addressedlocally.

    Thanks for pointing that out. Somewhere along the line I must have forgotten to update /etc/dhcpcd.conf with:

    slaac hwaddr

    It was still set to the default of: slaac private

    It looks like DNS is already updated with the new address & ipv6scanner.com is showing 24553 & 24554 as open with an address of:

    2607:fea8:ab00:e4f:dea6:32ff:fe60:847b


    Jay

    ... Corduroy pillows are making headlines

    --- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)