[Dxspider-support] RF connect question
Ron Stordahl N5IN
ronn5in-dxspider at yahoo.com
Mon Oct 27 21:52:36 GMT 2008
This is a very interesting observation.
I would test this out with the BPQ32 radio interface, but my DXSpider machine went kaput, so I need to install on a different box and I have not had the time.
It almost seems as if AGWPE is not returning the hard disconnect to DXSpider or it is not seeing it. Clearly this is not an issue with a hard disconnect via telnet, or it would have been corrected long ago.
Hopefully a BPQ32/DXSpider user can test this before I get to it. Make a connection by radio, get some spots, then kill the user radio for a while and see if the user gets dropped by DXSpiser due to a hard disconnect, then reconnect and see if old spots are still queued, they shouldn't be.
----- Original Message ----
> From: Danny Pease <dpease at adams.net>
> To: DXspider <dxspider-support at dxcluster.org>
> Sent: Monday, October 27, 2008 9:26:35 AM
> Subject: [Dxspider-support] RF connect question
> This weekend I had an RF user that got disconnected but the node still
> showed him as connected. About 14 hours later, he connected again and
> all of the spots he missed during that time started being sent to him.
> After an hour of trying to catch up on old spots (and there was still 11
> hours worth of stuff to catch up), I finally shut down the AGW packet
> engine, which stopped the cluster as well. I restarted everything and
> when the RF user reconnected, everything was fine.
> My question is, is there something in the settings I can change change
> to make sure this doesn't happen again?
> I am using Windows 98SE on a 600 MHz PIII, DX Spider version 1.55 build
> 0.26 and the TNC/radio is a Kenwood D700A with the TNC in KISS mode and
> the AGW Packet Engine software.
> Danny NG9R
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
More information about the Dxspider-support