Elecraft

K4 remote protocol

Classic

List

Threaded

3 messages Options

K5WA

K4 remote protocol

This may be a Wayne/Eric question but if anyone else knows for sure, please chime in.

I’m setting up a new remote system and want to plan properly for the pair of K4s I’ve got ordered. Is the ethernet communication between a K4 and its Elecraft remote software TCP or HTTP? I’m assuming TCP but thought I’d better check.

I’m having to go through an ATT Mobile system (CGNAT) with NGROK tunnels and I’m up against a limit on reserved TCP tunnels so want to make sure I’m going the right direction before I spring for more reserved TCP tunnels. 😉 The station is WAY out in the country and that is why I’m stuck with a mobile cellular ISP.

Thanks,

Bob K5WA

Houston, TX

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Steve Anness

Re: K4 remote protocol

Hello Bob,

I will definitely let someone more familiar with the Elecraft remote answer
in more detail but I did want to share. TCP and HTTP protocols happen at
different layers of the network stack. TCP is at the transport layer, it
defines how to send the data and deals with the actual transport of packets
around the network. Whereas HTTP is just the common language at the
application layer, at the very core it is just an instruction set. In
short, you can use TCP and HTTP together , you can have TCP without HTTP.

It sounds like you are trying to address a very common problem, which is
true with most ISPs these days, almost no one has a dedicated IP address
anymore unless they are paying for business level services. There are
numerous ways to solve this, the easiest and "free" way would just be port
forwarding on your router, of course perhaps you already thought of this
and if your ATT Mobile system is actually just a wifi hotspot and your
router doesn't support that than of course the port forwarding isn't an
option.

So assuming perhaps that you have already looked at port forwarding and
Dynamic DNS and settled on NGROK, the real question is going to be how many
connections do they make.
I did look at some of the Elecraft Documentation, there does appear to be
an HTTP component for connecting to your K3 Remote via a web browser, I
also saw reference to TCP port 4626 for the KPA-500 remote. I don't know
what other port ranges they use but my gut (and experience with networking)
tells me that the free version with 4 tunnels will likely work fine.

I hope this helps, feel free to reach out to me off the list for any
networking related questions. I will let the Elecraft experts speak to
their software.

73 de KJ5T

On Thu, May 21, 2020 at 11:09 AM K5WA <[hidden email]> wrote:

> This may be a Wayne/Eric question but if anyone else knows for sure,
> please chime in.
>
>
>
> I’m setting up a new remote system and want to plan properly for the pair
> of K4s I’ve got ordered. Is the ethernet communication between a K4 and
> its Elecraft remote software TCP or HTTP? I’m assuming TCP but thought I’d
> better check.
>
>
>
> I’m having to go through an ATT Mobile system (CGNAT) with NGROK tunnels
> and I’m up against a limit on reserved TCP tunnels so want to make sure I’m
> going the right direction before I spring for more reserved TCP tunnels.
> 😉 The station is WAY out in the country and that is why I’m stuck with a
> mobile cellular ISP.
>
>
>
> Thanks,
>
>
>
> Bob K5WA
>
> Houston, TX
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Lynn W. Taylor, WB6UUT-3

Re: K4 remote protocol

In reply to this post by K5WA

HTTP runs over TCP, so either way, we're talking about TCP.

Here is what I'd do.

Dig into OpenVPN. It's open source software, you can buy routers that
handle it natively, or you can put an Raspberry Pi 3 on the end of your
link. There is client software for just about everything out there.

This is the correct use for a VPN (most of the advertised VPNs offer
"security" that doesn't actually exist).

You open up the VPN whereever you are, and you have one connection that
magically becomes a really long ethernet cable.

Your device anywhere in the world is on the LAN at your remote station.

Doesn't matter if you have 5 connections, or 5,000. As far as AT&T can
tell, it's just one.

73 -- Lynn

On 5/21/20 9:08 AM, K5WA wrote:

> This may be a Wayne/Eric question but if anyone else knows for sure, please chime in.
>
>
>
> I’m setting up a new remote system and want to plan properly for the pair of K4s I’ve got ordered. Is the ethernet communication between a K4 and its Elecraft remote software TCP or HTTP? I’m assuming TCP but thought I’d better check.
>
>
>
> I’m having to go through an ATT Mobile system (CGNAT) with NGROK tunnels and I’m up against a limit on reserved TCP tunnels so want to make sure I’m going the right direction before I spring for more reserved TCP tunnels. 😉 The station is WAY out in the country and that is why I’m stuck with a mobile cellular ISP.
>
>
>
> Thanks,
>
>
>
> Bob K5WA
>
> Houston, TX
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]
>