TID: Mystic BBS 1.12 A48
REPLY: 2:280/5555 673b13eb
MSGID: 4:930/1 673bada9
PID: GED+W32 1.1.5-b20180707
CHRS: CP437 2
TZUTC: -0500
Hola Michiel!, saludo cordial

18 Nov 24 11:13, tu escribi(ste) a ti:

 MV> Hello David,

 MV> On Sunday November 17 2024 22:52, you wrote to me:

 MV>>> So congratulations and welcome to the Fidonet IPv6 club!

 DG>> Yup, but I just changed the IPv6 to match my (local) ipv4, so
 DG>> it's now
 DG>> ::20, give it a go and it should also reply.

 MV> Hmmm... That didn't work...

 MV> + 11:12 [4756] call to 4:930/1@fidonet
 MV>   11:12 [4756] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
 MV> ? 11:12 [4756] connection to 4:930/1@fidonet failed: {W32 API error
 MV> 10060} Conne ction timed out 11:12 [4756] trying bbs.skynetbbs.com
 MV> [181.142.97.252]... ? 11:12 [4756] connection to 4:930/1@fidonet
 MV> failed: {W32 API error 10061} Conne ction refused 11:12 [4756] trying
 MV> 2800:e2:5480:60::20 [2800:e2:5480:60::20]... ? 11:12 [4756] connection
 MV> to 4:930/1@fidonet failed: {W32 API error 10061} Conne ction
 MV> refused 11:12 [5792] the queue is empty, quitting...

 MV> 1) You forgot to update the AAAA record for bbs.skynetbbs.com.

I did indeed, that plus I use a shitty provider namecheap, but it's updated
now.

 MV> 2) It looks like you also forgot to restart Mystic as it is not
 MV> answereing at all on any IP.

 DG>> I also had to disable SLAAC from My Mikrotik edge so did not get
 DG>> EUI-64.

 MV> OK.


 MV> Cheers, Michiel

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

--
Saludos/Kind Regards
David
- SysOp SkyNet BBS
- telnet://bbs.skynet.com:20023
SEEN-BY: 902/26 930/1 341/66 900/106 902/19 280/464 229/426 0/0 90/0 900/0
SEEN-BY: 902/0
PATH: 930/1 902/26