¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: d-rats gtk-3 progress

 

GNS3 can simulate multiple hosts in a sandbox network but I have not used it personally.


73,
Robert, AE5YG


Re: d-rats gtk-3 progress

 

THANKS John, you're doing a great job!


Il giorno lun 22 mar 2021 alle ore 13:43 John E. Malmberg <wb8tyw@...> ha scritto:
This weekend I discovered that the conversion of the ddt2.py and
transport.py to use bytearrays in the master branch at
broke a bunch of stuff.

PRs have been submitted that fix Chat and file handling.

Spent the time testing and fixing that, so did not get anything more
ready of GTK-3 code for a published branch.

Got a small bit more of the protocol documented.



The GTK-3 code now seems to be working for receiving file transfer
requests, and chat conversations.

When I get time, I plan to try the message transfers next.

Still lots of stuff does not work.

* Some toolbars are blank.
* Something is wrong with the widget for station list display, it mostly
works, but I am getting a failure in the logs for related to it.
* Lots of log noise in the GTK-3 version.
* File transfer GUI not working the remote section.

Need a way to simulate the various servers and devices that d-rats can
connect to for testing that code.

73,
-John, WB8TYW







d-rats gtk-3 progress

 

This weekend I discovered that the conversion of the ddt2.py and transport.py to use bytearrays in the master branch at broke a bunch of stuff.

PRs have been submitted that fix Chat and file handling.

Spent the time testing and fixing that, so did not get anything more ready of GTK-3 code for a published branch.

Got a small bit more of the protocol documented.



The GTK-3 code now seems to be working for receiving file transfer requests, and chat conversations.

When I get time, I plan to try the message transfers next.

Still lots of stuff does not work.

* Some toolbars are blank.
* Something is wrong with the widget for station list display, it mostly works, but I am getting a failure in the logs for related to it.
* Lots of log noise in the GTK-3 version.
* File transfer GUI not working the remote section.

Need a way to simulate the various servers and devices that d-rats can connect to for testing that code.

73,
-John, WB8TYW


Re: Progress in the GTK-3 conversion

 

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


Re: Progress in the GTK-3 conversion

 

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


Re: Progress in the GTK-3 conversion

 

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


Re: Progress in the GTK-3 conversion

 

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


Progress in the GTK-3 conversion

 

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


Re: ICS 213 Reply

 

I think you need to have the "Include Original in reply" box checked under Preferences>Messages.

Hank
K4HYJ


Re: Backing up of configuration.

 

You can even have both folders, in the case of using the old or modern version. HI HI HI?


Re: Backing up of configuration.

 

Thanks. I found ¡°d-rats.config¡± in the roaming/D-RATS-EV folder.?

appreciate the help.?

danny


Re: Backing up of configuration.

 

This is where I found it in my Windows 10 machine:
C:\Users\n3tsz\AppData\Roaming\D-RATS-EV

Patrick (N3TSZ)


On Tuesday, March 9, 2021, 06:17:47 PM EST, Daniel Boggiano via groups.io <dboggny@...> wrote:


I don¡¯t have that.?


Re: Backing up of configuration.

W Paul Mills AC0HY
 

If you use %AppData% in windows start and then look under that, you will find it somewhere. Should persist after a reinstall anyhow.

Windows likes to mangle your user name, in above example from Patrick, substitute "User" with the mangled user name. Sometimes gets put in different folder than "Roaming". Who knows why windows puts things where the do!


Re: Backing up of configuration.

 

I don¡¯t have that.?


Re: Backing up of configuration.

 

My config file is here:
C:\Users\User\AppData\Roaming\D-RATS

Patrick (N3TSZ)


On Tuesday, March 9, 2021, 10:43:15 AM EST, Daniel Boggiano via groups.io <dboggny@...> wrote:


On the raspberry pi, I backup the .config file so if I have to re-install or make a new setup, I do not have to retype everything in.?

Is there a similar file in Windows I can do the same with?
thanks,
danny


Backing up of configuration.

 

