You are here

Home » Forums » Tunnels

23.4.0 Upgrade lost VPNs

13 posts / 0 new
Log in or register to post comments
Last post
Fri, 04/21/2023 - 12:18
#1
AK7F
23.4.0 Upgrade lost VPNs
I have 3x 750 Creta nones. One is the Hub for my Home Mesh Networks, the second is a node I carry with my Laptop. The third is from a local mountain top.

I have upgraded all 3 from 22.12.0 to 23.4.0 and the VPN connections no longer work. The VPN was working with port forwarding from the outside world. To eliminate the firewall, I placed both on the internal network an used the IPs direct. Even with the nodes on the same network, the VPN connections still do not go active.

As I am new to AREDN, I have not enabled ssh, and flying a bit blind. Any help would be great.

Thanks,

Brian, AK7F
Top
Sat, 04/22/2023 - 19:08
wb4bsd
the update killed my gl-inet
the update killed my gl-inet devices. :(
Top
Sun, 04/23/2023 - 06:40
(Reply to #2)
nc8q
nc8q's picture
Upgraded GL iNet devices to 3.23.4.0

I have upgraded these GL iNet devices from a nightly build to 3.23.4.0 without changing any settings:
AR750-creta: functions as my home AREDN network router with 9 port forwards
USB150: Primary away-from-home link-to-home-AREDN via Wi-Fi internet
AR150: Backup away-from-home link-to-home-AREDN via Wi-Fi internet
AR300: Adds Wi-Fi connectivity to a remote IP phone

Also upgraded to 3.23.4.0 without changing any settings:
Mikrotik RB952-Ui (hAP) with 9 active tunnel clients

73, Chuck

 

Top
Sun, 04/23/2023 - 11:02
(Reply to #3)
wb4bsd
I got mine nodes working, but
I got mine nodes working, but my tunnel vpns are not reconnecting at all.
Top
Sun, 04/23/2023 - 12:09
(Reply to #4)
K6CCC
K6CCC's picture
Tunnel client or server?
Are you the tunnel server or the tunnel client?  Please give details (we're not mind readers).
 
Top
Sun, 04/23/2023 - 15:35
(Reply to #5)
wb4bsd
Oh snap. I thought y'all were
Oh snap. I thought y'all were mind readers. 

I have both a tunnel server and I'm also a tunnel client. None of them are connecting. 

My microtik isn't connecting (client of server) either. 

my gl-iNet won't even receive a dhcp address from my network. It was working perfectly before the upgrade. 

so, something broke during the upgrade. 

 
Top
Mon, 04/24/2023 - 00:42
(Reply to #6)
KM4TBQ
KM4TBQ's picture
The update took four of our
The update took four of our mikrotik LDFs out immediately, and has caused numerous issues for every single node (various brands/models) we updated. This is setting us back monumentally due to the scale of the project. 
Top
Sun, 04/23/2023 - 18:26
n5hzr
n5hzr's picture
Me too

Earlier today I upgraded my GL i.Net AR 150 router to 3.23.4.0.
I have about eight tunnel servers set up and none of them have connected.
This box should have almost 70 devices connected to it.
I've attached the SupportData file.
Thoughts????

Image Attachments: 
Support File Attachments: 
File support data renamed from gz to tgz to upload
Top
Sun, 04/23/2023 - 18:44
(Reply to #8)
K6CCC
K6CCC's picture
Are you saying that you are
Are you saying that you are the tunnel server or the client?  If the server end, did your WAN address change?  If so, you would need to edit the port forarding in your router so that it points to the new address.
 
Top
Mon, 04/24/2023 - 00:53
(Reply to #9)
AJ6GZ
WAN
That is possible. I had one local user who's WAN port refused to get a DHCP address until multiple reboots and coaxing. One theory is its MAC address may have changed, which could cause a different IP to be handed out. In this case though, a custom (non 1) VLAN tag on the WAN port was in use. Changing it, and then changing it back fixed it. (This may have had the effect of clearing out an ARP cache/MAC table) No problems here on hAP, two Nanostations, and a Powerbeam.
Top
Mon, 04/24/2023 - 08:11
(Reply to #10)
n5hzr
n5hzr's picture
Thanks --
Thanks for pointing me to the WAN IP... -- Mark
Top
Mon, 04/24/2023 - 08:06
n5hzr
n5hzr's picture
Solved... WAN IP changed
Greetings, I have solved my issue.
My WAN IP address changed on the AREDN tunnel server machine from .54 to .56. 
A static DHCP server sets this address on the edge router.
I changed the port 5525 tunnel port forward to this new .56 address, and the system came to life.
My guess is that the WAN MAC must have changed during the update and the DHCP system assigned a new address to the new MAC.
Top
Tue, 04/25/2023 - 02:35
(Reply to #12)
KM4TBQ
KM4TBQ's picture
Glad your problem was solved.
Glad your problem was solved.
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer