rz3dvp

Нi all,

I don't know why someone use the TOR for connect to KiwiSDR if he is an honest listener?

Maybe add block TOR network on the proxy.kiwisdr.com server?

It's don't difficult, for example on Ubuntu:

1. install ipset: >sudo apt install ipset

2. create new set tor: >sudo ipset -N tor iphash

3. add new bash script like this: 

#!/bin/bash

wget -q https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=YOUR_IP -O -|sed '/^#/d' | while read IP

do

  ipset -q -A tor $IP

done

4. make it executable and start with sudo, if all fine - check new set: >sudo ipset -L tor(you should see a lot of IP's on this set)

5. then add this set to INPUT iptables: >sudo iptables -I INPUT -m set --match-set tor src -j DROP

6. and add to root CRON rule for restart this bash script every 5 hours (for example)...

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

Hi Jeff, you can test img from Dropbox? I downloaded it and see it's have more newer version than in KiwiSDR box - 1.46...
http://kiwisdr.com/quickstart/index.html#id-dload
And be patient first upgrade need lot of time ~45-60 min
Hope it's helpful...

Now looks very well!

Thank you!

Hi James, looks cool
But be careful, heatsink on BB-AI fixed only on sticky thermal interface and I'm not sure how it will behave over time (about year) on high temp...
You add lever arm to it. Maybe you know about FlexRadio 6400/6600 problem when similar heatsink installed vertical goes down under the influence of time and gravity.

You can build it manualy on SSH console connection.
For first time try use ./up script:
- connect to KiwiSDR console via SSH (you can use Putty for Windows) with debian user
> sudo su (type debian password again)
> cdp
> ./up
and wait about 40 min for build current version

if problems didn’t goes you can build KiwiSDR software from Github and then copy config from old version... look this post for fix serious problems: http://forum.kiwisdr.com/discussion/comment/8480#Comment_8480

Hello friends,
As you probably know know, for normal start BBG board need fast +5V voltage rise from PSU, if you use powerful transformer PSU you can have problem with autostart KiwiSDR after power outage.
Info from https://groups.google.com/forum/#!topic/beagleboard/aXv6An1xfqI[151-175]: "The BBG uses the TPS65217 power management IC. Per the data sheet, it will not turn on if the applied power has a ramp of greater than 50 mSec."

I have this problem with one of my PSU's, when BBG don't start after power lost and I installed device with 10s delay for allow power from PSU and it was very helpful for me:
https://www.ebay.com/itm/LED-Home-Automation-Delay-Timer-Control-Switch-Relay-Module-Digital-display-PLC/252867596893?ssPageName=STRK:MEBIDX:IT&var=551880757238&_trksid=p2060353.m1438.l2649



Maybe this info was halpfull for something else.

73! Yuri

Hello friends,
As you probably know know, for normal start BBG board need fast +5V voltage rise from PSU, if you use powerful transformer PSU you can have problem with autostart KiwiSDR after power outage.
Info from https://groups.google.com/forum/#!topic/beagleboard/aXv6An1xfqI[151-175]: "The BBG uses the TPS65217 power management IC. Per the data sheet, it will not turn on if the applied power has a ramp of greater than 50 mSec."

I have this problem with one of my PSU's, when BBG don't start after power lost and I installed device with 10s delay for allow power from PSU and it was very helpful for me:
https://www.ebay.com/itm/LED-Home-Automation-Delay-Timer-Control-Switch-Relay-Module-Digital-display-PLC/252867596893?ssPageName=STRK:MEBIDX:IT&var=551880757238&_trksid=p2060353.m1438.l2649



Maybe this info was halpfull for something else.

73! Yuri

Hi, my friend @sudentkra wrote simple Java script for this Christmas time:

<script type="text/javascript">document.addEventListener('DOMContentLoaded', function(){document.querySelectorAll("#id-left-logo").forEach(function(item) {item.src = "https://i.ibb.co/G3scxvc/santa-kiwi-with-head.png"; }); });;</script>

if you add this to Webpage - Owner info, your Kiwi will looks funny:

Merry Christmas and Happy New Year!

http://195.222.165.118:8073/ my AirBand KiwiSDR with passive mixer (QTH near SVO airoport Moscow).