Sorry for the outage on the cluster and spotters earlier. Not sure when we went offline but the computer was running but there was no network connectivity. Solved with a reboot.
We have a friend in Vietnam at 203.145.44.183, provided by
DANH TUAN TECHNOLOGY COMPANY LIMITED,
House number 36,
Hoa Binh Village,
Di Nau Commune,
Thach That District,
Hanoi City,
Vietnam
who has been beating on the server front door since midnight. Firewalled off now.
Hopefully that will be all or I’ll Firewall the entire IP range for that internet provider.
203.145.44.0/24 is still trying his luck and getting nowhere.
Today there was a period of disruption from a German IP address, this the last hour’s traffic that is blocked at the firewall.
And a Swiss station had made over 50 simultaneous connections and was still connecting… I think a script had gone wrong. He’s firewalled till I can mail him. Despite the mayhem, the cluster just kept running for a change :-):
I had to make a few fixes to the software today. There are more coming. The important point is the current software has my old call embedded in it, >MM0FMF< and I intend to change that real soon now to my new call >GM4LLD< This means some of you may have included the cluster prompt in commands for your logging programs to expect in response. So wherever you have MM0FMF that will need to become GM4LLD
Welcome to the MM0FMF SOTA Cluster
will become Welcome to the GM4LLD SOTA Cluster
<YOUR_CALL> de MM0FMF sota_cluster >
will become <YOUR_CALL> de GM4LLD sota_cluster >
SH/DX show latest spots SH/USERS show logged in users PING1 the cluster will send you its prompt once a minute PING5 the cluster will send you its prompt once every 5 minutes.
The last two are useful at keeping connections alive if the software you use does not support its own keep-alive methods.