On 3/14/2021 10:42 PM, ad5rb wrote:
Hi John -- I have several d-rats clients running on a single
network without any obvious problems.
For testing, I am running multiple d-rats clients on a single computer different thing.
With out my change, only one D-rats client on a single computer will communicate on a network. The rest will print an error message in the log, but not communicate.
I do a have a firewall on the network so the return ports would all
be different and handled by the Network Address Translation process.
Not relevant in this case.
Even without a firewall I don't understand why there would be a problem. Port 9100 is really the default port address for the
ratflectors not the clients.
The Ratflector default address is 9000, not 9100.
The existing client is binding port 9100 on "localhost" for its internal RPC Server, so that port is never exposed outside of the system it is running on.
The client never connects to it by that port specifically, it uses the RPC server object for the connection.
So the only reason to have a specific port exposed is if there was an external program that needed to communicate with the d-rats client, and I have not found any.
There are several 9xxx ports referenced in the source, that I need to look at and make sure that they can be set by configuration parameters.
Some of the 9xxx ports are also used by popular network print servers.
73,
-wb8tyw, John
