FS#58599 - [strongswan] IKEv2 VPN random DNS server

Attached to Project: Community Packages
Opened by Yegorius (Yegorius) - Monday, 14 May 2018, 20:58 GMT
Last edited by Christian Rebischke (Shibumi) - Sunday, 19 August 2018, 02:16 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Christian Rebischke (Shibumi)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Upon connecting to a IKEv2 VPN gateway, charon-nm fails to parse the provided DNS addresses correctly and fills in random garbage. As a result, no server names in the private network can be resolved.
This is a known problem and it is fixed by a specific patch in the git master branch.
This patch should fix the problem https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=ee8c2551

Additional info:
* package version: 5.6.2-1

Steps to reproduce:
1) Connect to IKEv2 VPN from NetworkManager
2) cat /etc/resolv.conf
This task depends upon

Closed by  Christian Rebischke (Shibumi)
Sunday, 19 August 2018, 02:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with 5.6.3-1
Comment by Christian Rebischke (Shibumi) - Wednesday, 18 July 2018, 23:00 GMT
does this bug still exist with strongswan 5.6.3-1?
Comment by Yegorius (Yegorius) - Monday, 30 July 2018, 12:21 GMT
According to strongswan changelog, this issue should have been fixed in 5.6.3

https://wiki.strongswan.org/versions/69
=> Fixed an issue with DNS servers passed to NetworkManager in charon-nm (ee8c25516a)

Loading...