Dave reports several outages in the crater during the IOP tonight. The following script reports eantf at 54dB (good?), and says it has been up for 12 hours. On the other hand, far has only been up 3 min and near only 2 hours, even though their signal levels are now 37 and 39 dB, respectively (okay values).
As expected, data_stats shows that the raw_data archive is fine at flr.
On a subsequent run of check_ap24, eanth@sodar came back, with a signal level of 49dB.
All of the above comments are consistent with Gordon's message early in the project.
[aster@flux ~]$ check_ap24.sh
local remote ( mac-addr) uptime ccq txrate rxrate rxsig snr #txpkts #rxpkts txretry rxretry txB/sec rxB/sec
ap24 ap24-3@near (00:15:6D:20:01:90) 1:56:06 98% 54.0Mbs 48.0Mbs -61dBm 39dB 9851146 9320039 0% 0% 103070 222934
ap24 ap24-2@rim (00:15:6D:10:1C:0D) 92:33:31 98% 48.0Mbs 54.0Mbs -60dBm 36dB 9528375 9851681 0% 0% 4445 12784
ap24 eanti@far (00:20:F6:05:24:56) 0:03:14 100% 11.0Mbs 2.0Mbs -63dBm 37dB 719 723 0% 0% 223 1186
awk: cmd. line:95: (FILENAME=- FNR=51) fatal: division by zero attempted
ap24-2 (00:15:6D:10:29:B2) 92:33:34 100% 54.0Mbs 48.0Mbs -51dBm 44dB 9929362 9450666 0% 0% 12784 4445
ap24-2 eantf@flr (00:20:F6:05:24:5A) 12:07:31 100% 11.0Mbs 11.0Mbs -43dBm 54dB 982727 898352 0% 0% 17755 8838
awk: cmd. line:93: (FILENAME=- FNR=39) fatal: division by zero attempted
ap24-3 ap24@base (00:15:6D:10:3C:BC) 1:56:09 97% 54.0Mbs 54.0Mbs -63dBm 32dB 9449388 9721786 0% 0% 222842 103027