开云体育

Some progress on the GTK-3 port.



I have a question, the d-rats client sets up a SimpleXMLRPCServer on port 9100. Does anyone know why this port is used and what happens if a different port is used?

I had to set it to use a floating port to allow running more than one d-rats client on the same system at the same time, and am planning on leaving it that way unless a reason can be found to use a fixed port.

I am currently planning on using the version 4.0 for the python3 d-rats.

I now have the a ratflector and one client running running using GTK-3 and connecting to a client running from the master of the upstream


I have also been able to connect two d-rats clients through USB serial ports for testing with out needing a two radios.

They are passing chat messages, and some of the RPC calls are working.

I am going through the menus and trying everything that I can test in that configuration.

I am also getting ready to setup a branch that others can access, but not sure when I will have that ready.


One of the changes with GTK-3 is that they have deprecated all stock icons.

So if someone wants to find or create a set to replace them, that would be helpful.

Currently all my GTK3 toolbars items are displaying as blank. I have not had time to look into why they are not displaying the text titles.

73,
-WB8TYW, John

Hi John -- I have several d-rats clients running on a single network without any obvious problems. 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. 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.

Very good news about the progress on GTK-3. Thanks and 73, Richard Browning AD5RB

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

Thanks for the explanation. I am not that familiar with the details in PYthon of setting up an RPC server. Looking around I see RPC things in the rpc.py program, evidently related to the file server features. If you have two clients communicating through a ratflector does the ratflector somehow use the 9100 port? I assume the test would be to transfer and delete some files.

Thanks again and 73, Richard Browning AD5RB

On 3/15/2021 1:33 PM, ad5rb wrote:

If you have two clients communicating through a ratflector does the
ratflector somehow use the 9100 port? I assume the test would be to
transfer and delete some files.

There is no communication between the 9100 port and the Ratflector.

The port 9100 is only open to the local system.

It appears that a frame comes in over the network, the client routes it to the RPC server running on port 9100 for a thread to handle it.

If a the RPC Server port is in use, then that client can not process any incoming frames.

73,
-John, WB8TYW