Did several tracert of cwop.aprs.net
in the span of about 10 minutes.
- 1, resolved to cwop1.tamu.edu 126.96.36.199 on hop 20. Hops 17, 18, 19 timed out.
- 2, same result including TOs.
- 3, resolved to cwop.fuller.net 188.8.131.52 on hop 17 with no TOs.
- 4, same as first and second passes (cwop1.tamu.edu).
- 5, same as third pass (cwop.fuller.net).
Changed my configured APRS server in WL to fixed IP 184.108.40.206
(cwop.fuller.net) and had a successful
xfer on next scheduled APRS upload.
Changed my configured APRS server in WL to fixed IP 220.127.116.11
(cwop1.tamu.edu). WL crashed (tell microsoft) after choking on next scheduled APRS upload.
Relaunched WL. "Error opening APRS socket" in log. Same crash on next scheduled APRS upload.
Relaunched WL and configured for cwop.fuller.net
(FQDN this time, not IP). Success
on next two scheduled APRS uploads.
But wait... WL crashed on the third scheduled APRS upload, just like with the tamu.edu server. Same log entry.
Relaunched WL and made no other changes so far. It has uploaded sucessfully to APRS a few times since.
So, either cwop1.tamu.edu
needs to tighten up their nameservers or Davis needs to allow for a little more delay in their connection timeout. (My vote is for the first. Whom do we contact?) Meanwhile, I'm leaving it configured for cwop.fuller.net
for now and hope it doesn't crash. I'd change it back to cwop.aprs.net but then it is a dice-throw which server it tries, based on the DNS for aprs.net. At least then it still uploads to my website and WU without crashing.
Thanks for your help dalecoy, although it would have been quicker for me to roll-back.
At least this is closer to the cause of the problem. I wonder if tamu.edu was causing the 5.9.2a (pre-beta) problems from the beginning?
 Crashed again. Reconfiguring for cwop.aprs.net and going to bed. [/edit]