开云体育

Hello group,

I want to take the next step and access my Hermes-Lite via the internet and have absolutely no experience with this. I am happy to do the learning necessary to set my self up but would appreciate if someone could guide me to the first step of deciding the best way to approach this. Should I do this via VNC or will the encryption latency be too great? Perhaps ddns might be the best approach and like all hams I like a freebie so are there too many fishhooks in the free sites and should I take a subscription? Maybe there is yet another approach that I have not thought about or someone knows of a web site where the procedure has been well explained that I could follow.

I would appreciate any information that I can get.

73, Graeme ZL2APV

Sorry about VNC which should have been VPN. I have been fortunate enough to get a fixed IP address so have tried port forwarding and it seems to be going but I will need to try it off site which I will probably do tomorrow.

73, Graeme ZL2APV

Well if it is VPN, then it is not clear to me which is the scenario

a) HL2 is remote, Quisk runs locally, HPSDR data stream goes "over the internet"

b) HL2 is remote, Quisks runs *remote* on a computer connected to the HL2, only
screen contents and audio go "over the internet"

For the second case VNC & friends might work for SSB (some doubts if CW is concerned),
but for the first scenario there might be problems with the discovery process,
since not all routers, especially if VPN is involved, my route the discovery (broadcast) packages.

For my Hamlab (RedPitaya based) I added a "TCP" option to the "SDR firmware", the with an
SDR program knowing about this (my piHSPDR version) you can connect across many routers, VPNs etc.
(you have to specify the IP addr. of the radio), but the HL2 afaik only has UDP connection.

Thanks Christoph,

Option 2 is what I am using. The VPN is so I can appear as a different IP address from the internet side of my router and then I can test the connection back into my usual network address appearing as an outside machine. Something like running client and server on the same computer with localhost.. I was also trying to avoid ddns which I will sort out now with a fixed IP address.

Within my local lan Quisk is running really well in client/server mode with the server being a raspberry pi and the client my normal desktop. I have had quite a lot of CW contacts now and my next step is to try this from my daughter's house using my laptop.

73, Graeme ZL2APV

I recall that the HL2 does not understand routing, so the Quisk machine has to be on the same network as the HL2.? A VPN could accomplish this, but I think there would be too much latency for it to work.? I do remote by running Quisk on a Raspberry Pi connected directly to the HL2 and then operate the Pi via VNC.

Steve KD2USS

Hello group,

Thanks for all the responses and yes Steve I did not go for a VPN in the end. I can report that I have the radio running well on preliminary tests over the internet and it is very reliable with no dropouts using either ethernet cable or wifi at the client (ctl-head) end. I have conducted an SSB QSO using my laptop from a friends house and the communication was flawless.

My final setup is to use port forwarding with 4585 opened as TCP and 4586-7 as UDP on my wifi router. The HL2 is connected to a Raspberry Pi which does not have UFW enabled yet so that is still to be tested and these are connected to a switch which in turn is connected to my router. Quisk remote is run on my Rpi4 and I run it up using ssh with the command "DISPLAY=:0 nohup ~/quisk/quisk &". I can connect Quisk Ctl-Head from any computer inside my lan using the IP address of the Rpi4 or the network IP Address of my router. My local ISP are happy for me to have a fixed IP address so no need for ddns.

Very early days yet and while remote I have no way of triggering my antenna tuner or switching the gear on and off etc. but that will come. I need to study Jim's Pico I/O board to see exactly what facilities can be run through Quisk and rebuild a lot of my station to accommodate my new requirements.

Work needs to be done on a system to log users on so that only authorised people can access the radio as it is my intention to ultimately make the radio available to some hams who are in care facilities or apartments where an antenna is not possible yet they are still capable of running a qso or even a contest.

I guess you can imagine how excited I was to get the radio running over the internet and how grateful I am for all the work that has gone in to the project. I did set my phone up as a hotspot but I had a dreadful connection with latency ranging between 10 and 16 seconds. I can't say that I have seen it this bad before but maybe it is. In spite of this it still worked although it was a bit weird waiting 10-16 seconds after clicking on the graph for the frequency to change or TX to happen after pressing PTT but happen it did without crashing but a QSO would have been impractical.

