Bug 1413705 - Routes pushed by the openvpn server are not set
Summary: Routes pushed by the openvpn server are not set
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-openvpn
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-16 17:35 UTC by Aurelien Bompard
Modified: 2017-01-17 09:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 09:12:29 UTC
Type: Bug


Attachments (Terms of Use)
Journal (10.54 KB, text/plain)
2017-01-16 17:36 UTC, Aurelien Bompard
no flags Details
Routes after connecting to the VPN (574 bytes, text/plain)
2017-01-16 17:37 UTC, Aurelien Bompard
no flags Details
NetworkManager VPN config (867 bytes, text/plain)
2017-01-16 17:37 UTC, Aurelien Bompard
no flags Details

Description Aurelien Bompard 2017-01-16 17:35:58 UTC
Description of problem:
When I connect to my OpenVPN server, the specific routes that are pushed by the server are not set on the client.
I'm attaching an extract of the client's journal which shows that routes to 192.168.27.64/27 and 192.168.0.0/24 are received by the vpn client, and the output of the "route -n" command which show that these routes are not set.

I'm also attaching the VPN configuration as found in /etc/NetworkManager/system-connections/ (without the password of course) to help troubleshoot this.

Version-Release number of selected component (if applicable):
NetworkManager-openvpn-1.2.6-1.fc25.x86_64

How reproducible:
always

Expected results:
The routes to the 192.168.27.64/27 and 192.168.0.0/24 networks are set. If I set them manually using "ip route", I can reach those networks.

Additional info:
I can reproduce this every time, so feel free to ask me for more info.
However, I can't send you the server OpenVPN configuration, as it's in an Internet appliance I have no control over.

Comment 1 Aurelien Bompard 2017-01-16 17:36:37 UTC
Created attachment 1241353 [details]
Journal

Comment 2 Aurelien Bompard 2017-01-16 17:37:13 UTC
Created attachment 1241354 [details]
Routes after connecting to the VPN

Comment 3 Aurelien Bompard 2017-01-16 17:37:54 UTC
Created attachment 1241355 [details]
NetworkManager VPN config

Comment 4 Beniamino Galvani 2017-01-17 08:01:12 UTC
Can you please run 'nmcli general logging level trace', connect to the VPN and then attach the journal log?

Comment 5 Aurelien Bompard 2017-01-17 09:12:29 UTC
For some reason, today it worked. I collected the data last week, maybe there was an update in the stack in-between (kernel maybe?).
I'll reopen if it happens again, thanks for your reply.


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