• Listening on a specific IPv6 address.

    From Tony Langdon@3:633/410 to All on Friday, January 05, 2018 12:46:00
    Hi all. Just getting my BBS back online after a major crash. The new BBS is sharing a system with another BBS to both speed deployment, as well as simplify the new network backup systems (both systems can share the same network and cloud infrastructure).

    I have multiple IPv4 and V6 statis IPs, and want binkd to listen on a specific IPv4 and IPv6 address. I got IPv4 working fine, but I can't get binkd listening on a specific IP. I did a bit of Googling, and there was a post that said the following should work:

    listen [<ipv6 address>]

    But putting the address in square brackets like this still gives an error message.

    Any ideas?

    I'm running the following:
    $ binkd -v
    Binkd 1.1a-96 (Jan 1 2018 18:11:16/Linux)


    ... What is mind? No matter! What is matter? Never mind! - Homer S.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Michiel van der Vlist@2:280/5555 to Tony Langdon on Friday, January 05, 2018 14:59:45
    Hello Tony,

    On Friday January 05 2018 12:46, you wrote to All:

    I have multiple IPv4 and V6 statis IPs, and want binkd to listen on a specific IPv4 and IPv6 address. I got IPv4 working fine, but I can't
    get binkd listening on a specific IP. I did a bit of Googling, and
    there was a post that said the following should work:

    listen [<ipv6 address>]

    This is what I entered in my binkd config for a test:

    listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24555
    listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24554
    listen 192.168.178.15

    This seems to work. You should be able to call my system on port 24544 and port
    24555 on IPv6 and on IPv4 port 24554 only.

    But putting the address in square brackets like this still gives an
    error message.

    What error message?


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Saturday, January 06, 2018 16:15:00
    Michiel van der Vlist wrote to Tony Langdon <=-

    This is what I entered in my binkd config for a test:

    listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24555
    listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24554
    listen 192.168.178.15

    That didn't work for me. :( This is exactly what I tried.

    This seems to work. You should be able to call my system on port 24544 and port 24555 on IPv6 and on IPv4 port 24554 only.

    But putting the address in square brackets like this still gives an
    error message.

    What error message?

    16:09 [7477] BEGIN, binkd/1.1a-96/Linux binkd.conf
    16:09 [7477] servmgr started
    - 16:09 [7477] servmgr listen on 202.12.89.162:binkp
    16:09 [7478] clientmgr started
    ? 16:09 [7477] servmgr getaddrinfo: Name or service not known (-2)
    16:09 [7477] downing servmgr...
    ! 16:09 [7478] got signal #15.


    This is what I had in my config file.

    listen 202.12.89.162
    listen [2001:44b8:4176:f100:0:0:0:6]:24554
    listen *:24555


    ... testing a bit. Sorry lads.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Michiel van der Vlist@2:280/5555 to Tony Langdon on Saturday, January 06, 2018 10:30:00
    Hello Tony,

    On Saturday January 06 2018 16:15, you wrote to me:

    - 16:09 [7477] servmgr listen on 202.12.89.162:binkp
    16:09 [7478] clientmgr started
    ? 16:09 [7477] servmgr getaddrinfo: Name or service not known (-2)
    16:09 [7477] downing servmgr...
    ! 16:09 [7478] got signal #15.


    This is what I had in my config file.

    listen 202.12.89.162

    That may be the problem. Any address here should be a valid address on the local machine. So unless your fido machine is NOT behind a NAT, it should be an
    RFC1918 address, not the WAN address of your router.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Kees van Eeten@2:280/5003.4 to Tony Langdon on Saturday, January 06, 2018 10:29:26
    Hello Tony!

    06 Jan 18 16:15, you wrote to Michiel van der Vlist:

    16:09 [7477] BEGIN, binkd/1.1a-96/Linux binkd.conf
    16:09 [7477] servmgr started
    - 16:09 [7477] servmgr listen on 202.12.89.162:binkp
    16:09 [7478] clientmgr started
    ? 16:09 [7477] servmgr getaddrinfo: Name or service not known (-2)
    16:09 [7477] downing servmgr...
    ! 16:09 [7478] got signal #15.

    You have o declare what port number binkp uses.
    Is the following line given in /etc/services

    binkp 24554/tcp # binkp fidonet protocol



    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Joacim Melin@2:201/120 to Michiel van der Vlist on Saturday, January 06, 2018 12:18:55
    MvdV> Hello Tony,

    MvdV> On Friday January 05 2018 12:46, you wrote to All:

    I have multiple IPv4 and V6 statis IPs, and want binkd to listen on a
    specific IPv4 and IPv6 address. I got IPv4 working fine, but I can't
    get binkd listening on a specific IP. I did a bit of Googling, and
    there was a post that said the following should work:

    listen [<ipv6 address>]

    MvdV> This is what I entered in my binkd config for a test:

    MvdV> listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24555
    MvdV> listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24554
    MvdV> listen 192.168.178.15

    MvdV> This seems to work. You should be able to call my system on port
    MvdV> 24544 and port 24555 on IPv6 and on IPv4 port 24554 only.

    But putting the address in square brackets like this still gives an
    error message.

    MvdV> What error message?

    Just do a port forward from each virtual public IP to the server on the "inside".


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Monday, January 08, 2018 20:35:00
    Michiel van der Vlist wrote to Tony Langdon <=-

    Hello Tony,

    On Saturday January 06 2018 16:15, you wrote to me:

    - 16:09 [7477] servmgr listen on 202.12.89.162:binkp
    16:09 [7478] clientmgr started
    ? 16:09 [7477] servmgr getaddrinfo: Name or service not known (-2)
    16:09 [7477] downing servmgr...
    ! 16:09 [7478] got signal #15.


    This is what I had in my config file.

    listen 202.12.89.162

    That may be the problem. Any address here should be a valid address on the local machine. So unless your fido machine is NOT behind a NAT, it should be an RFC1918 address, not the WAN address of your router.


    Well, the machine does in fact have multiple public IP addresses, there is no NAT router. And besides, IPv4 works, it's the IPv6 address that doesn't work in the binkd listen directive.


    ... It's important that I NOT know.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Kees van Eeten on Monday, January 08, 2018 20:41:00
    Kees van Eeten wrote to Tony Langdon <=-

    Hello Tony!

    06 Jan 18 16:15, you wrote to Michiel van der Vlist:

    16:09 [7477] BEGIN, binkd/1.1a-96/Linux binkd.conf
    16:09 [7477] servmgr started
    - 16:09 [7477] servmgr listen on 202.12.89.162:binkp <-- IPv4 works OK
    16:09 [7478] clientmgr started
    ? 16:09 [7477] servmgr getaddrinfo: Name or service not known (-2) <--
    IPv6 doesn't
    16:09 [7477] downing servmgr...
    ! 16:09 [7478] got signal #15.


    binkp 24554/tcp # binkp fidonet
    protocol

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

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

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


    ... Jokes about German sausage are the wurst.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Kees van Eeten@2:280/5003.4 to Tony Langdon on Monday, January 08, 2018 12:43:44
    Hello Tony!

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

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

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

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

    Are you sure, you can add the port number to the address on the "listen"
    line?

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Michiel van der Vlist@2:280/5555 to Kees van Eeten on Monday, January 08, 2018 13:35:42
    Hello Kees,

    On Monday January 08 2018 12:43, you wrote to Tony Langdon:

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

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

    Are you sure, you can add the port number to the address on the
    "listen" line?

    It works for me. You can call 280/5555 on port 24554 and port 24555. (IPv6)

    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


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Tony Langdon on Monday, January 08, 2018 13:53:54
    Hello Tony,

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

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

    I vaguely remembers something like that...

    there is no NAT router. And besides, IPv4 works, it's the IPv6
    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
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Tommi Koivula@2:221/6 to Tony Langdon on Monday, January 08, 2018 15:01:44

    08 Jan 18 20:41:00, you wrote to Kees van Eeten:

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

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

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

    Can you drop the ':24554 part', what does is say then? Or change the port to something else?

    Do you have 'iport xxxxx' in your config?

    Are you absolutely sure that [2001:44b8:4176:f100::6] is your _local_ ipv6 address? ;-D It does not answer to ping.

    And finally, run with -vv, so we can see all the logging.

    'Tommi

    ---
    * Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)
  • From Tommi Koivula@2:221/6 to Kees van Eeten on Monday, January 08, 2018 15:21:04

    08 Jan 18 12:43:44, you wrote to Tony Langdon:

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

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

    Are you sure, you can add the port number to the address on the "listen"
    line?

    Yes.

    === Cut ===
    listen [2001:470:1f15:cb0::6]
    listen [2001:999:43:79b1:e5b:8fff:fe27:9a64]:23456
    === Cut ===

    15:22 [6512] BEGIN, binkd/1.1a-96/CYGWIN_NT-6.1 binkd.cfg
    15:22 [6512] servmgr started
    15:22 [6512] servmgr listen on [2001:470:1f15:cb0::6]:24555
    15:22 [6512] servmgr listen on [2001:999:43:79b1:e5b:8fff:fe27:9a64]:23456

    'Tommi

    ---
    * Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Monday, January 08, 2018 14:29:51
    Hello Tommi,

    On Monday January 08 2018 15:01, you wrote to Tony Langdon:

    Are you absolutely sure that [2001:44b8:4176:f100::6] is your _local_
    ipv6 address? ;-D It does not answer to ping.

    What I didn't mention is that I manually added the ::5556 address with netsh:

    D:\FIDO\BINKD>ipconfig

    Windows-IP-Konfiguration


    Ethernetadapter LAN-Verbindung:

    Verbindungsspezifisches DNS-Suffix: dynamic.ziggo.nl
    IP-Adresse. . . . . . . . . . . . : 192.168.178.15
    Subnetzmaske. . . . . . . . . . . : 255.255.255.0
    IP-Adresse. . . . . . . . . . . . : 2001:1c02:1100:d700:f1d0:2:280:5556
    IP-Adresse. . . . . . . . . . . . : 2001:1c02:1100:d700:f1d0:2:280:5555
    IP-Adresse. . . . . . . . . . . . : fe80::215:60ff:fe52:213d%4
    Standardgateway . . . . . . . . . : 192.168.178.1
    fe80::7277:81ff:fe72:a4bb%4



    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Wilfred van Velzen@2:280/464 to Kees van Eeten on Monday, January 08, 2018 15:41:07
    Hi Kees,

    On 2018-01-08 12:43:44, you wrote to Tony Langdon:

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

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

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

    Are you sure, you can add the port number to the address on the
    "listen" line?

    It isn't specified anywhere in the docs or example configuration. You specify the port with the 'iport' configuration line.

    Maybe it's handled by the windows api function the 'listen' string is handed to? So it won't work on linux.


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Monday, January 08, 2018 16:08:26
    Hello Wilfred,

    On Monday January 08 2018 15:41, you wrote to Kees van Eeten:


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

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

    Are you sure, you can add the port number to the address on the
    "listen" line?

    It isn't specified anywhere in the docs or example configuration. You specify the port with the 'iport' configuration line.

    Can one specify multiple ports with that?

    Anyway, it is no good for those who need disfferent ports for IPv4 and IPv6.

    Maybe it's handled by the windows api function the 'listen' string is handed to? So it won't work on linux.

    It certainly works for Windows.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Monday, January 08, 2018 16:41:51
    Hi Michiel,

    On 2018-01-08 16:08:26, you wrote to me:

    It isn't specified anywhere in the docs or example configuration. You
    specify the port with the 'iport' configuration line.

    MvdV> Can one specify multiple ports with that?

    I don't know, but probably not.

    MvdV> Anyway, it is no good for those who need disfferent ports for IPv4
    MvdV> and IPv6.

    You can, but you will have to start multiple instances of binkd, with different
    configurations.


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6 to Michiel van der Vlist on Monday, January 08, 2018 18:41:06

    08 Jan 18 16:08:26, you wrote to Wilfred van Velzen:

    It isn't specified anywhere in the docs or example configuration. You
    specify the port with the 'iport' configuration line.

    Can one specify multiple ports with that?

    Easy to test: nope.

    Multiple iport lines in binkd.conf and the last one wins.

    Anyway, it is no good for those who need disfferent ports for IPv4 and IPv6.

    Maybe it's handled by the windows api function the 'listen' string is
    handed to? So it won't work on linux.

    It certainly works for Windows.

    But not in linux. But works in cygwin port. Funny.

    In Windows you can have nice address and port combinations, even by hostname! :

    === Cut ===
    iport 24555
    listen [2001:470:1f15:cb0::6]
    listen [2001:999:43:79b1:e5b:8fff:fe27:9a64]:23456
    listen [2001:999:43:79b1:d440:f045:3754:2]:24666
    listen 0.0.0.0:24777
    listen 0.0.0.0
    listen len.localnet:5678
    === Cut ===

    18:48 [5192] servmgr listen on [2001:470:1f15:cb0::6]:24555
    18:48 [5192] servmgr listen on [2001:999:43:79b1:e5b:8fff:fe27:9a64]:23456 18:48 [5192] servmgr listen on [2001:999:43:79b1:d440:f045:3754:2]:24666
    18:48 [5192] servmgr listen on 0.0.0.0:24777
    18:48 [5192] servmgr listen on 0.0.0.0:24555
    18:48 [5192] servmgr listen on len.localnet:5678

    'Tommi

    ---
    * Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)
  • From Kees van Eeten@2:280/5003.4 to Tony Langdon on Monday, January 08, 2018 19:41:54
    Hello Tony!

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

    - 16:09 [7477] servmgr listen on 202.12.89.162:binkp <-- IPv4 works
    OK
    16:09 [7478] clientmgr started
    ? 16:09 [7477] servmgr getaddrinfo: Name or service not known (-2)
    <--

    IPv6 doesn't

    16:09 [7477] downing servmgr...
    ! 16:09 [7478] got signal #15.


    binkp 24554/tcp # binkp fidonet
    protocol

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

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

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

    There was smething in the back of my mind still nagging, that I had come
    across this as well.

    On all experimental en active versions of Binkd i use:

    listen 0.0.0.0

    So I tried
    listen [ipv6-addres]

    I got the same error as you do. ;((

    I have also something nagging in the back of my mind, that I was looking into
    this, either for binkd or jammnntpd. I think it prooved to be the change in
    name of an element of a structure or the name of a constant.

    The problem is that I currently cannot remember where and how I solved this.
    So I actually wonder if anybody is using the listen option for
    specified IPv6 addresses on a linux system?

    It is clear, that it is somewhere in the call to open a listen socket.

    I will have a look these comming days, but don't hold your breath.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Kees van Eeten@2:280/5003.4 to Tony Langdon on Monday, January 08, 2018 21:58:42
    Hello Tony!

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

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

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

    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)
  • From Tommi Koivula@2:221/0 to Kees van Eeten on Monday, January 08, 2018 23:46:02

    08 Jan 18 19:41, Kees van Eeten wrote to Tony Langdon:

    I got the same error as you do. ;((

    I second this on my ubuntu box:

    08 Jan 23:37:00 [2223] /etc/binkd/binkd.cfg changed!
    08 Jan 23:37:00 [2223] Reloading configuration...
    08 Jan 23:37:00 [2223] previous config is no longer in use, unloading
    08 Jan 23:37:08 [2223] servmgr getaddrinfo: Name or service not known (-2)
    08 Jan 23:37:08 [2223] downing servmgr...
    08 Jan 23:37:08 [2224] got signal #15.

    But when I put the hostname instead of ipv6 address, it works.

    "listen pin.tkk.iki.fi"

    08 Jan 23:38:41 [18764] BEGIN, binkd/1.1a-96/Linux /etc/binkd/binkd.cfg -q -C 08 Jan 23:38:41 [18764] unexpected pid_file: /run/ftn/binkd.pid: unlinked
    08 Jan 23:38:41 [18764] servmgr started
    08 Jan 23:38:41 [18765] clientmgr started
    08 Jan 23:38:41 [18764] servmgr listen on pin.tkk.iki.fi:binkp
    08 Jan 23:39:36 [18764] incoming from 176.93.176.228 (60515)
    08 Jan 23:39:36 [18778] incoming session with 176-93-176-228.bb.dnainternet.fi [176.93.176.228]

    08 Jan 23:39:52 [18764] incoming from 2001:470:1f15:cb0::6 (60541)
    08 Jan 23:39:52 [18779] incoming session with 2001:470:1f15:cb0::6

    So, Tony, you could try:

    "listen freeway.vkradio.com" or whatver name points to your ipv6 address.

    'Tommi

    --- hpt/os2-emx 1.9.0-cur 17-02-17
    * Origin: 2001:470:1f15:cb0:f1d0:2:221:0 (2:221/0)
  • From Tony Langdon@3:633/410 to Kees van Eeten on Tuesday, January 09, 2018 10:28:00
    Kees van Eeten wrote to Tony Langdon <=-

    Are you sure, you can add the port number to the address on the
    "listen"
    line?

    Tried it both ways, doesn't work. But I can do

    listen *:24555 and binkd listens on 24555 on both IPv4 and IPv6.


    ... Is this some conspiracy to make me look paranoid?
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Michiel van der Vlist on Tuesday, January 09, 2018 10:32:00
    Michiel van der Vlist wrote to Tony Langdon <=-

    Hello Tony,

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

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

    I vaguely remembers something like that...

    there is no NAT router. And besides, IPv4 works, it's the IPv6
    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]

    What version of binkd and OS are you using?

    Multple listen statements do not seem to be a problem.

    Confirmed here, just that I can't seem to use IPv6 addresses in listen statements here. :(

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

    That's what I'm wondering. I compiled mine from source on a Pi.


    ... Warranty: If it breaks, both halves are yours.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Tommi Koivula on Tuesday, January 09, 2018 10:39:00
    Tommi Koivula wrote to Tony Langdon <=-

    Can you drop the ':24554 part', what does is say then? Or change the
    port to something else?

    Tried both, no difference.

    Do you have 'iport xxxxx' in your config?

    Are you absolutely sure that [2001:44b8:4176:f100::6] is your _local_
    ipv6 address? ;-D It does not answer to ping.

    Copied and pasted from the output of ifconfig, and it's a static IP.

    And finally, run with -vv, so we can see all the logging.

    Good idea, thanks. :)

    Nope, that didn't shed any light on the issue, the server process dies as soon as that error is encountered. :(

    sbbs@lemaker /sbbs/ctrl $ binkd -vv binkd.conf
    10:34 [20100] BEGIN, binkd/1.1a-96/Linux -vv binkd.conf
    10:34 [20100] created /sbbs/binkd/run/binkd.pid
    10:34 [20100] servmgr started
    - 10:34 [20100] servmgr listen on 202.12.89.162:binkp
    10:34 [20101] clientmgr started
    $ -c 3:633/410.1@fidonet
    c- 21:1/100@fsxnet
    10:34 [20101] started client #1, id=20102
    10:34 [20101] started client #2, id=20103
    10:34 [20102] created /sbbs/binkd/outbound/0279019a.pnt/00000001.csy
    + 10:34 [20102] call to 3:633/410.1@fidonet
    10:34 [20103] created /sbbs/binkd/fsxnet.015/00010064.csy
    + 10:34 [20103] call to 21:1/100@fsxnet
    ? 10:34 [20100] servmgr getaddrinfo: Name or service not known (-2)
    10:34 [20100] downing servmgr...


    ... You can name your salary here, I call mine fred.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Kees van Eeten on Tuesday, January 09, 2018 10:45:00
    Kees van Eeten wrote to Tony Langdon <=-

    On all experimental en active versions of Binkd i use:

    listen 0.0.0.0

    That's not an option for me, and listen ipv4-address works fine, FYI.

    So I tried
    listen [ipv6-addres]

    I got the same error as you do. ;((

    Glad someone else has managed to reproduce this. :(

    I have also something nagging in the back of my mind, that I was
    looking into
    this, either for binkd or jammnntpd. I think it prooved to be the
    change in
    name of an element of a structure or the name of a constant.

    The problem is that I currently cannot remember where and how I solved this.
    So I actually wonder if anybody is using the listen option for
    specified IPv6 addresses on a linux system?

    It is clear, that it is somewhere in the call to open a listen socket.

    I will have a look these comming days, but don't hold your breath.

    OK, thanks. I am able to listen on IPv4, and have a second port setup for IPv4/v6 incoming sessions.


    ... Daddy, why doesn't this magnet pick up your diskettes?
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Kees van Eeten on Tuesday, January 09, 2018 11:23:00
    Kees van Eeten wrote to Tony Langdon <=-

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

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

    - 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>

    This one is not listed as OS specific.
    ----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.

    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.

    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"

    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)
  • From Tony Langdon@3:633/410 to Tommi Koivula on Tuesday, January 09, 2018 11:35:00
    Tommi Koivula wrote to Kees van Eeten <=-

    But when I put the hostname instead of ipv6 address, it works.

    That fixed my problem! Thanks! :) I had to remove the "listen 202.12.89.162" statement, because it is now redundant and causes a port conflict. Using the hostname works in one hit for both IPv4 and v6 (there are both A and AAAA records for the name).

    So, Tony, you could try:

    "listen freeway.vkradio.com" or whatver name points to your ipv6
    address.

    Yep, that works for me. Thanks! :)


    ... I know exactly what a sextet is... But I'd rather not say...
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tommi Koivula@2:221/1.1 to Tony Langdon on Tuesday, January 09, 2018 10:03:12

    09 Jan 18 11:35:00, you wrote to me:

    Tommi Koivula wrote to Kees van Eeten <=-

    But when I put the hostname instead of ipv6 address, it works.

    That fixed my problem! Thanks! :) I had to remove the "listen 202.12.89.162" statement, because it is now redundant and causes a port conflict. Using the hostname works in one hit for both IPv4 and v6 (there are both A and AAAA records for the name).

    So, Tony, you could try:

    "listen freeway.vkradio.com" or whatver name points to your ipv6
    address.

    Yep, that works for me. Thanks! :)

    Great! :)

    But I still cannot connect by ipv6:

    === Cut ===
    10:01 [776] call to 3:633/410@fidonet
    10:01 [776] trying f410.n633.z3.binkp.net [2001:44b8:4176:f100::6]...
    10:02 [776] connection to 3:633/410@fidonet failed: Connection timed out
    10:02 [776] trying f410.n633.z3.binkp.net [202.12.89.162]:24554...
    10:02 [776] bind -- getaddrinfo: Name or service not known (8)
    10:02 [776] connected
    10:02 [776] outgoing session with f410.n633.z3.binkp.net:24554 [202.12.89.
    10:02 [776] OPT CRAM-MD5-188dcc066f7c6ad7fc23e4e896f6acee
    10:02 [776] Remote requests MD mode
    10:02 [776] SYS Freeway BBS
    10:02 [776] ZYZ Tony Langdon
    === Cut ===

    'Tommi

    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)
  • From Kees van Eeten@2:280/5003.4 to Tony Langdon on Tuesday, January 09, 2018 19:58:36
    Hello Tony!

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

    - 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>

    This one is not listed as OS specific.

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

    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.

    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.

    Look at the code in server.c

    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"

    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
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Tony Langdon@3:633/410 to Tommi Koivula on Wednesday, January 10, 2018 08:42:00
    Tommi Koivula wrote to Tony Langdon <=-

    But I still cannot connect by ipv6:

    Thanks for the feedback. Fixed. Had firewall issues, took a bit of beating the router into submission to fix it. :)


    ... Secret of electronics: Keep the smoke in the wires.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tony Langdon@3:633/410 to Kees van Eeten on Wednesday, January 10, 2018 08:45:00
    Kees van Eeten wrote to Tony Langdon <=-

    This one is not listed as OS specific.

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

    That's a big assumption! If it's Windows specific, then it should have been mentioned in that line.

    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.

    That is true, though the notation is the "standard" way for an IPv6 literal, which is why I was a bit surprised it didn't work.


    ... When eating an elephant, take one bite at a time.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Kees van Eeten@2:280/5003.4 to Tony Langdon on Wednesday, January 10, 2018 16:15:50
    Hello Tony!

    That is true, though the notation is the "standard" way for an IPv6 literal, which is why I was a bit surprised it didn't work.


    ... When eating an elephant, take one bite at a time.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

    Just as an afterhought, for those running e.g. Linux. If some setups with
    multiple addresses/ports/IP-families are not available within Binkd, there
    is is always the possibillity to use the inetd or xinetd deamon.

    Not elegant, but it may work.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Tony Langdon@3:633/410 to Kees van Eeten on Thursday, January 11, 2018 16:24:00
    Kees van Eeten wrote to Tony Langdon <=-

    is is always the possibillity to use the inetd or xinetd deamon.

    Not elegant, but it may work.

    If you can pass the socket to binkd, I don't see why not. Anyway, problem solved.


    ... Ignorance is the mother of research.
    === MultiMail/Win32 v0.49
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Tommi Koivula@2:221/1.1 to Kees van Eeten on Thursday, January 11, 2018 10:51:34

    Just as an afterhought, for those running e.g. Linux. If some setups
    with multiple addresses/ports/IP-families are not available within
    Binkd, there is is always the possibillity to use the inetd or xinetd deamon.

    Not elegant, but it may work.

    It works. I run xinetd in a router. :) And a second one in ubuntu raspberry pi2.

    'Tommi

    ---
    * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)