Hi Mike,
On 2024-01-12 09:27:00, you wrote to me:
And don't specify the default port.
I have found that if my own system is not using the default port, it
is
best to specify it for systems that do.
Your current node is using BinkIT (on the default port), not binkd... ?
This system is, yes. 2320/107 is running binkd on a non-standard port. If
I don't specify the default port, it will try to use the port that binkd is
defined to on that system.
You probably set both iport and oport in your binkd config, then the behaviour is as expected. While you only supposed to set the iport for incoming connections!
This is translated from the russian docs, by google translate:
4.27. iport
The iport directive specifies the TCP port that will be opened by binkd to receive incoming connections. This directive can be used to set a non-standard port for binkd to run on, in particular to bypass the deny rules of a network gateway firewall.
Parameter ? a positive integer or a string (the name of the port number from the /etc/services file in unix and c:\winnt\system32\drivers\etc\services in Windows NT and 2000, in c:\windows\system32\drivers\etc\ services in Windows XP and 2003). The default value is 24554.
This directive is optional.
Example:
iport 24555
4.41. oport
The oport directive specifies the port on which binkd will try to establish a connection when the port for the link is not explicitly specified in the link's host address in the node line.
Parameter ? a positive integer or a string (the name of the port number from the /etc/services file in unix and c:\winnt\system32\drivers\etc\services in Windows NT and 2000, in c:\windows\system32\drivers\etc\ services in Windows XP and 2003). The default value is 24554.
This directive is optional.
Example:
oport 24555
Bye, Wilfred.
--- FMail-lnx64 2.2.1.0
* Origin: FMail development HQ (2:280/464)