OpenVPN could not be established after upgrade to 23.01 on SG-3100
-
Shared key will still work in 23.01. It likely won't work in future versions when OpenVPN stops supporting it upstream.
Was there anything logged at the other end?
I would try turning up the logging level in OpenVPN and retesting of you can.Steve
-
@stephenw10 re: shared key...that's what I understaood but worth mentioning.
The remote log shows no errors or warnings.
Looks normal except there's no Peer Connection Initiated with [AF_INET]XXX.XXX.XXX.XXX:1194 at the top of the log.
-
Can you show more of the OpenVPN client log showing the failures? Preferable with the logging level raised.
-
K KpuCko referenced this topic on
-
@stephenw10 Yes, when this happens I can still SSH to it using putty. This is how I've been restarting it and how I was able to try restarting the web configurator, etc. Other VPN traffic works fine as well ie: web gui for unifi.
-
Ok, well we need more info here to try to reproduce the issue really. Any additional error logs you might be able to get. Anything unusual in your config.
-
@stephenw10 said in OpenVPN could not be established after upgrade to 23.01 on SG-3100:
kldxref /boot/kernel
Finally! This fixed both OpenVPN and Tailscale. Thank you so much for posting this. SG-3100 here.
-
@stephenw10 I just reproduced it on a completely different 3100 at a different location. I have nothing special going on regarding configuration. All I did to reproduce it is connect to openvpn from a windows 10 machine running the openvpn connect client. I visited the pfsense web gui and logged in. I held shift while clicking refresh. 3/4 of the page loaded then it froze completely. Dropdowns stopped working and broken images. I disconnected VPN and reconnected hard wire and still could not get the web gui to properly respond. I rebooted the 3100 and everything is back in order. I can get to the web gui like normal. I can get you whatever logs or configs you'd like.
-
Hmm, do you see anything logged when that happens? Nothing logged as blocked in the firewall log?
The only vaguely related thing I'm aware of here is this: https://redmine.pfsense.org/issues/13938
Obviously there's no kernel panic here but you are still accessing nginx via a virtual interface. You might try disabling unmapped mbufs as shown there to see if it makes any difference.Steve
-
@stephenw10 I didn't see anything logged in system/gui or firewall pointing to an issue. Disabling sendfile on one of them seems to have solved the problem. Doing that and kern.ipc.mb_use_ext_pgs=0 on the other seems to have solved the crashing and need for a reboot, though it doesn't resolve the gui loading through vpn issue.
-
Hmm, that's interesting. I would only have expected to need those workarounds at the remote side of the tunnel.
So with those in place you are still unable to access the webgui on the remote pfSense over the VPN? But doing so no longer prevents clients local to it accessing it after that?
-
@stephenw10 In both test cases they were remote side. I tested each with multiple clients and connections. One 3100 issue was resolved. The other didn't completely resolve with either of the two fixes I mentioned. It continues to fail to load the web gui when accessed through the tunnel but it no longer prevents local access to it prior to a reboot.
-
@techscribe said in OpenVPN could not be established after upgrade to 23.01 on SG-3100:
Tail
Hey @techscribe Did you have to do anything extra to get Tailscale to work? My Tailscale didn't return after entering
kldxref /boot/kernelinto the command prompt. Any insight would be appreciated, thank you! -
W wavesound referenced this topic on
-
having the same issue after 23.01 on a custom build tried the fix did not work, removed my defined network from "IPv4 Tunnel Network" openvpn connects again.
-
@mmrk All I did was run the command, then restarted both my OpenVPN and Tailscale services.
-
@sphillips said in OpenVPN could not be established after upgrade to 23.01 on SG-3100:
removed my defined network from "IPv4 Tunnel Network" openvpn connects again
That sounds more like a subnet conflict. Perhaps something else changed coincidentally with the upgrade? Or possibly simply making any change and resaving the OpenVPN settings re-created the conf file. I would have expected to see errors logged in either of those cases though.
Steve
-
@stephenw10 said in OpenVPN could not be established after upgrade to 23.01 on SG-3100:
That sounds more like a subnet conflict. Perhaps something else changed coincidentally with the upgrade? Or possibly simply making any change and resaving the OpenVPN settings re-created the conf file. I would have expected to see errors logged in either of those cases though.
SteveI did not see any other errors besides the "Exiting due to fatal error", i dont recall making any changes between the upgrade and noticing the issue, i confess it took e a few days to notice the issue since i dont use vpn everyday.
i just got frusted with the problem and went back to pfsense CE will revisit pfsense plus when theres an update or time allows, thank you. -
Ok, probably some other issue then. Unfortunately "Exiting due to fatal error" isn't particularly helpful in the default OpenVPN output. We'll probably need to turn up the logging level if nothing else is shown.
-
@stephenw10 Thank you, this simple fix also did it for me!
-
@stephenw10 This worked for me, as well! Thanks!
-
@stephenw10 Just adding for the web record that I also encountered this issue when upgrading my 3100 this morning. The manual update to the linker file followed by a reboot of the Firewall fixed it.
I obviously have no data on how pervasive this issue is, but like with the 1100 and 2100 maybe it's worth pulling the 23.01 upgrade for the time being on the 3100? Yes I fixed it by going to Netgate forums and see this is one of the top OpenVPN threads but there's lots of folks with these appliances out there that are going to be pulling their hair out over this especially when the interfaces are still in place. Just seems like a big headache for them waiting to happen. Doubly so if they're at remote sites. Either way, the fix was simple! Seems like this should be petted manually and reintroduced as a new release for the 3100 to cover this bug.
