Hello Wilfred,

On Monday August 03 2020 10:32, you wrote to me:

 MvdV>>  75  1:14/6       Jeff Smith             T-6in4  he.net
 MvdV>> DOWN

 WV> I noticed that Jeff posted a message in an echomail area, so I decided
 WV> to test his node. 1:14/6 Doesn't exist anymore in the nodelist,

Aha. I noticed that Arno Klein, 2:240/100 was no longer in the nodelist, but I missed 1:14/6. Tnx for pointing it out. I will remove him from the list.

 WV> so I tested 1:14/0, which has an IPv6 address, with the following
 WV> result:

 WV> + 03 Aug 10:19:03 [10843] call to 1:14/0@fidonet
 WV>   03 Aug 10:19:03 [10843] trying ftn.region14.org
 WV> [2001:470:1f10:abd::2]... 03 Aug 10:19:03 [10843] connected + 03 Aug
 WV> 10:19:03 [10843] outgoing session with ftn.region14.org:24554
 WV> [2001:470:1f10:abd::2] ? 03 Aug 10:19:05 [10843] got M_BSY: Blocked +
 WV> 03 Aug 10:19:05 [10843] done (to 1:14/0@fidonet, failed, S/R: 0/0 (0/0
 WV> bytes)) 03 Aug 10:19:05 [10843] session closed, quitting...

 WV> And I get the same on his regular node which has a different host
 WV> name, but resolves to the same IPv6 address.

If it has the same IPv6 address and the same port nr, it is the same node. 1:282/1031 is in the list.

 WV> Could be a misconfigured Mystic system, which by default blocks
 WV> systems of which it doesn't have a secure link with...

It isn't that. I have seen that before and it generates a different error. This is probably a busy flag that isn't cleared because of an irregular shut down.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303