Greetings, traveler ...

30 Apr 18 06:10, I wrote to you:

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

 AD> It may have something to do with the libs versions I've linked Windows
 AD> build with, I'll try to see what does these mean ... Perhaps I have to
 AD> rebuild it with newer VC or something.

As per MSDN (https://msdn.microsoft.com/en-us/library/windows/desktop/ms738574)
IPV6_V6ONLY support was added to Windows starting from Vista. This option just
not in XP IP stack, I guess warning may be safely ignored.


\aID


--- GoldED+/BSD 1.1.5-b20170303