kernel 4.15 breaks xl2tpd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xl2tpd (Debian) |
Fix Released
|
Unknown
|
|||
xl2tpd (Fedora) |
Fix Released
|
High
|
|||
xl2tpd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Billy Olsen | ||
Artful |
Won't Fix
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Billy Olsen |
Bug Description
[Impact]
Kernel 4.15 breaks xl2tpd, please see following upstream issue for more details :
https:/
The following commit/patch fixes the issue:
https:/
As Ubuntu 18.04 (Bionic Beaver) is no longer accepting Debian packages, I'm guessing then that the patch would need to be added and applied to the existing xl2tpd-1.3.10-1 package.
The linux-image kernel package on Ubuntu 18.04 is currently linux-image-
[Test Case]
* apt install network-
* Add new VPN connection via network manager
* establish vpn connection
[Regression Potential]
* For Bionic, there is none. The xl2tpd daemon does not work without the patch on the standard bionic kernel.
* For Xenial w/ the 4.15 HWE kernel there is no risk.
* For Xenial w/ the stock 4.4 kernel there is minimal risk as the code is pulling values that are not valid on the 4.4 kernel by default.
Note that a test pkg (Pre-SRU) has been tested for both Bionic and Xenial by a user affected by this problem and the package has been proven to work as expected on the different supported Ubuntu kernel series (v4.4, v4.13, v4.15).
For more details, please have a look at comment #17 and #23.
Changed in xl2tpd (Debian): | |
status: | Unknown → New |
Changed in xl2tpd (Fedora): | |
importance: | Unknown → High |
status: | Unknown → Fix Committed |
Changed in xl2tpd (Fedora): | |
status: | Fix Committed → Fix Released |
Changed in xl2tpd (Debian): | |
status: | New → Fix Released |
tags: | added: sts sts-sru-needed |
Changed in xl2tpd (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in xl2tpd (Ubuntu Bionic): | |
status: | New → Confirmed |
Changed in xl2tpd (Ubuntu Artful): | |
status: | New → Confirmed |
Changed in xl2tpd (Ubuntu Xenial): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in xl2tpd (Ubuntu Artful): | |
importance: | Undecided → Medium |
Changed in xl2tpd (Ubuntu Bionic): | |
importance: | Undecided → Medium |
description: | updated |
tags: | added: sts-sponsor-slashd |
description: | updated |
Changed in xl2tpd (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
kernels 4.16 release candidates and 4.15 have broken xl2tpd with a ENODEV (No such device) error, see: /github. com/xelerance/ xl2tpd/ issues/ 147
https:/
As mentioned in that github xl2tpd issue, I've submitted a pull request that fixes the bug. It is based on xl2tpd- 1.3.8-saref. patch in Fedora's xl2tpd RPM spec file, except it doesn't attempt to obtain the ancillary IP_PKTINFO data, so does pretty much what xl2tpd running on non-linux operating systems do.
I've requested a new xl2tpd release which has the pull request, but don't know how long it will be for the new release.
It would be great if Fedora 26, 27 and EPEL7 xl2tpd packages are updated to the next new release or have a patch based on the pull request.