Bug 1366832 - we require IKEv1 peer to have ID '@ip.addr' , but peer declares 'ip.addr'
Summary: we require IKEv1 peer to have ID '@ip.addr' , but peer declares 'ip.addr'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-l2tp
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Douglas Kosovic
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-13 09:08 UTC by dearfriend
Modified: 2016-11-28 07:25 UTC (History)
4 users (show)

Fixed In Version: NetworkManager-l2tp-1.2.4-1.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-28 07:25:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dearfriend 2016-08-13 09:08:27 UTC
Description of problem:

When vpn server reports ipsec-gateway-id different from 'vpn address', I set it manually in "ipsec settings" -> "gateway id"
But connection still failed.

Journalctl -xe reports, that NetworkManage-l2tp insert "@" before 'ipaddr'.

Comment 1 Douglas Kosovic 2016-08-13 12:25:11 UTC
The "@" before 'ipaddr' issue is fixed upstream in this commit :

https://github.com/nm-l2tp/network-manager-l2tp/commit/ed15e04278c2053abef0041e9947a0dcf7424209

and will be made available with NetworkManager-l2tp 1.2.4

Does is not work if you leave the Gateway ID field blank in the IPsec configuration dialog box? Most people are able to getaway with not filling in that field.

Comment 2 dearfriend 2016-08-13 13:48:23 UTC
When Gateway ID field blank connection failed with 
"we require IKEv1 peer to have ID 'ip.addr1' , but peer declares 'ip.addr2'"
where ip.addr1 is vpn server address (from dns), ip.addr2 - reported gw id

Now I am using ip.addr2 as a vpn address, so I can wait 1.2.4 in testing repo.
thx

Comment 3 Douglas Kosovic 2016-09-17 11:31:51 UTC
There are ongoing issues with the newer version and then I went on long service leave which prevent me working on the code.

I'll try and do an interim RPM with a back ported patch which I'll work on in the next couple of days.

The new version of NetworkManager-l2tp is still some way away as I keep discovering issues and bugs.

Comment 4 Douglas Kosovic 2016-09-20 14:04:11 UTC
I've created a git snapshot RPMs of the upcoming NetworkManager-l2tp 1.2.4 :

https://copr.fedorainfracloud.org/coprs/dkosovic/nm-l2tp/

alternatively if want to manually install the two RPMs (i.e. NM-l2tp and NM-l2tp-gnome), find them here:
https://copr-be.cloud.fedoraproject.org/results/dkosovic/nm-l2tp/fedora-24-x86_64/00455380-NetworkManager-l2tp/

The git snapshot version is usable and fixes many issues compared to version 1.2.2.

I still have a few bug fixes that exist in all current versions related to when some wrong IPsec arguments are supplied in the GUI resulting in the ipsec start command not finishing. Once I've updated the code, I'll release 1.2.4 proper.

Comment 5 Fedora Update System 2016-11-20 11:08:18 UTC
NetworkManager-l2tp-1.2.4-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-863a28c489

Comment 6 Fedora Update System 2016-11-20 19:53:17 UTC
NetworkManager-l2tp-1.2.4-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-863a28c489

Comment 7 Fedora Update System 2016-11-28 07:25:10 UTC
NetworkManager-l2tp-1.2.4-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.