I've been bitten by this three times and I finally found a pattern.
I've got an Airrouter set up with node name FRED and it's connected to a Tunnel server at 1.2.3.4 with client name FRED, password SECRET, and net 172.15.15.15. (As an example.) And, it works just fine.
I want to change the node name to BILL. If I make the change in the node name on the Basic Setup page, save the change and reboot the Airrouter, As expected, after reboot, the new node name is displayed and DNS picks up the new node name and responds appropriately. HOWEVER, what is unexpected, is that the tunnel client still connects properly to the server with the 'old' node name of FRED. If I change the client name on the Tunnel server to match the new node name of BILL, the tunnel does not connect...
Shouldn't changing the node name change the client name in the tunnel section?
Is there a way to change the client name from the GUI?
Is this a bug, or a feature?
Is there a way to fix this without loading new firmware and unticking the 'Keep settings' box?
I've got an Airrouter set up with node name FRED and it's connected to a Tunnel server at 1.2.3.4 with client name FRED, password SECRET, and net 172.15.15.15. (As an example.) And, it works just fine.
I want to change the node name to BILL. If I make the change in the node name on the Basic Setup page, save the change and reboot the Airrouter, As expected, after reboot, the new node name is displayed and DNS picks up the new node name and responds appropriately. HOWEVER, what is unexpected, is that the tunnel client still connects properly to the server with the 'old' node name of FRED. If I change the client name on the Tunnel server to match the new node name of BILL, the tunnel does not connect...
Shouldn't changing the node name change the client name in the tunnel section?
Is there a way to change the client name from the GUI?
Is this a bug, or a feature?
Is there a way to fix this without loading new firmware and unticking the 'Keep settings' box?
Kind of odd, but I guess I can live with that.
Thanks!
I factory reset the router and started over.
Note to self, watch for typos and make no changes...
We have been running this configuration where the Airrouter is named BILL, but the tunnel client name has to be FRED (the old name) to make the router tunnel client connect. All was well.
We just installed firmware 3.22.8.0 on the Airrouter in question and it would not connect to the tunnel server. When we changed the name on the SERVER to BILL (the new name), the client connected straight away.
So, 3.22.8.0 must have fixed my 'name change' problem.
Thanks...