Hello, maybe someone know what the activity from IP address 199.7.185.10? It use kiwiclient.py for record 5Mhz, 10 MHz or 15Mhz:
Sat Jun 26 16:20:06 00:02:34.710 0... 0 L 5000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (ARRIVED)
Sat Jun 26 16:20:16 00:02:45.291 .... 0 L 5000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (LEAVING after 0:00:12)
Sat Jun 26 16:20:31 00:03:00.206 0... 0 L 10000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (ARRIVED)
Sat Jun 26 16:20:42 00:03:10.781 .... 0 L 10000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (LEAVING after 0:00:11)
Sat Jun 26 16:20:57 00:03:26.313 0... 0 L 15000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (ARRIVED)
Sat Jun 26 16:21:08 00:03:37.396 .... 0 L 15000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (LEAVING after 0:00:12)
Sat Jun 26 16:30:07 00:12:36.272 0... 0 L 5000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (ARRIVED)
Sat Jun 26 16:30:18 00:12:47.022 .... 0 L 5000.00 kHz am z0 "kiwirecorder.py" 199.7.185.10 (LEAVING after 0:00:12)
but never stop when day time limit was ended...
Log's file on my KiwiSDR from the Khabarovsk:
Sun Jun 27 16:44:23 1d:00:26:52.285 0123 0 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:44:24 1d:00:26:53.015 0123 1 PWD entry timeout
Sun Jun 27 16:44:24 1d:00:26:53.344 0123 1 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:44:25 1d:00:26:54.023 0123 2 PWD entry timeout
Sun Jun 27 16:44:26 1d:00:26:55.331 0123 2 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:44:27 1d:00:26:56.024 0123 3 PWD entry timeout
Sun Jun 27 16:44:27 1d:00:26:56.328 0123 3 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:44:44 1d:00:27:13.086 0123 0 PWD entry timeout
Sun Jun 27 16:44:44 1d:00:27:13.228 0123 0 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:44:45 1d:00:27:14.035 0123 1 PWD entry timeout
Sun Jun 27 16:44:46 1d:00:27:15.384 0123 1 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:44:47 1d:00:27:16.032 0123 2 PWD entry timeout
Sun Jun 27 16:44:47 1d:00:27:16.341 0123 2 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:44:48 1d:00:27:17.025 0123 3 PWD entry timeout
Sun Jun 27 16:44:49 1d:00:27:18.310 0123 3 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:45:05 1d:00:27:34.029 0123 0 PWD entry timeout
Sun Jun 27 16:45:06 1d:00:27:35.463 0123 0 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:45:07 1d:00:27:36.090 0123 1 PWD entry timeout
Sun Jun 27 16:45:07 1d:00:27:36.318 0123 1 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:45:08 1d:00:27:37.042 0123 2 PWD entry timeout
Sun Jun 27 16:45:08 1d:00:27:37.084 0123 2 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:45:10 1d:00:27:39.001 0123 3 PWD entry timeout
Sun Jun 27 16:45:10 1d:00:27:39.365 0123 3 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:45:27 1d:00:27:56.058 0123 0 PWD entry timeout
Sun Jun 27 16:45:28 1d:00:27:57.000 0123 0 TLIMIT-IP connecting LIMIT EXCEEDED cur:120 >= lim:120 for 199.7.185.10
Sun Jun 27 16:45:28 1d:00:27:57.091 0123 1 PWD entry timeout
As result KiwiSDR don't have free channel to connect from other users.
PS I add this IP to black list on this KiwiSDR....
Comments
tower-research.com
"Quantitative Trading and Investment Strategies"
Thanks for the IP.
I wonder if this is related to the financial trading firms using shortwave radio links to shave a few milliseconds off comm links, for high frequency trading purposes (high frequency as in lots of financial trades, although in this case it also refers to high frequency radio).
They were tuned to 10 or 15 MHz - perhaps monitoring WWV or another time station for propagation research / measurement purposes?
Possibly related - I have noticed someone from Taiwan using all 7 of the KiwiSDR receivers here to monitor CHU using the signal strength extension. I do not have time limits on the receivers, and when I have noticed them they have been up for upwards of 12 hours. Then I give them the boot, ban them. They'd come back a few days later from another IP, lather, rinse repeat. They have not been back for a while now, but I probably just jinxed myself.