[drats_users] Thread 4 on Windows using 30 to 50% CPU, GPS Parsing?

[John E. Malmberg]

On 2/21/2013 12:57 PM, Dan Smith wrote:
>> If this is a network connection to an outside server with no active
>> traffic, the local ISP will terminate the connection after a period
>> of time.  15 minutes sounds like their timeout.
>
> Your ISP should not be proxying your connections at layer 4 under
> normal circumstances. I suspect this is actually coming from your
> NATing router, not your ISP.

It appears to be a standard practice for Cable Company run broadband.

My previous QTH broadband ISP actually stated that they were doing this 
in their TOS document.

My NATing router does not have that feature.

> If it's really upstream of you entirely, you should get a new ISP :)

Not sure if the only other ISP would be any better.

>> The only way to stop them from terminating the connection is for
>> either the client or server application have a keep alive heart beat
>> that sends a packet or two every few minutes.
>
> So you should be able to test this by configuring D-RATS to send a
> QST every five minutes on the network port and have it not break
> in the way you usually would after thirty minutes or so.

I did a test last night and did not connect to RAT1 in addition to RAT. 
  RAT was active most of the night and I did not see the CPU utilization 
until this morning when the GUI was no longer responding.

I have started a QST beacon on RAT, and will monitor it tonight.

Regards,
-John