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.
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
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] 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
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.
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.
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.
Kees van Eeten wrote to Tony Langdon <=-IPv6 doesn't
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) <--
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.
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?
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 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.
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?
Are you absolutely sure that [2001:44b8:4176:f100::6] is your _local_
ipv6 address? ;-D It does not answer to ping.
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?
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.
It isn't specified anywhere in the docs or example configuration. You
specify the port with the 'iport' configuration 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.
- 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.
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.
I got the same error as you do. ;((
Kees van Eeten wrote to Tony Langdon <=-
Are you sure, you can add the port number to the address on the
"listen"
line?
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]
Multple listen statements do not seem to be a problem.
Maybe you stumbled on a difference between the Windows and the Linux version?
Tommi Koivula wrote to Tony Langdon <=-
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.
Kees van Eeten wrote to Tony Langdon <=-
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 van Eeten wrote to Tony Langdon <=-
- 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"
Tommi Koivula wrote to Kees van Eeten <=-
But when I put the hostname instead of ipv6 address, it works.
So, Tony, you could try:
"listen freeway.vkradio.com" or whatver name points to your ipv6
address.
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! :)
- 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.
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.
Tommi Koivula wrote to Tony Langdon <=-
But I still cannot connect by ipv6:
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.
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)
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.
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.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,048 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 73:40:18 |
| Calls: | 236,065 |
| Files: | 60,366 |
| D/L today: |
13 files (1,542K bytes) |
| Messages: | 289,996 |