You are here

Client failure after firmware upgrade

9 posts / 0 new
Last post
KQ6EO
Client failure after firmware upgrade

Had a 3.19.3.0 client with the tunnel working fine.  Deleted the client config, rebooted (it was gone), Upgrade to 3.20.3.1, reinstalled tunnel client, reconfigured client and enabled, and rebooted.  Client does not connect to server anymore.  Server has been at 3.20.3.1 for a long time.

I have reconfigured the client, rebooted the client and the server multiple times.  I can telnet to the server through the internet router on port 5545 and get the tunnel version message.  I can't see anything wrong but the tunnel does not come up.  Need some ideas what to check next.

Client router config attached.

Hope it is just something stupid that I missed.

Tom Preston
KQ6EO

KQ6EO
The tunnel was working right

The tunnel was working right up to the upgrade of the client and I can telnet to the server through the firewall.

k1ky
k1ky's picture
Tunnel Upgrades

You don't need to delete (or disable) tunnel Client/Server tables when upgrading.  Simply remove the VTUN module before upgrading, reboot, upgrade Firmware, Reinstall Tunnel and you should be good to go with all previous settings intact.  

K6CCC
K6CCC's picture
Don't even need to remove the

Don't even need to remove the VTUN module.  You do need to disable tunnels, but the firmware update will delete the tunnel firmware for you (whether you wanted it to or not).
 

k1ky
k1ky's picture
Disable Tunnel(s)

I find it easier to just remove the module.  Less actions if you have multiple Tunnel Clients and Tunnel Server connections.  Too many check boxes to undo and then re-enable!

KQ6EO
That's what I thought but it

That's what I thought but it is not working.
Does anyone know what modules I need to remove to be able to reinstall tunnel client?
Tom

k1ky
k1ky's picture
Remove VTUN module

remove package vtun 3.0.3-2 from admin package management - remove package section.
Then reboot and proceed with firmware upgrade if needed.

KQ6EO
Reload of tunnel client was no help

I deleted the tunnel package vtun and rebooted.  Reloaded tunnel client and reconfigured.  Rebooted.
Tunnel still does not come up.

nc8q
nc8q's picture
Deleted the client config,

I looked at your support data file and found:

Wed Nov 18 12:45:44 2020 daemon.info vtund[2680]: Connecting to aredn-tunnel.sac-aredn.org
Wed Nov 18 12:45:44 2020 daemon.info vtund[2680]: Connection denied by aredn-tunnel.sac-aredn.org

repeated 296 times (with slightly different date-times).

Perhaps you did not re-enter your credentials exactly.
Perhaps aredn-tunnel.sac-arden.org is expecting your previous identification (3.19.3.0).

I hope this helps, Chuck

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer