|
Re: KiwiSDR dynamic IP address
Gur Lavie
Yohoooo,
I was missing in /etc/ssh/sshd_config an explicit directive : GatewayPorts yes :) It now works like magic ! Amazing ! Rob - you are amazing ! The script is so nice and elegant. Really a jam. And I can't close without a question ... I guess I now need to automate or spawn the tunnel creation from the kiwi side into an automatic independent way - not through the Console. Because with timeout I am loosing the Console and then the tunnel I am very cautious with touching the Kiwi files, not to lose access... Any recommended/preferred way ? Thanks for all the help ! Gur
|
|
|
|
Re: KiwiSDR dynamic IP address
Rob Robinett
Unless there are iptables rules which suppress such traffic, SERVER:8073 will be global and any packets sent to it from any IP address will be forwarded through the tunnel to the Kiwi where they will be delivered to the Kiwi's localhost:8073 port. run: "sudo iptables -L "to see if there are any such rules.
On Sun, Nov 14, 2021 at 9:43 AM Gur Lavie <gurlavie@...> wrote: hehehe I had to keep myself concentrated for 2 hours to get this done :) not an easy task.... --
|
|
|
|
Re: KiwiSDR dynamic IP address
Gur Lavie
hehehe I had to keep myself concentrated for 2 hours to get this done :) not an easy task....
I was indeed testing accessing the kiwi through the SERVER:8073.....but it didn't work... I am thinking that the "tunnel" I opened from the kiwi local console which is "interactive" might be "local" to the context of the kiwi console session ? and the port forwarding might not be globally available ? hence not seen by others ?
|
|
|
|
Re: KiwiSDR dynamic IP address
Rob Robinett
Congratulations! It took me 2 years to get that far with ssh ;=) While the Kiiw's ssh session with your server is active, you should be about to access the Kiwi at: http://SERVER_IP:8073. The config of WD running on SERVER should list your Kiwi receiver at 'localhost:8073'
On Sun, Nov 14, 2021 at 9:06 AM Gur Lavie <gurlavie@...> wrote: Hi again, --
|
|
|
|
Re: KiwiSDR dynamic IP address
Gur Lavie
Hi again,
I managed to work around the passwords (with the keys and ssh-copy-id remote_username@server_ip_address). So on the SERVER (and WD computer), I am running fine: "connect_to_wd_daemon is running with pid 26374" On the KIWI console after executing ssh -R 8073:localhost:8073 kiwisdr@... I am seeing the SERVER prompt. And in the wsprdaemon.conf, I have the KIWI defined as : "KIWI_0 192.168.68.125:8073 " Which means it IS NOT listing the KIWI address but the "remote" side of the tunnel. But no WD connections on the kiwi... Any suggestions ?
|
|
|
|
Re: KiwiSDR dynamic IP address
Gur Lavie
On Thu, Nov 11, 2021 at 10:24 AM, Rob Robinett wrote:
ssh -R 8073:localhost:8073 someuser@...Hi, The tunnel method looks super advanced and really fun. I tried to deploy it, but I guess I am falling on the trivial things I am missing. Should I generate public/private key so I can login without password ? On the Kiwi, the command sh -R 8073:localhost:8073 kiwisdr@... succeeded prompting the password and then entering a remote shell on the "Server" But on the SERVER (which also runs WD), the password prompt is asynchronous
Gur
|
|
|
|
Re: KiwiSDR dynamic IP address
Rob Robinett
Another solution would be to have your Kiwis maintain ssh sessions with your Pi (or another server with a static IP address) and forward ports on that Pi/server back to the Kiwis port 8073 through the tunnels created by that ssh session. For example: on the Kiwi cmd line run 'ssh -R 8073:localhost:8073 someuser@...'. Then your WD would be configured to access that Kiwi at 'someserver.net:8073' I have attached a script which maintains such a session at one WD site. After running it once you will need to modify the wd-tunnels.conf for your environment and configure a user account on 'some_server' and set up that account to allow your Kiwi to autologin. Of course there will be interruptions when your Kiwis change IP addresses while the current listener ssh sessions to your PI/server timeout and are re-established.
--
|
|
|
|
Re: KiwiSDR dynamic IP address
Rob Robinett
If your DNS service tracks the changing IP address of your Kiwis, then you could specify the DNS names of the Kiwis. When their IP address changes the WD sessions would error and WD would retry a session at the new IP address supplied by your DNS server. If your DNS server doesn't track that, then you could write a little script to maintain the correct IP addresses in your Pi's /etc/hosts file.
On Thu, Nov 11, 2021 at 9:41 AM Gur Lavie <gurlavie@...> wrote: Hi, --
|
|
|
|
KiwiSDR dynamic IP address
Gur Lavie
Hi,
Because of some network configuration problem, my KIWISDR is changing its IP address every few hours. Is there a method to periodically update the address in the wsprdaemon.conf file ? Thanks Gur
|
|
|
|
Re: E: Package 'qt5-default' has no installation candidate
Rob Robinett
I'm glad you got it installed on that new Raspian "bullseye". I wasn't aware there was a successor to buster and will add testing of installation on that version to my 'todo' list.
As I recall, the qt5 package is required by components of WSJT-x which aren't used by WD. So a fake installation should work and you may have helped my debugging of installation on bullseye The easiest way to view the status of WD's connection to your Kiwis is to go to the Kiwi's Admin->Users page. There is a uploading daemon log file which can be viewed with some difficulty on v2.10k. In another forum thread I describe how to enable and view that logging. In WD v3.0 I will make it much easier to see those logs.
|
|
|
|
Re: E: Package 'qt5-default' has no installation candidate
Gur Lavie
ok.
It works great. Amazing. Really amazing. both the simplicity and quality. I see now that the "version" on http://wsprd.vk7jj.com/ is listed as "WD_2.10k" I had to go with the "fake" package for "qr5-default" as listed in the link I posted below. But I guess since I am just using it for wspr it is good enough. Just curious, if I am running the daemon on one computer, is there a way to connect from a remote computer with a "UI" for the FT8 and other digital modes ?
|
|
|
|
Re: E: Package 'qt5-default' has no installation candidate
Gur Lavie
Hi,
Another piece of information which might be important is that I am trying to set it as "headless". No GUI, automatic WSPR spot uploading. Is there a simple way to test if the connection to the KIWISDR system is active ? Is there a log of decoded Sports ? I guess this is really trivial question. From my reading in the forum it looks like everyone here are super experienced, while I am really just doing first steps. Thanks ! Gur
|
|
|
|
Re: E: Package 'qt5-default' has no installation candidate
Gur Lavie
Hi,
Its : Raspberry Pi 3 Model B Rev 1.2 Linux raspberrypi 5.10.63-v7+ #1459 SMP Wed Oct 6 16:41:10 BST 2021 armv7l GNU/Linux PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
|
|
|
|
How to resolve FATAL ERROR: Failed to install 'qt5-default' on RaspberryPi during Wsprdaemon fresh install
Gur Lavie
Hi,
First time installing Wsprdaemon on raspberryPi, targeting wspr decoding from KiwiSDR. Keep failing ./wsprdaemon.sh -V on the message : E: Package 'qt5-default' has no installation candidate
FATAL ERROR: Failed to install 'qt5-default' which is needed to run the 'jt9' copmmand in wsprd V2.3.xxxx What am I missing ? Thanks Gur
|
|
|
|
Re: E: Package 'qt5-default' has no installation candidate
Rob Robinett
What Pi and what version of Raspian? I test installation only on the latest 'buster'
On Wed, Nov 10, 2021 at 2:37 PM Gur Lavie <gurlavie@...> wrote: Hi, --
|
|
|
|
E: Package 'qt5-default' has no installation candidate
Gur Lavie
Hi,
Fresh install on RaspberryPi. I cant work around this error - "E: Package 'qt5-default' has no installation candidate". "FATAL ERROR: Failed to install 'qt5-default' which is needed to run the 'jt9' copmmand in wsprd V2.3.xxxx" I am reading in this link, about creating a fake package, to by pass the error - https://askubuntu.com/questions/1335184/qt5-default-not-in-ubuntu-21-04 I didnt find any reference to this in the forum messages. Thanks! Gur
|
|
|
|
Re: wsprdaemon tmp file questions
Yes, those are the cached spots from when your Pi couldn't reach wsprnet.org
One WD has reconnected WD will upload in batches of up to 1000 the oldest cached spots until it catches up with real time.
In WD 3.0 I have fixed and enhanced that cache upload service and also made it easier to view the operation of that upload service.
On Tue, Nov 9, 2021 at 12:41 PM Chris M <nvhengr@...> wrote:
--
|
|
|
|
Re: Dupes
Rob Robinett
Hi Alan, Since 'dups' are a frequent source of questions in my wsprdaemon group, I have included that group in this response. Your 60M 'dups' are certainly not a problem for wsprdaemon, but due to limits in wsprnet.org's spot reporting, as detailed by Phil below, he can't easily detect your 'tx-generated-dups' among the many more 'receive-site-dups' recorded by receive sites which use multiple copies of WSJT-x or other SW packages. Those 'receive site generated dups' waste transfer bandwidth, CPU time and storage space at wsprnet.org, and some sites are recording almost 20,000 dups per day. And snce there is no way to differentiate between the antenna+receivers generating those duplicate spots, there is no useful information which can be learned from them. Receive sites using my wsprdaemon SW separately report 60M and 60eu, but they are separate bands because one 3 kHz rx channel can't cover both of those 'bands'. There is an analogous situation on the 80M and legacy 80eu bands. In contrast,wsprdaemon reports only one rx_band+tx_call+tx_grid signal for each WSPR cycle. It also includes the capability to define a single logical receiver whose spots are taken from the antenna+receiver with the best SNR on each WSPR cycle. Further, all spots from all antenna+receivers can be uploaded to the wsprdaemon.org database where the individual antenna+receiver spots can be analyzed and displayed. But if you want to compare the performance of your two transmitter+antenna systems, I would think you could learn a lot more if they used different transmit call signs. 73, Rob
On Sun, Oct 31, 2021 at 2:58 PM Philip Barnard <vk7jj@...> wrote:
--
|
|
|
|
Dupes suddenly not zero anymore
Rob Robinett
FYI… ---------- Forwarded message --------- From: Phil <phil@...> Date: Fri, Oct 29, 2021 at 3:38 PM Subject: Re: Dupes suddenly not zero anymore To: Rob Robinett <rob@...> CC: John Huggins <john.huggins.ee@...>, <wsprdaemon@groups.io> Hi Rob, John. All the 60m data we get from WSPRnet's API for the 60m band is a mixture of 5.2Mhz and 5.3MHz spots. Thus Arne's db can only be queried on the basis of band = 5 and the WD database where wd_band = '60' and both dbs return a mixture of 5.2Mhz and 5.3MHz spots. There is a solution using advanced search based on frequency. For wsprd.vk7jj.com (accessing the WD Postgres db) you should select 60m from the band menu and then use either and "MHz" < '5.3' or and "MHz" > '5.3' as per the screen shot below. For wspr.rocks (accessing Arne's ClickHouse db) the syntax is different and frequency < '5300000' or and frequency > '5300000' The same works for the 4m band or for different segments of the 2m band or for 27MHz, though in those cases the band menu should be set to "all bands". The queries can be combined, eg for 70MHz the Spanish allocation is 70.150 to 70.200 ref. https://www.wsprnet.org/drupal/node/4836 and frequency > '70100000' and frequency < '70200000' Regards Phil. 
--
|
|
|
|
Re: Dupes suddenly not zero anymore
Jim Lill
on jimlill.com:8088 I count those bands separately. I stopped
counting dupes after I found it caused rancor amongst some...
On 10/29/21 10:01 AM, Rob Robinett
wrote:
|
|
|
