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

Lynn W. Taylor, WB6UUT KX3 at ColdRocksHotBrooms.com
Fri Dec 20 16:12:26 EST 2013


Dynamic DNS services are a different way of achieving a similar goal.

What they don't do is free someone from configuring a firewall at the 
radio-end.

The method I outlined works with just about every translating firewall.  
You don't have to mess with pass-thrus or proxies or know port numbers 
or fiddle with a "DMZ" (which is never a true DMZ).

You don't even care about the private IP of the "radio end" or how many 
times the address gets translated.

On 12/20/2013 12:52 PM, David Christ wrote:
> Exactly.
>
> I have a friend who uses this service so he can always reach his home network by name without having a static IP.  Perhaps this can be of use to some on the list.
>
> http://dyn.com/support/clients/
>
> And it has been working very well according to him.
>
> David K0LUM
>
> On Dec 20, 2013, at 11:46 AM, Lynn W. Taylor, WB6UUT wrote:
>
>> 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
> ______________________________________________________________
> 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
>



More information about the Elecraft mailing list