Subj : New router and HE.NET tunnel
To   : Mattias Larsson
From : Michiel van der Vlist
Date : Tue Aug 16 2016 12:55:28

Hello Mattias,

On Tuesday August 16 2016 11:20, you wrote to All:

 ML> IPv6-test.com reports 19/20 result. Not been able to check if my
 ML> services work over IPv6 though

Try making an outgoing binkp call to my system.

Oh wait. Mystic does not support outgoing IPv6 yet...

 ML> but I have opened binkp on bbs.beyond.nu 24554 in hopes that it works
 ML> now.

You'r making progress:

+ 12:36 [1040] call to 2:203/210@fidonet
  12:36 [1040] trying 2002:9b04:d43a:0:81cd:e79d:45e7:9566
               [2002:9b04:d43a:0:81cd:e79d:45e7:9566]...
? 12:36 [1040] connection to 2:203/210@fidonet failed:
               {W32 API error 10060} Connection timed out

That's not working. But...

  12:36 [1040] trying bbs.beyond.nu [2001:470:28:84e:2a0:98ff:fe96:8f6]...
  12:36 [1040] connected
+ 12:36 [1040] outgoing session with bbs.beyond.nu:24554
               [2001:470:28:84e:2a0:98ff:fe96:8f6]
- 12:36 [1040] OPT CRAM-MD5-36249fee1f47b1b6b43e93e16909d2cc
+ 12:36 [1040] Remote requests MD mode
- 12:36 [1040] SYS Beyond Systems BBS
- 12:36 [1040] ZYZ Mattias Larsson

That works! Your he.net tunnel does its job. Just remove the AAAA record for the
2002:9b04:: from your host name.

- 12:36 [1040] VER Mystic/1.12A31 binkp/1.0
+ 12:36 [1040] addr: 2:203/210@fidonet
? 12:36 [1040] rerror: Unsecured session not allowed
+ 12:36 [1040] done (to 2:203/210@fidonet, failed, S/R: 0/0 (0/0 bytes))
  12:36 [1040] session closed, quitting...

And of course nag the maintainer of mystic to remove the annoying bug of not accepting unsecure sessions.


Cheers, Michiel

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

.