Show Posts
16
General discussion forum / New Problem Identified: Tip if RemoteRig Stops Working
« on: 2014-08-05, 12:10:56 »
I resolve a number of RemoteRig problems for users every week, but recently I had two unusual problems in Germany and Spain
that turned out to be a new issue that will likely come-up more and more often. I therefore want to warn the user community
about how to recognize this problem and how to possibly solve it.
The effect of the problem is that a previously perfectly working setup just stops working for no apparent reason. In general,
a working system that stops working is not due to a RRC defect, but due to a change somewhere in the environment (e.g.
router, loose cable, etc.)
This new problem is caused by the migration of internet providers from IPv4 to IPv6. The provider changes the IPv4 connection
to the internet to a new type of "encapsulated" link that shares a single external IP number with its users. This means that the
users no longer have an external IP number on the internet that can be used to reach devices within the users' networks using
port forwards (called "double NAT"). The RRC is therefore all of a sudden no longer reachable and the system goes down.
How to recognize the problem: you need to go into your router and see what IP number the router has received from the provider.
This is under a menu called "status", "WAN" or similar. Then go into your radio RRC's status page (or use a browser to go to
http://www.whatismyip.com/) and see if the external IP numbers match or not. If they do not match, then your provider made this
change. If they do match, your problem is elsewhere in your hardware or network.
How to fix the problem: there is no real fix as such. You need to contact your provider and see if they can give you a true external IP
number as you used to have. If they can not do this or are unwilling to do this, then you will need to change your internet provider.
As an alternative, you can setup a VPN, but this is beyond the scope of this posting.
73,
Mitch DJ0QN / K7DX
that turned out to be a new issue that will likely come-up more and more often. I therefore want to warn the user community
about how to recognize this problem and how to possibly solve it.
The effect of the problem is that a previously perfectly working setup just stops working for no apparent reason. In general,
a working system that stops working is not due to a RRC defect, but due to a change somewhere in the environment (e.g.
router, loose cable, etc.)
This new problem is caused by the migration of internet providers from IPv4 to IPv6. The provider changes the IPv4 connection
to the internet to a new type of "encapsulated" link that shares a single external IP number with its users. This means that the
users no longer have an external IP number on the internet that can be used to reach devices within the users' networks using
port forwards (called "double NAT"). The RRC is therefore all of a sudden no longer reachable and the system goes down.
How to recognize the problem: you need to go into your router and see what IP number the router has received from the provider.
This is under a menu called "status", "WAN" or similar. Then go into your radio RRC's status page (or use a browser to go to
http://www.whatismyip.com/) and see if the external IP numbers match or not. If they do not match, then your provider made this
change. If they do match, your problem is elsewhere in your hardware or network.
How to fix the problem: there is no real fix as such. You need to contact your provider and see if they can give you a true external IP
number as you used to have. If they can not do this or are unwilling to do this, then you will need to change your internet provider.
As an alternative, you can setup a VPN, but this is beyond the scope of this posting.
73,
Mitch DJ0QN / K7DX
