Bug #9043
closed
openvpn 2.4.3-p1 -> 2.4.4, failed
0%
Description
hi
After the update has stopped working normally openvpn for Pfsense + mikrotik v6.43.2 (Protocol TCP and Device mode tun)
1.Server mode "Remote Access (ssl/tls + User Auth)" Status: link established, but not connected
2.Server mode "Remote Access (User Auth)" Status: link established, but not connected
2.Server mode "Peer to peer (ssl/tls)" Status: connected, but cannot ping access local network (from mikrotik to pf - ok, from pf to mikrotik - problem)
Sorry for my English and thank.
Updated by Jim Pingle about 6 years ago
- Status changed from New to Not a Bug
Not enough info here for a valid bug report.
Please post on the forum at https://forum.netgate.com/ -- There are several international language areas, if there is one for your native language that would be a good place to figure out the details of what happened.
Updated by Rasmus Berg over 5 years ago
Hi,
I'm experiencing the same issues after upgrading pfSense from 2.3.x to 2.4.2 and the problem is still there in 2.4.4.
I'm using Remote Access (SSL/TLS + User Auth), TCP, TUN in combination with Mikrotik. What more information do you need to work on this bug report? Just let me know and I'll supply it.
Updated by Tomáš Bittner over 5 years ago
Hello everyone,
We have the same problems after the upgrade pfSense software from 2.3.x to 2.4.x.
We use Remote Access (SSL/TLS + User Auth),TCP,TAP in combination with Mikrotik.
Today I tested pfSense software 2.4.4-RELEASE-p3 + mikrotik RELEASE 6.45.1 (Stable). Status: link established, but not connected.
The problem is with the "User Auth" method. Remote Access SSL/TLS is functional without "User Auth"
In my opinion, pfsense software 2.3.x was an openvpn version of the 2.3x series.
The pfsense software 2.4.x is a 2.4x openvpn version.
Mikrotik probably has a problem with the openvpn 2.4x series.
Mikrotik manufactures its own OVPN client.
Do you think the problem is in pfSense software or in mikrotik OS?
Updated by Jim Pingle over 5 years ago
There is no pfSense bug here. Either it's a Mikrotik issue or a config issue. Post on the forum for assistance.
Updated by Rasmus Berg over 5 years ago
I ended up moving over to OPNSense, which works flawlessly with Mikrotik. They're using an OpenVPN version which is one minor version newer than PFSense's ditto. Don't remember the full version number though.
Updated by Tomáš Bittner over 5 years ago
Thanks for the information, I will try out with OS debian stable, version 2.4.x openvpn.
pfSense software 2.4.4-RELEASE-p3
pkg search openvpn
openvpn-2.4.6_1
I'll see if the mikrotik works.
Then it will be clear where the mistake is.