RRC 1258 Support in English > Configuration, RRC 1258

Could you please support the noip.com free DDNS?

(1/3) > >>

W7KWS:
Hello Mikael,

I am hoping that you will consider supporting other DDNS services such as noip.com which is still a free ddns service for up to five non-commercial host names.  I realize that you are providing free DDNS service for RemoteRig in addition to supporting DynDNS but it would be helpful to include support for other DDNS services that we use for our general systems.  If the RemoteRig did this it would backup the DDNS client on my computer in case of its failure.

Since my computer crashed, I've lost access to my station.  The RemoteRig still works but I now cannot rotate my beam or switch antennas.  If the RemoteRig was updating the free noip.com I would still have access to these systems which are run separetly from the RemoteRig.

I will look forward to your thoughts on this.  If you need the noip.com settings, the developer is very helpful or I can forward them to you.

Thank you,

Bob, W7KWS

dj0qn:
Bob,

Although it may make sense for RemoteRig to support other free services such as noip.com, your statement
is not really logical.

It is completely irrelevant which service you use to reach your network, because you have only one single external
IP number. If you had 10 devices, only one of them needs to have some sort of dynamic DNS service to be able to
reach your entire network. Indeed, using the RemoteRig built-in service allows a fall-back to reach your network if
the other service can not be used.

If you still have access to your station using RemoteRig's system, just copy and paste that IP address (called SIP
contact in your control RCC) into the other devices or browser and use the correct ports. Then you will be able to
reach your beam and switch. You will find that having this actually allows you a fall-back and will make things easier
for you. Just try it now and you will see that this solves your problem.

73,
Mitch DJ0QN / K7DX

W7KWS:
Mitch,

Thank you for your suggestion but, unfortunately, my IP address at the far end changes several times a day.  What you suggest is great for a work around but is inconvenient and time consuming to enter the new IP address into all of the clients I have here every time the distant end changes.  In addition to my rotor, Steppir and antenna switch, I have things such as my VOIP telephone OPX line, IP Camera, Etc., none of which have the ability to update DDNS.  There are just too many clients to be updated manually so often.

On the other hand, you have inspired me.  Instead of doing what I suggested, I could reverse my thinking and put a RemoteRig DDNS host name into all of the clients here where I am located.  They should resolve just fine but if the RemoteRig failed I might find myself in the same fix without any backup.  Also, this would add unanticipated traffic for the RemoteRig DDNS servers.  My little bit of traffic might not be a problem but if many others decided to do this, it might not be appreciated.  I have a feeling that multiple devices for updating the DDNS server, whichever one I end up using, will be more reliable.

Any thoughts on this?

Thank you,

Bob, W7KWS

dj0qn:
Bob,

That's what I meant: just use the RemoteRig dynamic DNS address instead. You however still didn't
understand the concept of the multiple devices in that network not needing to update the server. It
is only necessary for one, single device to update the server when the external IP number changes.
Having multiple devices update using the same dynamic DNS server makes no sense, and anyway the
server used by RemoteRig would only allow that authorized device to make the update.

The call-ups generated by your control point is the only traffic generated, and that is only for DNS lookups.
There should be no problem just putting the address used by RemoteRig as the target address, and this
would work every bit as good or better than using noip.

73,
Mitch DJ0QN / K7DX

W7KWS:
Dear Mitch,

Thanks for the quick feedback.  I must not be describing my main concern to you very well.  In addition to that concern, I'm shy about adding traffic to the RemoteRig servers that is unrelated to RemotRig.

My main concern is for a backup to update the radio location's IP address.  In your scenario, if there is any failure in the RemoteRig or in its path out to the Internet from my LAN, I'll find myself in the same situation I'm in right now with no updates.  It would be better if I could use my RemoteRig to update noip.com in addition to my computer doing so, once it's back up and working.  This way, one of the two could fail and the other would remain available to update noip.com.  There is no way for this kind of redundancy if I rely solely on the RemoteRig’s servers and the RemoteRig radio for doing updates since there is no other device, that I'm aware of, that will act as a backup and update the RemoteRig DDNS server if the RemoteRig Radio should have a problem doing updates.

Thanks & 73,

Bob, W7KWS

Navigation

[0] Message Index

[#] Next page