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)

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)

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)

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)

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> g�ltig und wurde in der Datenbank gefunden. Er
MvdV> verf�gt 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)

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 g�ltig und wurde in der
MvdV>>> Datenbank
MvdV>>> gefunden. Er verf�gt 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)

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)

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)

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)

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)