Hello Tony,

On Monday January 08 2018 20:35, you wrote to me:

 TL> Well, the machine does in fact have multiple public IP addresses,

I vaguely remembers something like that...

 TL> there is no NAT router.  And besides, IPv4 works, it's the IPv6
 TL> address that doesn't work in the binkd listen directive.

Odd. Ik works here, This what I have for 280/5556

#iport 24554
#oport 24554
listen [2001:1c02:1100:d700:f1d0:2:280:5556]:24554
bindaddr [2001:1c02:1100:d700:f1d0:2:280:5556]

And this for 280/5555

#iport 24554
#oport 24554
listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24555
listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24554
bindaddr [2001:1c02:1100:d700:f1d0:2:280:5555]
listen 0.0.0.0

Multple listen statements do not seem to be a problem.

When I enter multiple bindadrr statements however, only the last seems to have
effect. With the above setup, I get a bind error when calling an IPv4 only
node:

+ 13:49 [2772] call to 2:280/1041@fidonet
  13:49 [2772] trying fido.bier028.nl [62.195.219.231]...
+ 13:49 [2772] bind -- getaddrinfo: Der angegebene Host ist unbekannt.  (11001)
  13:49 [2772] connected
+ 13:49 [2772] outgoing session with fido.bier028.nl:24554 [62.195.219.231]
- 13:49 [2772] OPT ENC-DES-CBC CRAM-MD5-bf94c91d047ed045cea9404d924f06c2
+ 13:49 [2772] Remote requests MD mode
- 13:49 [2772] SYS fido.bier028.nl

The error seems to have no effect.

The error disappears when I add

bindaddr 0.0.0.0

But then every IPv6 call is launched from ::5556


Maybe you stumbled on a difference between the Windows and the Linux version?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303