Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] IPSec VPN: Wrong VPN Types offered with IKEv2 #1961

Closed
somova opened this issue Nov 26, 2017 · 9 comments
Closed

[Bug] IPSec VPN: Wrong VPN Types offered with IKEv2 #1961

somova opened this issue Nov 26, 2017 · 9 comments
Assignees
Labels
feature Adding new functionality
Milestone

Comments

@somova
Copy link

somova commented Nov 26, 2017

In case of setting up a VPN for mobile clients (roadwarrior) the phase1 settings offers wrong authentication methods in conjunction with "IKEv2" as key exchange version.

  • Hybrid RSA + Xauth
  • Mutual RSA + Xauth
  • Mutual PSK + Xauth

If I understand the strongswan documentation correctly [1], "Xauth" is only supported for "IKEv1". I investigated a little bit because it was not possible to get a connection from androids' strongswan client with mode (Mutual RSA + EAP User/Password).

If I manually change the "rightauth2" parameter in the "ipsec.conf" from "xauth" to "eap-mschapv2" the strongswan client on my mobile phone works fine. So I think the authentication methods have to be adapted to IKEv2 (e.g. Mutual RSA + EAP MSCHAPv2, ...) if the latter is selected.

Opnsense version: 17.7.8

[1] https://wiki.strongswan.org/projects/strongswan/wiki/ConnSection

@somova somova changed the title IPSec VPN: Wrong VPN Types offered with IKEv2 [Bug] IPSec VPN: Wrong VPN Types offered with IKEv2 Dec 3, 2017
@somova
Copy link
Author

somova commented Dec 3, 2017

Is anybody here familiar with IPSEC IKEv2 and Strongswan respectively using it?

@sempervictus
Copy link

My testing of the IPSEC functionality in OPNSense shows that its pathologically broken - they can site-to-site with each other, but aren't compatible with mainstream IKE implementations in v1 or v2. We solved this problem in openstack's vpnaas via libreswan, but getting that to build on BSD is apparently a nightmare (i tried). Our solution was to move as much as we could to OpenVPN and use an alternative ipsec terminator when required.

@somova
Copy link
Author

somova commented Jan 7, 2018

Tests with a manually modified ipsec.conf file work well with a Fritzbox as another tunnel endpoint (tunnel mode) and with an android phone using strongswan client (roadwarrior).

The problem is that the web UI does not allow me to properly setup the ipsec configuration

@somova
Copy link
Author

somova commented Jun 26, 2018

Is there anybody who can help to solve this problem? With every update of the opnsense, I have to manually update the configuration. In my opinion the GUI should allow to configure {left|right}auth and {left|reight}auth2 separately.

@AdSchellevis
Copy link
Member

What configuration do you need and for what use-case? IKEv2 + eap-mschapv2 is supported, if I'm not mistaken it's approximately the use-described here https://wiki.strongswan.org/projects/strongswan/wiki/Win7EapMultipleConfig

@somova
Copy link
Author

somova commented Jun 29, 2018

I need mutual RSA + eap-mschapv2. This is not configurable via the GUI

leftauth = pubkey
rightauth = pubkey
rightauth2 = eap-mschapv2

@AdSchellevis
Copy link
Member

@somova can you try 6619147 ?

To install the patch, use:
opnsense-patch 661914

@somova
Copy link
Author

somova commented Jul 3, 2018

@AdSchellevis: Thank you, the patch works great.

@fichtner
Copy link
Member

fichtner commented Jul 3, 2018

Shipping in 18.1.12 then, thanks for testing! ❤️

@fichtner fichtner closed this as completed Jul 3, 2018
@fichtner fichtner added the feature Adding new functionality label Jul 3, 2018
@fichtner fichtner added this to the 18.7 milestone Jul 3, 2018
fichtner pushed a commit that referenced this issue Jul 3, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality
Development

No branches or pull requests

4 participants