OpenVPN could not be established after upgrade to 23.01 on SG-3100

stephenw10

I have use that and seen no issues since. It does survive a reboot.

fred7911

Ok great, thank you!
I will also follow your bug report status..

bdzero

Same here, kldxref /boot/kernel fixed for me as well. 3100

jsnaza

I also had this issue with a 3100 and the kldxref /boot/kernel command worked for me too.

crogerson

@stephenw10 I ended up having this issue on a 1537. Applied the patch from the redmine post and issue is now resolved.

acardenas

@stephenw10 Is this ran through SSH console? I ran via SSH and ran into the following error: kldxref: can't create /boot/lhint.h6bsDi: Permission denied

stephenw10

You probably need to be logged in as root or admin to run that.

It should work via Diag > Command Prompt in the webgui though.

PeeKay

@stephenw10 worked for me. Thanks for this!
Ran kldxref /boot/kernel in Diagnostics > Command Prompt on 3100 and restarted OpenVPN services. fired up immediately.

jkibbey

The above fix and/or patch worked for me and VPN functionality is working fine with the only perceived exception: when trying to access the pfSense web gui through VPN, it loads some of the page then hangs. From then forward, it seems to corrupt the gui service (PHP?) for any client until the firewall is rebooted (restarting webConfigurator and restarting PHP-FPM did not resolve the issue, reboot was required.) I also tried different browsers, different client machines, and forcing a cache refresh.)

I've tested this through site-to-site as well as remote access through OpenVPN. Everything else through VPN is working fine. Testing included SSH, Remote Desktop, UniFi web gui.

I'm using a Netgate 3100.

tennbaum

@peekay said in OpenVPN could not be established after upgrade to 23.01 on SG-3100:

works for me as well (3100)
kldxref /boot/kernel
all working after (did not check the pfsense gui though)

stephenw10

@jkibbey said in OpenVPN could not be established after upgrade to 23.01 on SG-3100:

From then forward, it seems to corrupt the gui service (PHP?) for any client until the firewall is rebooted

Hmm, that's odd. Do you mean it happens one time after updating the linker hints? Or Whenever you try to access the gui over the VPN even after the reboot?

And does that then also apply to local clients accessing it?

Steve

jkibbey

@stephenw10 It happens anytime I try to access the pfSense gui via the OpenVPN tunnel. All other communication through VPN is fine and the pfSense gui functions like normal if I do not access it via VPN and if I have not attempted to use it via the tunnel after a reboot, even if it was from another client.

stephenw10

Hmm, is it only the webgui, can you ssh to the firewall across the VPN?

JayB

Dealing with similar result (different cause?) this morning on our 2440. Upgraded HO on Saturday and We've no connectivity this morning (first day office is back since upgrade)

Tunnel is stuck on "Adding Routes to System" and the RO (which did not get the upgrade) is showing "reconnecting: ping-restart". The logs show GDG: problem writing to routing socket. Tried the kldxref /boot/kernel fix but to no effect.

Unable to roll back to previous stable (not offered) so we're putting a spare that's on 22.05 online to replace the borked one.

stephenw10

What is it connecting to? The only other report of this was at the other end of a link to a 3100 that had also been updated and required the above fix. But if that was the case here it would still fail after you replaced the local end.

You did not also see logged:

ERROR: FreeBSD route add command failed: external program exited with error status: 1

Which would indicate some sort of route conflict.

Steve

JayB

@stephenw10 Both ends are SG-2440's That said, the RO is running 2.6.0 (we recently restored it and haven't re-upgraded to Plus yet) Maybe it's a 23 <> 2.6 issue? We're also still running peer to peer on a shared key but seems it's still allowed?

We're back on our "spare" 2440 which is on 22.01 and the tunnel is up.

I didn't see any error messages, just the GDG warning.

stephenw10

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

JayB

@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.

stephenw10

Can you show more of the OpenVPN client log showing the failures? Preferable with the logging level raised.

jkibbey

@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.