[Elecraft] Fwd: K3/0 to K3 RemoteRig issue

[Lynn W. Taylor, WB6UUT]

I ran an internet service provider for a couple of decades.

The sad part of this is that there is a standard solution to all of 
this, the same one that works for Skype and BitTorrent.

The radio end needs to send a message to some central server (run by 
RemoteRig) that says "I'm on, my 'name' is N1AL" or whatever identifier 
seems reasonable.

The server sees the message, gets the apparent public IP from the 
header, and records it.  The updates have to be every minute or two, but 
they can be UDP to minimize bandwidth and connections.

The client (at Starbucks) sends a message to the central server saying 
"I want to operate N1AL" and the server says "connect to this IP using 
these port numbers."

The next time the station checks in (about half the update interval on 
average) the server tells the station "connect to the operator's IP 
using these port numbers."

Because the typical firewall opens up circuits for outgoing connections, 
the NAT firewall at Starbucks and the NAT firewall at the station both 
open the correct ports, thinking that they're connecting out, and not 
realizing they're being tricked into allowing a connection in -- it's 
okay because it has been coordinated through the central server.

No static IP addresses, no messing with port forwarding, no trying to 
get your IT department to let you operate during your lunch break.

There are a few missing details, but that's how most everything else works.

-- Lynn

On 12/20/2013 5:15 AM, bwruble at gmail.com wrote:
> What was so bizarre in all this --- i should be able to take the K3/0 plus RemoteRig control box (RRC) to a local Starbucks and get on the air using wifi.