[Elecraft] K4 Remote Lives and Breathes!

[Magnus Danielson]

This issue is real. A problem is also there is quite many port forward 
configurations to setup as one setup a station.

There is methods to punch through NATs, and I hope one have chosen to 
use an approach that does this. One is to operate over a VPN that have 
these abilities. Another is to use a standard tunnel usinging say TLS 
that also include the punch-through capabilities.

Also, IPv6 is starting to replace the IPv4 NAT/CG-NAT hell. It's been a 
long coming for sure, but there is plenty of signs it is happening. 
While initial release may be IPv4 limited, IPv6 should be high up on the 
list of thigns to fix if it is not already handled. This should not be 
relevant only for the K4, but any device.

When wearing another set of hats, I work on these issues.

73 Magnus SA0MAD

On 2023-12-15 10:42, Dave wrote:
> Very interesting Rick, thanks for sharing the info.
>
> One issue that seems to be increasingly common is that some (many?) ISPs no
> longer offer a fixed IP address, which K4 Remote currently needs. The
> system many ISPs are changing to is carrier grade network address
> translation, it first surfaced in mobile networks, but is spreading to home
> broadband too as ISPs run out of IPv4 addresses, see:
> https://en.wikipedia.org/wiki/Carrier-grade_NAT
>
> A way around this is with the use of a central server, which isn't usually
> free. Remote TX works in this way but uses a Raspberry Pi. I note they
> support the K3. https://www.remotetx.net/
>
> 73 Dave G4AON
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to magnus at rubidium.se