Subj : Listening on a specific IPv6 address.
To   : Tony Langdon
From : Kees van Eeten
Date : Mon Jan 08 2018 09:58 pm

Hello Tony!

08 Jan 18 20:41, you wrote to me:

 TL> It's already in there. In fact, binkd has done the lookup to report the
 TL> above. The getaddrinfo error occurs when I have the line:

 TL> listen [2001:44b8:4176:f100::6]:24554

 TL> Without that line, it works on IPv4 and binkd runs.

 The story continues. Ignore the fact, that I may have found a bug in the
 past.

 My friends in R24 always say: He who reads has clearly has an advantage.

 I found the following in the HISTORY file

----8<----------------------------------------------------------------------
2012/01/03 19:26:05 1.0a-564 green
rfc2553.c,NONE,2.1 rfc2553.h,NONE,2.1 !README.FIX,2.53,2.54 client.c,2.70,2.71 
e
xitproc.c,2.43,2.44 ftnnode.c,2.36,2.37 https.c,2.21,2.22 iphdr.h,2.17,2.18 
ipto
ols.c,2.14,2.15 iptools.h,2.7,2.8 md5b.c,2.9,2.10 perlhooks.c,2.72,2.73 
protoco2
..h,2.27,2.28 protocol.c,2.203,2.204 readcfg.c,2.97,2.98 server.c,2.43,2.44 
serve
r.h,2.3,2.4 srif.c,2.19,2.20 sys.h,2.32,2.33
Implemented IPv6 support
- replace (almost) all getXbyY function calls with getaddrinfo/getnameinfo 
(RFC2553) calls
- Add compatibility layer for target systems not supporting RFC2553 calls in 
rfc2553.[ch]
- Add support for multiple listen sockets -- one for IPv4 and one for IPv6 (use 
V6ONLY)
- For WIN32 platform add configuration parameter IPV6 (mutually exclusive with 
BINKD9X)
- On WIN32 platform use Winsock2 API if IPV6 support is requested
- config: node IP address literal + port supported: [<ipv6 address>]:<port>
----8<----------------------------------------------------------------------

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

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

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

 Hope this gives some insight.

Kees

--- GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

.