Hide Forgot
Description of problem: All connections in the post are managed by Network-Manager. This issue may apply to VPN connections other than the OpenVPN type, however I have only tried it with OpenVPN connections When establishing a OpenVPN connection (tun0) over an existing Mobile Broadband Connection (ppp0), Network-Manager does not add a static route to the OpenVPN Gateway Server via the ppp0 interface; thus connectivity to the OpenVPN server is now routed through the VPN (tun0) itself - which results in the VPN not functioning. When establishing a OpenVPN connection (tun0) over an existing WiFi connection, the correct static route to the VPN Gateway Server is automatically added over the WiFI interface - thus the VPN works in this scenario. Version-Release number of selected component (if applicable): How reproducible: This issue exists when establishing an OpenVPN Connection over a Mobile Broadband connection (test case) This issue DOES NOT exist when establishing an OpenVPN connection over a WiFi Connection (test case). In this case the correct static route to the VPN server is automatically added and the VPN works. Steps to Reproduce: 1. Connect to Mobile Broadband (ppp0); ensure not on any other network 2. Connect to VPN (OpenVPN) server 3. Review route table Actual results: No static route to the VPN Gateway Server via the Mobile Broadband interface; thus routing to the VPN connection breaks once the VPN is established. Expected results: Static route to the VPN Gateway Server via the Mobile Broadband (nominally ppp0) interface. This means traffic traffic from the VPN client cannot get to the VPN gateway and the VPN no longer functions. Additional info:
is there any other additional info I can supply to assist with this bug?
Created attachment 1237659 [details] [PATCH] vpn: add device route to VPN gateway if parent has no gateway
SJM, can you please try if the packages in this scratch build resolve your issue: https://koji.fedoraproject.org/koji/taskinfo?taskID=17168764 ? Download the RPMs, run 'rpm -Fvh *.rpm && systemctl restart NetworkManager' and connect again to the VPN.
(In reply to Beniamino Galvani from comment #2) > Created attachment 1237659 [details] > [PATCH] vpn: add device route to VPN gateway if parent has no gateway lgtm
lgtm
(In reply to Beniamino Galvani from comment #3) > SJM, can you please try if the packages in this scratch build resolve your > issue: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=17168764 > > ? > > Download the RPMs, run 'rpm -Fvh *.rpm && systemctl restart NetworkManager' > and connect again to the VPN. LGTM - works as expected. Thank you for your prompt action.
Applied to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=ae5adc9e21c642a198868b519b2a278b0b108ab8 nm-1-4: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-4&id=48db5806f3a99f6cac526fecd6df5a090b53c192 and nm-1-2: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=ff6ef0d696a09f0ebbb5b956c129ce64c3ecae0c
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.