Bug 1214643
Summary: | pptp VPN Connection stops working after update | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Glenn L. Jenkins <glenn.l.jenkins908> |
Component: | NetworkManager-pptp | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | abuse, dcbw, jklimes, k_a_r_l_o_, lrintel, psimerda |
Target Milestone: | --- | Flags: | mleitner:
needinfo-
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-05-01 16:44:31 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Glenn L. Jenkins
2015-04-23 09:48:37 UTC
There has been an change in kernel and pptp now requires nf_conntrack_pptp module to be loaded. # sudo modprobe nf_conntrack_pptp There are more information in bug 1187328. However, I am considering the option that NM-pptp plugin would load the module automatically. Pushed upstream branch jk/pptp-nf_conntrack_pptp (network-manager-pptp plugin) with the change (loading the module). Confirmed this is the cause of my issue. After loading the module, removing my firewall rule and restarting the VPN now works. Many thanks for your prompt response. (In reply to Jirka Klimes from comment #2) > Pushed upstream branch jk/pptp-nf_conntrack_pptp (network-manager-pptp > plugin) with the change (loading the module). Looks good to me. The patch was pushed to network-manager-pptp master upstream: 695d4f2 service: try to load nf_conntrack_pptp kernel module (rh #1214643) NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc22 Can this patch please be made available to F20 and F21 too? Thanks, Bas. I can confirm that the F22 build I grabbed from koji works fine for me in F21. The two packages upgraded without complaints. When starting the VPN in NM, the module got loaded and the VPN was setup properly. Sorry for the noise. One question can up: is there a reason why the nf_conntrack_pptp kmod is not unloaded after the VPN is stopped? One can check for it not being used and then unload it. NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21 Seems fine on FC21, karma added. Package NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7100/NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc22 then log in and leave karma (feedback). Could someone create a version for F20, I'd have a look myself but I don't really know where to start. Thanks, Glenn Get the file https://kojipkgs.fedoraproject.org//packages/NetworkManager-pptp/1.1.0/1.20150428git695d4f2.fc21/src/NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21.src.rpm and rebuild it for yourself: As normal user (not root!) perform the following steps: $ sudo yum install yum-utils rpmbuild $ cd ~/Downloads # for example $ wget https://kojipkgs.fedoraproject.org//packages/NetworkManager-pptp/1.1.0/1.20150428git695d4f2.fc21/src/NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21.src.rpm $ sudo yum-builddep NetworkManager-pptp $ rpmbuild --rebuild NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21.src.rpm $ sudo rpm -Uhv ~/rpmbuild/RPMS/*/NetworkManager-pptp-gnome-1.1.0-1.20150428git695d4f2.fc21.*.rpm ~/rpmbuild/RPMS/*/NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21.*.rpm Note that strictly speaking, the yum-builddep utility will install the build deps from the latest version of the package in the repository. Usually, that is sufficient to build the package you got from an unreleased build. Otherwise, you have to manually install the build dependencies manually. Notice that build dependencies are different from the dependencies to install the package. Hope this helps. The update works for Fedora 20 as well. You have to update some more packages to succeed. First of all You have to build following packages: libnl3-3.2.25-5.fc21 http://koji.fedoraproject.org/koji/buildinfo?buildID=598009 NetworkManager-0.9.10.2-2.fc21 http://koji.fedoraproject.org/koji/buildinfo?buildID=620708 network-manager-applet-0.9.10.2-1.fc21 http://koji.fedoraproject.org/koji/buildinfo?buildID=617947 And at last: NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21 http://koji.fedoraproject.org/koji/buildinfo?buildID=631407 The updates for Fedora 20 repository will be welcomed!!! I have put-up for myself a repository. It's a bit messy, but you can find binaries in http://priede.bf.lu.lv/ftp/Linux/Fedora/repo/20/i386/os/packages/ http://priede.bf.lu.lv/ftp/Linux/Fedora/repo/20/x86_64/os/packages/ or use http://priede.bf.lu.lv/ftp/Linux/Fedora/bf.lu.lv-repository-1.0-K01.noarch.rpm Well done Zirneklitis! I worked my way back to NetworkManager last night, but didn't have time to go any further. I'll have another go this evening and report back, I'd like to go through this for myself so I can help out in the future. NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. NetworkManager-pptp-1.1.0-1.20150428git695d4f2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |