[WT-support] how to increase the WT network reliability?

Tõnno Vähk tonno.vahk at gmail.com
Thu Apr 4 21:36:41 CEST 2013

Thanks Peter and Luca,


But I do not complain about synchronization. Yes, of course I have the
syncrhonization activated (Disable.. not checked) and the synchronization
works OK. SYNC command is not needed. So when one computer drops out of
network and either WT reload or computer restart restores the network then
all the QSOs are usually nicely synchronized. The problem is losing the
network (network being disabled by WT or other reasons) for some reason once
in a while.


I read from WT wiki that fixed IP is recommended. So maybe that is what I
should do to avoid trouble? 


But is there any reason to believe cable ethernet is better than WIFI?




From: support-bounces at f5mzn.org [mailto:support-bounces at f5mzn.org] On Behalf
Of Luca NCJ
Sent: Thursday, April 04, 2013 10:15 PM
To: support at win-test.com
Subject: Re: [WT-support] how to increase the WT network reliability?



have you never tryed to use the command "SYNC" instead of reload?

Last year in D4C M/M using 7 PC's some of them connected with cable (3 if I
rememeber well) and the rest via local WI-FI and the differences between
logs were really minor after 48 hours (and not present in all logs).

We used same IP category both for cable and WI-FI and with automatic IP




2013/4/4 Peter <pc2a at pi4cc.nl>


At PI4CC we run M/M up to 12 computers and find always that all the
computers has the same log.
If a computer has a outage/crash of if a new computer plugged into the
network it fills automagic with all the qso's without any command.
I have never used the command reload

But all the computers are connected via cat5


Op 4-4-2013 20:46, Tõnno Vähk schreef:

We and I think most other multi op stations are used to the network problems
that cause one computer lose network and RELOAD is needed to restore the
connection. There are different kind of error messages about non-unique QSO
identifier, some erroneous UDP sockets or whatever...

I find this an unavoidable part of multi op operation. We did MM for the
first time in WPX SSB with ca 15 networked computers. The amount of needed
RELOAD's also went up. And now there were at least 3 times when reload did
not help and computer had to restarted to restore network. It was strange
that packet spots were flowing but QSOs did not and synchronization did not
function also before restart was done.

We used a mix of cable and wifi network. Of course making sure no computer
had both enabled. For cable had mostly determined IPs and for WIFI

My question is - can anyone say or recommend:

Is it better to use cable rather than WIFI?

Is it better not to mix two?

Is it better to use determined IP instead of automatic? Does it make any

Any other ideas how to make the network more reliable and save the trouble
of frequent reloads and restarts?`


Support mailing list
support at win-test.com

Support mailing list
support at win-test.com

Luca IK2NCJ 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20130404/0a344e2f/attachment-0001.html>

More information about the Support mailing list