Date   

Re: WSPR reports on 40M, also config includes only 20M

Rob Robinett
 

Also, did you stop WD before making the change to its conf file?  You might stop WD (WD -z) and then start if again (WD -a) to ensure it is using the current version of the config file.

On Sat, Nov 20, 2021 at 2:18 PM Rob Robinett via groups.io <rob=robinett.us@groups.io> wrote:
Hi Gur,

Boy, you have so much RF noise that it is a wonder that you hear anything.
Also, you are tracking only 3 GPS satellites, so are you sure of the accuracy of the Kiwi's tuning?  If the WSPR signal is near the band edge your Kiwi might move it outside the 1400-1600 hz band.


Rob


Screen Shot 2021-11-20 at 2.12.36 PM.png

On Sat, Nov 20, 2021 at 1:51 PM Gur Lavie <gurlavie@...> wrote:
Hi,

My Kiwi is here - http://84.228.126.167:8073/

I am testing a problem where my Kiwi doesn't detect a local transmitter at 14.07Mhz.
I am testing now a configuration where
1. "WSPR extensions" are only defined on 20M - they don't decode anything
2. WSPRDAEMON config is set to 20M only :
declare WSPR_SCHEDULE_simple=(
    "00:00                       KIWI_0,20"
)

Still, in wsprnet, I keep seeing reports for WSPRDAEMON detecting 40M transmissions :


How can this be ? If I didnt set WSPRDAEMON to decode 40M ?

Thanks !



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: WSPR reports on 40M, also config includes only 20M

Rob Robinett
 

Hi Gur,

Boy, you have so much RF noise that it is a wonder that you hear anything.
Also, you are tracking only 3 GPS satellites, so are you sure of the accuracy of the Kiwi's tuning?  If the WSPR signal is near the band edge your Kiwi might move it outside the 1400-1600 hz band.


Rob


Screen Shot 2021-11-20 at 2.12.36 PM.png


On Sat, Nov 20, 2021 at 1:51 PM Gur Lavie <gurlavie@...> wrote:
Hi,

My Kiwi is here - http://84.228.126.167:8073/

I am testing a problem where my Kiwi doesn't detect a local transmitter at 14.07Mhz.
I am testing now a configuration where
1. "WSPR extensions" are only defined on 20M - they don't decode anything
2. WSPRDAEMON config is set to 20M only :
declare WSPR_SCHEDULE_simple=(
    "00:00                       KIWI_0,20"
)

Still, in wsprnet, I keep seeing reports for WSPRDAEMON detecting 40M transmissions :


How can this be ? If I didnt set WSPRDAEMON to decode 40M ?

Thanks !



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: WSPR reports on 40M, also config includes only 20M

Gur Lavie
 

Please look only at the last hour/ or last 4 hours.
I did several tests over the last few days....


Re: WSPR reports on 40M, also config includes only 20M

Jim Lill
 

I see a mix or 20 and 40M looking into the raw data from wsprnet

On 11/20/21 4:51 PM, Gur Lavie wrote:

Hi,

My Kiwi is here - http://84.228.126.167:8073/

I am testing a problem where my Kiwi doesn't detect a local transmitter at 14.07Mhz.
I am testing now a configuration where
1. "WSPR extensions" are only defined on 20M - they don't decode anything
2. WSPRDAEMON config is set to 20M only :
declare WSPR_SCHEDULE_simple=(
    "00:00                       KIWI_0,20"
)

Still, in wsprnet, I keep seeing reports for WSPRDAEMON detecting 40M transmissions :


How can this be ? If I didnt set WSPRDAEMON to decode 40M ?

Thanks !


WSPR reports on 40M, also config includes only 20M

Gur Lavie
 

Hi,

My Kiwi is here - http://84.228.126.167:8073/

I am testing a problem where my Kiwi doesn't detect a local transmitter at 14.07Mhz.
I am testing now a configuration where
1. "WSPR extensions" are only defined on 20M - they don't decode anything
2. WSPRDAEMON config is set to 20M only :
declare WSPR_SCHEDULE_simple=(
    "00:00                       KIWI_0,20"
)

Still, in wsprnet, I keep seeing reports for WSPRDAEMON detecting 40M transmissions :


How can this be ? If I didnt set WSPRDAEMON to decode 40M ?

Thanks !


Re: KiwiSDR dynamic IP address

Gur Lavie
 

ok sorry. I guess its in the script :)


Re: KiwiSDR dynamic IP address

Gur Lavie
 

Thanks.
But maybe I missed something. 
I still need a way to run the RSS command.....
 ssh -R 8073:localhost:8073 kiwisdr@...

I need to automate it ?

Gur


Re: KiwiSDR dynamic IP address

Rob Robinett
 

Good debugging!
The tunnel is a Kiwi daemon which will restart if the ssh session from the Kiwi to your server fails.

In order for that daemon to start during a Kiwi power cycle or reboot, there needs to be a systemctl configuration file registered with Llinux on the Kiwi.  I'll put adding that feature on my 'TODO' list for the next time I'm working with Kiwis
 

On Sun, Nov 14, 2021 at 10:14 AM Gur Lavie <gurlavie@...> wrote:
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



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


Re: KiwiSDR dynamic IP address

Rob Robinett
 

First, on the Kiwi run:

To see the status of of your tunnel:                                  ./wd-tunnel.sh -s  
To watch the log file output of the running tunnel run:     ./wd-tunnel.sh -l


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

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 ?



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


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,

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 ?



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


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.


On Thu, Nov 11, 2021 at 9:59 AM Rob Robinett via groups.io <rob=robinett.us@groups.io> wrote:
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,

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



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


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,

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



--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


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 ?

1121 - 1140 of 1670