On the raspberry pi, I backup the .config file so if I have to re-install or make a new setup, I do not have to retype everything in.?

Is there a similar file in Windows I can do the same with?
thanks,
danny


ICS 213 Reply

 

Can't seem to reply to an ICS 213 form and have the reply appear in the bottom of the original ICS213. Anybody get this to.work? This is the way it works I'm FLDigi and how the form is designed to work.?


Re: D_RATS on Pi keep alive

 

The easiest thing to do is send a GPS-A report in a QST, as location data does not print anywhere, so it will not be seen anywhere but the event tab and the Map.

Patrick (N3TSZ)


On Wednesday, February 24, 2021, 04:58:06 PM EST, ad5rb <ad5rb@...> wrote:


Hi John and Patrick
After looking at this some more it does seem that moving to Python 3 would help.? When I look at the documentation for Python 2.7, for the socket routine, I see things about the timeout feature, but not the keepalive feature.? Python 3 at least talks about both, but not clear to me how to implement things.? When I look at current Windows documentation it talks about the default timeout for a TCP port being 5 minutes, but changeable during the initialization process for the port.? It also talks about keepalive as used to keep a connection open when there are no packets being sent.? The details here seem fairly intricate and it is not clear if the Linux, Mac OS, and Windows systems have all agreed on how a TCP port should be operated.

Meanwhile the 4 minute QST does seem to work and using the Filter option in D-RATS the messages just accumulate in another tab that you can mostly ignore.? Is there a standard for these keep alive messages?? I am setting a QST message with the contents KpAlv4 and then creating a filter for KpAlv4 as well.

Thanks for the advice,? Richard Browning? AD5RB






Re: D_RATS on Pi keep alive

 

Hi John and Patrick
After looking at this some more it does seem that moving to Python 3 would help. When I look at the documentation for Python 2.7, for the socket routine, I see things about the timeout feature, but not the keepalive feature. Python 3 at least talks about both, but not clear to me how to implement things. When I look at current Windows documentation it talks about the default timeout for a TCP port being 5 minutes, but changeable during the initialization process for the port. It also talks about keepalive as used to keep a connection open when there are no packets being sent. The details here seem fairly intricate and it is not clear if the Linux, Mac OS, and Windows systems have all agreed on how a TCP port should be operated.

Meanwhile the 4 minute QST does seem to work and using the Filter option in D-RATS the messages just accumulate in another tab that you can mostly ignore. Is there a standard for these keep alive messages? I am setting a QST message with the contents KpAlv4 and then creating a filter for KpAlv4 as well.

Thanks for the advice, Richard Browning AD5RB


Re: D_RATS on Pi keep alive

 

While this issue is being addressed, here is a trick that will keep the clutter off the main chat tab.

HOW TO END RATFLECTOR FATIGUE
If your screen is too busy, try this.
Go to File>Preferences>Appearance and type \[QST] on the Ignore RegEx line.
Go to File>Preferences>Chat and disable Show status updates in chat.
Click Save to exit Preferences.
Click Add Filter on the toolbar in the main window.
Enter [QST] as the filter text and click Save



Patrick (N3TSZ)


On Tuesday, February 23, 2021, 04:47:35 PM EST, ad5rb <ad5rb@...> wrote:


Recently, while trying to get standardized on the latest 0.3.9 version, I have ratflector connections timing out at around 5 minutes.? The simple cure is to run a QST announcement every 4 minutes.? Only one station needs to be running this and it seems to keep all stations connected. This is running on Windows 10 machines, but I also have an Ubuntu Linux laptop that does the same 5 minute time out.? Running a 6 minute QST announce does not work.
While the cure is simple, it does result it lots of clutter on the Main chat page.? Again, not a problem if a separate Channel is used for the primary conversation, but then everyone needs to know about the Channel.
Is it worth trying to modify the D-Rats client so the TCP port time out is set to something like 30 minutes or an hour?? Running a QST once an hour makes a nice clock so you realize how much time you are spending, but every 4 minutes is a little excessive in my opinion.
Richard Browning? AD5RB