TID: FMail-W32 2.1.3.7-B20170919
RFC-X-No-Archive: Yes
TZUTC: 0200
CHRS: CP850 2
MSGID: 2:280/5555 60f9991b
REPLY: 5012.fidonetipv6@4:902/26 255de89f
Hello Fernando,

On Wednesday July 21 2021 19:26, you wrote to you:

 FT> I can't find the problem on my node, I already checked my settings
 FT> several times and they seem to be ok .. but there is something that
 FT> made my he.net node stop working ipv6.

It seems your end of the tunnel is down. I can ping the other end of the
tunnel:

D:\FIDO6\BINKD>ping 2001:470:1f1e:4e::1

Ping wird ausgef�hrt f�r 2001:470:1f1e:4e::1 mit 32 Bytes Daten:

Antwort von 2001:470:1f1e:4e::1: Zeit=195ms
Antwort von 2001:470:1f1e:4e::1: Zeit=193ms
Antwort von 2001:470:1f1e:4e::1: Zeit=194ms
Antwort von 2001:470:1f1e:4e::1: Zeit=194ms

Ping-Statistik f�r 2001:470:1f1e:4e::1:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 193ms, Maximum = 195ms, Mittelwert = 194ms

But there is no response from your end of the tunnel:

D:\FIDO6\BINKD>ping 2001:470:1f1e:4e::2

Ping wird ausgef�hrt f�r 2001:470:1f1e:4e::2 mit 32 Bytes Daten:

Zeit�berschreitung der Anforderung.
Zeit�berschreitung der Anforderung.
Zeit�berschreitung der Anforderung.
Zeit�berschreitung der Anforderung.

Ping-Statistik f�r 2001:470:1f1e:4e::2:
    Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

 FT> My ISP now seems to be delivering ipv6 through 6to4, I will try to
 FT> change he.net to 6to4 and see if it works again

We wait and see...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: he.net certified sage (2:280/5555)
SEEN-BY: 1/123 19/10 90/1 105/81 120/340 123/131 203/0 221/0 6 226/30
SEEN-BY: 227/702 229/424 426 428 550 700 1016 240/5138 5411 5824 5832
SEEN-BY: 240/5853 249/206 317 400 250/1 280/464 5003 5006 5555 282/1038
SEEN-BY: 301/1 310/31 317/3 320/219 322/757 342/200 460/58 633/280
SEEN-BY: 640/1384 712/848 2452/250 2454/119 5019/40 5020/545 1042
SEEN-BY: 5020/12000 5053/58
PATH: 280/5555 240/5832 229/426