You are here

Tunnel Failure AREDN 998 03-10-2022

9 posts / 0 new
Last post
w8erw
w8erw's picture
Tunnel Failure AREDN 998 03-10-2022

After loading the latest nightly release 998, Tunnel connections are no longer active.

I have done this several times previously without a hitch.  This time, the tunnel connections do not light up and Mesh status indicates no active tunnels.
I have reverted to 3.22.1.0.

Thanks,

Jim
W8ERW
 

w8erw
w8erw's picture
Update with 3.22.1.0

After reverting to the stable release 3.22.1.0, tunnels are not working.
I have verified my firewall is not blocking and it appears the original IP addresses for the tunnels have not changed.
At this point, I'm not sure what has gone awry.

Thanks,

Jim
W8ERW
 

K6CCC
K6CCC's picture
Check Network IP

Check to make sure that the Network IP for the tunnels did not change.  When I updated a hAP to 991 yesterday, it blew away all 13 of my tunnels.  When I went to rebuild the ones on the Tunnel Server page, the Network IP setting at the top of the page changed.  Fortunately, I have a spreadsheet with the correct information.  After correcting that, the tunnels came up, however the Tunnel Server page does not indicate active tunnels, but the Mesh Status page shows them working (as does the far end clients that I checked).  The Tunnel Clients Page does correctly show tunnel status.
 

nc8q
nc8q's picture
nightly release 998, Tunnel connections are no longer active.

Hi, Jim/Jim:
 
 I 'survived'.
I removed vtun and rebooted.
It took me at least 4 tries to load 998 over 3.22.1.0.
After the successful load of 998(*), I 'installed 'Tunnel Server' firmware from the GUI/Setup page.
All 12 of my tunnel server settings survived, but only 10 were 'active'.
I edited the 'Advanced Configuration' page, setting/saving clients/servers to 13 each.
(*) The 'successful' load of NB-998 took over 15 minutes to 'recover'.

73, Chuck


 

w8erw
w8erw's picture
Success

Although this is the first time I had any issues with upgrading my nodes, After 5 more tries and many more reboots, upgrading was just now successful.Everything continued to appear normal, just no tunnel connections.  I did nothing any different this last time and it worked.

Thanks for the comments.  They were and are apreciated.

Jim
W8ERW
 

w8erw
w8erw's picture
Tunnel additional

Yes, I did finally get the node to establish tunnels.  However, it only brought up two and left 5 others disconnected. After a bit of digging, I realized the tunnels were all thrashed with different than the original IP settings.  Since I cannot make the appropriate changes in the server node, each one will need to be corrected at the other end.  Not a serious issue, but one of inconvenience and a big wonder why.  To be exact I could delete and re-enter each one under the correct IP address since the range is the same.  And my outlying partners should be able to make the correction individually in their remote nodes.  A good reason to take a screen shot of all your configurations which I had not done recently.  

 

K6CCC
K6CCC's picture
What firmware version are you

What firmware version are you running?There was a recent nightly that messed up the order on both tunnel server and client pages.  That was corrected, and even with the errored version, if you go to the Perl version of the page (add .pl to the end of the url), it will be correct there.

 

w8erw
w8erw's picture
Tunnels

I have loaded the nightly version for 03-12 998.  Thanks for the additional information.
 

K6CCC
K6CCC's picture
I'm not positive if that was

I'm not positive if that was a version affected by the scrambled tunnels issue, but it might be.  Update to the current (which as I type this is 1027).
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer