[Dxspider-support] Hamclock connections

[Michael Walker]

I reached out to him again and explained that set/qra would cause a lot of
SD card writing and asked him if there is a better way.

This is what I got back:

Ok, I had not considered the *set* command would cause writing to an SD
card. What do you think if I change the heartbeat to a *show* command which
I assume are passive, such as "show/date", and cranking up the timeout to 5
minutes?

If there is a better option, I have his ear.

73 all, Mike va3mw


On Thu, Mar 2, 2023 at 2:09 PM Mike McCarthy, W1NR via Dxspider-support <
dxspider-support at tobit.co.uk> wrote:

> Consumer firewall/routers running NAT will sometimes expire or otherwise
> lose NAT connection mapping if no traffic is seen in short periods of
> time. If filtering is heavy that no spots flow for a while, maybe that
> is the reason?
>
> W1NR
>
> On 3/2/2023 2:01 PM, Dirk Koopman via Dxspider-support wrote:
> > I am struggling to  understand why HamClock requires a "keepalive"
> > timer. It's a TCP based connection that will have ICMP turned on (unlike
> > certain TCP connections in day$ job). This means that he *will* get
> > notified if his connection goes away ("connection reset by peer"). But,
> > in any event, if there is no output for a user for more than 11 minutes
> > (extremely tight filtering perhaps), the he will get a prompt.
> >
> > But, getting traffic - by itself - *should* reset his "keepalive" timer.
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230302/626328a3/attachment.htm>