Subj : Re: Listening on a specific IPv6 address.
To   : Kees van Eeten
From : Tony Langdon
Date : Tue Jan 09 2018 11:23 am

-=> Kees van Eeten wrote to Tony Langdon <=-

 KvE> - Add support for multiple listen sockets -- one for IPv4 and one for
 KvE> IPv6 (use V6ONLY)

I don't understand this option.  The name and description don't match in my
head. :/

 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: [<ipv6
 KvE> address>]:<port>

This one is not listed as OS specific.
 KvE> ----8<------------------------------------------------------------------
 KvE> ----

 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, which
 KvE> apparently is for unix like os's. It clearly limits to one IPv4 and one
 KvE> IPv6 port. To activate this IPV6_V6ONLY has to be defined.

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

 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 addresses
 KvE> 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"

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


.... Cats are purrfect
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

.