Subj : IPV6 and Netgear
To   : Mattias Larsson
From : Michiel van der Vlist
Date : Fri Aug 05 2016 13:22:01

Hello Mattias,

Friday August 05 2016 12:51, I wrote to you:

 MV> No IPv6 ping, no answer on port 23 and port 24554 IPv6

You aren't in the nodelist yet, get your NC to contribute to the daily list ;-)

I had to do some tricks, you IPv6 number is a 6to4 number and in that case windows treies IPv4 first.

+ 13:20 [1728] call to 2:203/210@fidonet
  13:20 [1728] trying 2002:9b04:d43a:0:81cd:e79d:45e7:9566               [2002:9b04:d43a:0:81cd:e79d:45e7:9566]...
? 13:20 [2884] connection to 2:5019/40@fidonet failed: {W32 API
               error 10060} Connection timed out
  13:21 [1728] trying bbs.beyond.nu [155.4.212.58]...
  13:21 [1728] connected
+ 13:21 [1728] outgoing session with bbs.beyond.nu:24554 [155.4.212.58]
- 13:21 [1728] OPT CRAM-MD5-a1772e5888d417789a81dc553a00dbac
+ 13:21 [1728] Remote requests MD mode
- 13:21 [1728] SYS Beyond BBS
- 13:21 [1728] ZYZ Mattias Larsson
- 13:21 [1728] VER Mystic/1.12A31 binkp/1.0
+ 13:21 [1728] addr: 2:203/210@fidonet
? 13:21 [1728] rerror: Unsecured session not allowed
+ 13:21 [1728] done (to 2:203/210@fidonet, failed, S/R: 0/0 (0/0 bytes))
  13:21 [1728] session closed, quitting...

You should allow unsecure sessions...

I do not know if Mystic supports Iv6 yet. You may want to try binkd.


Cheers, Michiel

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

.