Bug 755300

Summary: NetworkManager's openvpn is not using the custom gateway port I set
Product: [Fedora] Fedora Reporter: Andrig Miller <andrig.t.miller>
Component: NetworkManager-openvpnAssignee: Dan Williams <dcbw>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: choeger, dcbw, huzaifas, steve
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-21 05:50:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screen shot showing that I have indeed set the advanced configuration option for a custom gateway port of 443. none

Description Andrig Miller 2011-11-20 14:05:27 UTC
Created attachment 534658 [details]
Screen shot showing that I have indeed set the advanced configuration option for a custom gateway port of 443.

Description of problem:

Trying to configure OpenVPN through NetworkManager to connect to OpenVPN gateway for work, and it is not using the custom gateway port I configured.  Instead its using the default port of 1194, which the gateway doesn't listen on, so the connection eventually times out.

Version-Release number of selected component (if applicable):

NetworkManager-openvpn-0.9.0-1.fc16.x86_64


How reproducible:

Everytime.

Steps to Reproduce:
1.Configure NetworkManager OpenVPN
2.In the Advanced settings, set the gateway port to a non-default (correct of course), value
3.Try to connect, and you get a timeout.
  
Actual results:

Connection times out.

Expected results:

Should be using the custom gateway port specified in the configuration and successfully connect.

Additional info:

First line of a packet capture which shows that its ignoring the custom gateway port configuration:

Destination port: openvpn (1194)

Comment 1 Andrig Miller 2011-11-21 05:50:12 UTC
Turns out that I was finding the port in the packet capture correctly, and it was using the custom gateway port.

I had the wrong CA file configured, and once I had the correct one, it worked fine.