[Elecraft] Elecraft K3 RemoteRig Issue - Remote radio won't power off

[Dave B]

On 28/01/17 01:12, elecraft-request at mailman.qth.net wrote:
> Message: 13
> Date: Fri, 27 Jan 2017 10:22:21 -0800
> From: Rick Tavan <rick at tavan.com>
> To: Elecraft Reflector <elecraft at mailman.qth.net>
> Subject: [Elecraft] K3 RemoteRig Issue - Remote radio won't power off
> 	fully
> Message-ID:
> 	<CANVONA+K85SbOyYLCnqhuL7LNFUzue8x6e9KuKRSgjF1b-nZVQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Recently I had to replace the router at my remote site. The replacement
> router is the same model as its predecessor (Cisco EA4500). I had good, but
> possibly imperfect, records of the port forwarding setup which I reproduced
> on the replacement router. Now, pressing POWER on the Control K3 turns the
> Remote K3 ON and operates correctly, but when I turn off the Control K3,
> the Remote K3 stays on. If I then tap the POWER button on the Remote K3,
> its screen goes solid amber with no LCD segments lit, but it does not fully
> power down. It also becomes catatonic, its own POWER button useless, but
> it's still responsive to power on from the Control K3. I have Restarted
> both RemoteRig boxes to no avail. I have confirmed that my DDNS real IP
> address is correct.
>
> In case it's material, here are the port forwards I have in place:
>
> RRC UPD Cmd 10000
> RRC UDP Audio 11000
> RRC Web 5058
> RRC Telnet 5059
> RRC SIP 5088
>
> All port forwards are set the same for both internal and external use, both
> TCP and UDP protocols, LAN address of the RRC.
>
> Is something missing? Any suggestions?
>
> Thanks,
>
> /Rick N6XI
Hi.

That's a lot of open ports.  Not using a VPN then?  (Doesn’t look like
the router itself can be an endpoint though, you'd need some PC or
Raspberry Pi at the remote site for that.)

Anyway.  Find out how to backup and restore the router's configuration
to a file on a PC, and make that backup.  Then the next time you have to
change it (due to lightning strike?)  You can just load the known
working config into the new router, and likely you are ready to go.  
(Page 55 of the user manual.)

Also.  With new out the box routers, check if there is updated firmware
available from the makers.  Often the things come out of the factory
(wherever) with very old/early firmware in, that has known issues. 
Cisco are no exception to that sadly.   (Linksys in disguise!)   Make
sure you get the correct firmware, that product has two versions of
hardware it seems.

I've not checked, but "OpenWRT" or "Tomato" alternative firmware's might
run on that device.  That can often give you "a lot" more functionality,
if you need it, such as VPN endpoints!

Oh, and make sure any UPnP functionality is not exposed to the www.  
grc.com/shieldsup will test that for you...  (If you connect via the new
router.)

73 and Enjoy.

Dave G0WBX.

(I do similar remote shack things using SSH tunnels home from my
travelling laptop, to dedicated Linux boxes in the shack.)