Subj : ipv6 resolvability
To   : Michiel van der Vlist
From : David Gonzalez
Date : Sun Nov 17 2024 10:52 pm


   Hello Michiel!

17 Nov 24 22:07, you wrote to me:

 MV> Hello David,

 MV> Sunday November 17 2024 21:27, I wrote to you:

 MV>> So no IPv6 connect yet. The first thing to look at would be the
 MV>> firewall. You should create an IPv6 pinhole fo port 24554.

 MV> I see you goy it fixed already:

 MV> + 22:06 [4472] call to 4:930/1@fidonet
 MV>   22:06 [4472] trying bbs.skynetbbs.com [2800:e2:5480:60::2]...
 MV>   22:06 [4472] connected
 MV> + 22:06 [4472] outgoing session with bbs.skynetbbs.com:24554
 MV>                [2800:e2:5480:60::2]
 MV> - 22:06 [4472] OPT CRAM-MD5-566231661606aa412c74fee39a672079
 MV> + 22:06 [4472] Remote requests MD mode
 MV> - 22:06 [4472] SYS SkyNet BBS
 MV> - 22:06 [4472] LOC Medellin, Colombia
 MV> - 22:06 [4472] ZYZ DavidG
 MV> - 22:06 [4472] TIME Sun, 17 Nov 2024 21:06:38 -0500
 MV> - 22:06 [4472] VER Mystic/1.12A48 binkp/1.0
 MV> - 22:06 [4472] BUILD 2023/01/15 15:29:47 Windows/32
 MV> + 22:06 [4472] addr: 21:3/188@fsxnet (n/a or busy)
 MV> + 22:06 [4472] addr: 3:633/2744.188@fidonet
 MV> + 22:06 [4472] addr: 4:930/1@fidonet
 MV> + 22:06 [4472] addr: 4:930/0@fidonet

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

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

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

Thanks

 MV> Cheers, Michiel

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

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
 * Origin: SkyNet BBS | telnet://bbs.skynetbbs.com:20023 (4:930/1)

.