I did not have a key with me so didn't try CW. A test for another day.

73, Graeme ZL2APV

Hello Group,

Me again but I have just managed to configure UFW on my Rpi4 and found that configuring this firewall was not 100% straight forward - mainly because I was not familiar with the commands so this may be helpful.

To install the firewall start with an up to date machine
sudo apt update
sudo apt full-upgrade

Now install the firewall
sudo apt install ufw

The firewall will be disabled by default and you need to setup some ports before enabling it
??? Please ignore the // comments
sudo ufw allow 22?? // This is the ssh port
sudo ufw limit 22?? // Limit your connections
sudo ufw allow 80?? // http port
sudo ufw allow 443? // https port
sudo ufw allow 5900 // VNC Viewer port
sudo ufw allow in from 192.168.1.198 port 1024 to any?? // Quisk hardware port
sudo ufw allow 4585/tcp // Control signals
sudo ufw allow 4586/udp // Graph stream
sudo ufw allow 4587/udp // radio sound and microphone stream

A double check before starting the firewall
sudo ufw show added
Added user rules (see 'ufw status' for running firewall):
ufw limit 22
ufw allow 80
ufw allow 443
ufw allow 5900
ufw allow from 192.168.1.198 port 1024
ufw allow 4585/tcp
ufw allow 4586/udp
ufw allow 4587/udp

Enable the firewall. If you are using ssh to set up, you won't lose your connection but will get a warning.
sudo ufw enable

Check your status
sudo ufw status numbered
Status: active

???? To???????????????????????? Action????? From
???? --???????????????????????? ------????? ----
[ 1] 22???????????????????????? LIMIT IN??? Anywhere???????????????? ?
[ 2] 80???????????????????????? ALLOW IN??? Anywhere???????????????? ?
[ 3] 443??????????????????????? ALLOW IN??? Anywhere???????????????? ?
[ 4] 5900?????????????????????? ALLOW IN??? Anywhere???????????????? ?
[ 5] Anywhere?????????????????? ALLOW IN??? 192.168.1.198 1024?????? ?
[ 6] 4585/tcp?????????????????? ALLOW IN??? Anywhere???????????????? ?
[ 7] 4586/udp?????????????????? ALLOW IN??? Anywhere???????????????? ?
[ 8] 4587/udp?????????????????? ALLOW IN??? Anywhere???????????????? ?
[ 9] 22 (v6)??????????????????? LIMIT IN??? Anywhere (v6)??????????? ?
[10] 80 (v6)??????????????????? ALLOW IN??? Anywhere (v6)??????????? ?
[11] 443 (v6)?????????????????? ALLOW IN??? Anywhere (v6)??????????? ?
[12] 5900 (v6)????????????????? ALLOW IN??? Anywhere (v6)??????????? ?
[13] 4585/tcp (v6)????????????? ALLOW IN??? Anywhere (v6)??????????? ?
[14] 4586/udp (v6)????????????? ALLOW IN??? Anywhere (v6)??????????? ?
[15] 4587/udp (v6)????????????? ALLOW IN??? Anywhere (v6)

By using the "numbered" parameter you can easily delete etc. by using the number
sudo delete 11
sudo delete 3?? // would have removed "443"

"sudo ufw enable" or "sudo ufw disable" to start and stop the firewall

73, Graeme ZL2APV

Steve Gaarder KD2USS napsal(a):

I recall that the HL2 does not understand routing, so the Quisk machine has to be on the same network as the HL2.? A VPN could accomplish this, but I think there would be too much latency for it to work.? I do remote by running Quisk on a Raspberry Pi connected directly to the HL2 and then operate the Pi via VNC.
Steve KD2USS

I think the original question was about the quisk remote control feature (which is now built-in in quisk), i.e.:

[quisk-control-head] <--internet--> [quisk-remote] <--LAN--> [HL2]

And it works pretty well over internet, no VNC is needed

73! Jaroslav, OK2JRQ

This is very exciting news, both from Graeme and Jaroslav!

Thanks for the reports and info, and many thanks to Jim for all his work integrating and debugging!

-- Ben, AC2YD --