Greetings, traveler ...

28 Apr 18 21:47, you wrote to me:

 AD>> Please give it a try and let me know the results here or by
 AD>> netmail.

 MV> There are a few poblems. First I had to remove the commands related to
 MV> compression from my config. There is an error at startup:

Aha, this is intersting can you share the node line which didn't work?

 MV> D:\FIDO\BINKD>binkd-static binkd.cfg
 MV>   21:47 [3120] BEGIN standalone, binkd/1.1a-97/Win32 binkd.cfg
 MV>   21:47 [3120] servmgr started
 MV>   21:47 [2420] clientmgr started
 MV> ? 21:47 [3120] servmgr setsockopt (IPV6_V6ONLY): {W32 API error 10042}
 MV>                An unknown, invalid, or unsupported option or level was
 MV>                specified in a getsockopt or setsockopt call
 MV> - 21:47 [3120] servmgr listen on
 MV> [2001:1c02:1100:d700:f1d0:2:280:5555]:24555 ? 21:47 [3120] servmgr
 MV> setsockopt (IPV6_V6ONLY): {W32 API error 10042}
 MV>                An unknown, invalid , or unsupported option or level
 MV> was
 MV>                specified in a getsockopt or setsockopt call
 MV> - 21:47 [3120] servmgr listen on
 MV> [2001:1c02:1100:d700:f1d0:2:280:5555]:24554 - 21:47 [3120] servmgr
 MV> listen on 0.0.0.0:24554

Which version you were running with this config before mine? Can you share your
config?
To be honest I didn't touch nor test server pieces of code, onlu client and I
did my tests with 'binkd -c -P'.
Perhaps there is some work to do in a server side too, you config (or at least
pieces of it where you 'bind' binkd) might be helpfull.

 MV> And then when I try to call 2:5020/9696 (T-6to4) it always calls out
 MV> on IPv6, no matter if I specify -64, -46 or just -4.

Let me try this one ...


\aID


--- GoldED+/BSD 1.1.5-b20170303