Best Recent Content

  • Damage due to nearby lightning strike

  • https site not shown in public list

    Done!

    I had two scenarios that didn't work, see below.

    • connect to http://<mysite>:8073
    • connect to http://<mysite>:8074 (now fixed)
    • connect to https://<mysite>:8073 (now fixed)
    • connect to https://<mysite>:8074

    In the list of stations, kiwisdr.com still lists my station as a http site, but at least it's back on.

    Whatever way visitors connect, the link will always be upgraded to https. The biggest bonus is that it's no longer interfering with browsers wanting to prefer https once they've seen it available on a domain.

    I might spend some more time in the future to see if I can have it running all over 8073 again, but for now I'm pretty happy with how it works.


    For those interested in the details:

    Raspberry Pi B+ Rev1.2

    Raspbian 10.10

    Nginx 1.14.2-2


    # /etc/nginx/sites-available/kwisdr-reverseproxy.conf

    server {

       listen 10.0.0.10:8073; # listen on 8073

       server_name www.marcelpost.com:8073;


       ssl on;

       ssl_certificate     /etc/letsencrypt/live/www.marcelpost.com/fullchain.pem;

       ssl_certificate_key /etc/letsencrypt/live/www.marcelpost.com/privkey.pem;


       # redirect any incoming http to https and port 8074

        return 301 https://www.marcelpost.com:8074$request_uri;

    }


    server {

       listen         10.0.0.10:8074; # listen on 8074

       server_name    www.marcelpost.com:8074;


       ssl on;

       ssl_certificate     /etc/letsencrypt/live/www.marcelpost.com/fullchain.pem;

       ssl_certificate_key /etc/letsencrypt/live/www.marcelpost.com/privkey.pem;


       # takes care of http connections on 8074 (redirect to https 8074)

        error_page 497 https://$host:$server_port$request_uri;


       location / {

           proxy_buffering    off;

           proxy_set_header   Host $http_host;

           proxy_set_header   X-Real-IP $remote_addr;

           proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;

           proxy_set_header   X-Forwarded-Proto http;

            proxy_pass          http://10.0.1.20:8074;  # server ip address of KiwiSDR


       }

    }


    The only other thing I had to change in /etc/nginx.conf was to uncomment:

    server_names_hash_bucket_size 64;

    This may not be necessary but I had this 'could not build server_names_hash' error which was fixed by uncommenting the above line.


    Thanks everyone for their input.

    Powernumptyrz3dvp
  • possible feature : TUNING lock

    I wish we could revisit the lock function... there is far too much area that one can click on (inadvertently) and knock oneself way off frequency. Asking for a klutzy friend....

    ChrisSmolinski
  • Possible detection of solar Type-II/III radio emissions on kiwisdr

    This was in the middle of the day, and it was a different solar radio burst to what you saw (May 22nd 2021).

    73

    Mark VK5QI

    HB9TMC
  • Possible detection of solar Type-II/III radio emissions on kiwisdr

    I've spotted similar on the VK5ARG KiwiSDR:

    At first I thought there was some issue with the site, or someone had driven a RF-noisy car up to the antenna, but It was also visible on the Australian Bureau of Meteorology's Learmonth Spectrograph.

    73

    Mark VK5QI

    HB9TMC
  • Possible detection of solar Type-II/III radio emissions on kiwisdr

    During a solar coronal mass ejection, the ejecta generates radio emissions as it plunges through the suns chromosphere and corona. These emissions can be received on earth. There are different types of radio emissions, shown in the spectrogram examples on this page:

    https://en.wikipedia.org/wiki/Solar_radio_emission#/media/File:Solar_Radio_Bursts_Types_I,_II,_and_III.jpg


    Early in the year, I observed a noise pattern in my kiwisdrs spectrogram that coincidentally happened at the same time as a solar flare with CME. I was sceptical, so I haven't thought further about this.


    On June 9th 2021, I saw the same pattern again, at the same time of a CME associated to a C3.8 LDE flare, with officially confirmed type-II radio emission.

    I was still sceptical if it was really what I was seeing on my kiwisdr.

    Here is a spectrogram of the event. Note that I have set the spectrogram very sensitive (low dynamic range) for the purpose of showing background noise. So DSL and PLC noise from more than 50 meters away can be seen. Also I have some LC filters installed, to prevent receiver saturation from strong broadcast stations. WF-rate 1 Hz. Suspected radio emission is circled red:

    Below 5 MHz no emission was recorded (on a separate kiwisdr with different filters). But the signal would be attenuated by the ionospheric D-layer anyway, so it can't reach earth surface.


    Now, today there was a powerful X1.59 flare. And my kiwisdr shows again this pattern. This time also with a distinctive radio blackout, as expected from a X-class flare.


    73

    LX1DQ
  • TDOA possibly offline from 28 June 2021 [fixed]

    Should be okay now. Someone made a weird Kiwi configuration which broke the TDoA script on kiwisdr.com. This has happened once before I believe.

    WA2ZKD
  • Many connections from 199.7.185.10

    tower-research.com

    "Quantitative Trading and Investment Strategies"

    Thanks for the IP.

    rz3dvp
  • Many connections from 199.7.185.10

    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....


    PowernumptyHB9TMC
  • Automatic Link Establishment - MIL-STD-188-141a (ALE 2G) decoding extension

    Your signal (recorded), from my latest standalone version (not merged into Kiwi extension yet) with more decoding:

    [00:00:22] [FRQ 0.00] [To: ] [His BER: 3]
    [00:00:22] [FRQ 0.00] [CMD] [AMD: "THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG"] [His BER: 3]
    [00:00:24] [FRQ 0.00] [Sounding THIS WAS] [From: BAS ] [His BER: 2]
    


    Others (from recordings people sent me), including a DTM:

    [00:00:30] [FRQ 0.00] [Call] [From: G8JNJ0 ] [To: G8JNJ3] [His BER: 0]
    [00:00:38] [FRQ 0.00] [Call ACK] [From: G8JNJ3 ] [To: G8JNJ0] [His BER: 20]
    [00:00:42] [FRQ 0.00] [Call EST] [From: G8JNJ0 ] [To: G8JNJ3] [His BER: 0]
    [00:00:54] [FRQ 0.00] [CMD] [AMD: "MESSAGE READS 12345"] [His BER: 0]
    [00:01:04] [FRQ 0.00] [Call] [From: G8JNJ0 ] [To: G8JNJ3] [His BER: 10]
    [00:01:04] [FRQ 0.00] [CMD] [AMD: "CONFIRM 54321"] [His BER: 10]
    


    [00:00:31] [FRQ 0.00] [Call] [From: SHAEENQ2 ] [To: USMANQ7] [His BER: 1]
    [00:00:31] [FRQ 0.00] [CMD] [DTM: "WE ALSO PASSED MSG TO OUR SECTION ALREDY TODAY MORNING ABOUT HOLIDAY HERE"] [His BER: 1]
    


    WA2ZKD