Hello Tony!

09 Jan 18 11:23, you wrote to me:

 KvE>> - For WIN32 platform add configuration parameter IPV6 (mutually
 KvE>> exclusive with BINKD9X)
 KvE>> - On WIN32 platform use Winsock2 API if IPV6 support is requested

 KvE>> - config: node IP address literal + port supported: [> address>]:

 TL> This one is not listed as OS specific.

 You probably have to read it together with the line above it.

 KvE>> The last line confirms to notation Michiel uses on a Windows machine.
 KvE>> There is also a Compile time option for multiple listen sockets,
 KvE>> which apparently is for unix like os's. It clearly limits to one IPv4
 KvE>> and one IPv6 port. To activate this IPV6_V6ONLY has to be defined.

 TL> This is confusing, the name and description seem different, result:  I
 TL> have no idea what it _really_ does and it looks like a translation error.

 Look at the code in server.c

 KvE>> In the default builds for Unix type os's nowhere is IPV6_V6ONLY
 KvE>> defined. We may conclude that for default use, listen to all
 KvE>> addresses is preferred by the developers.

 KvE>> A recompile with IPV6_V6ONLY defined, may solve some of your
 KvE>> requirements. If you want more functionality, most maintenance
 KvE>> developers will come back with the question: "Show me the code"

 TL> Maybe, though a bug is still not out of the question.

 What one may call a bug, the other may call a feature. Fact is that the
 network API's for Linux and Windows are different.

 If you choose the OS, you have to live with the API, or you have to
 create a compatibilly shim.

Kees

--- GoldED+/LNX 1.1.5