You are here

Changing Node Name doesn't affect Tunnel Client Name

3 posts / 0 new
Last post
n5hzr
n5hzr's picture
Changing Node Name doesn't affect Tunnel Client Name

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?

KD1HA
KD1HA's picture
It should clear in 24 Hrs.

It should clear in 24 Hrs.

n5hzr
n5hzr's picture
So...

So, after 24 hours the client machine will change the client tunnel name to the new node name. The tunnel will 'break', and then I'll have to update the tunnel server with the new client name?
Kind of odd, but I guess I can live with that.
Thanks!

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer