| Summary: | Can't connect to openvpn | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Elad Alfassa <elad> |
| Component: | NetworkManager-openvpn | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | brian, choeger, dcbw, huzaifas, loganjerry, steve, thaller |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-29 13:23:00 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: | |
|
Description
Elad Alfassa
2013-12-03 14:19:55 UTC
I also cannot connect, and the log looks similar; i.e., it reports "add_Object(): Netlink error: Invalid input data or parameter", and then we're toast. The same configuration worked before I upgraded this system from F-19 to F-20. Also, I can run openvpn from the command line and connect successfully. I'm happy to collect more information if someone will tell me how to do so. I, too, am having this problem - with just one of my two OpenVPN connections. They're both to different pfSense OpenVPN endpoints. I get the following output when I use the commandline openvpn client on the "bad" connection: $ sudo openvpn --config cmapfsense-udp-1194-brian.ovpn [truncated] Thu Jan 23 11:41:38 2014 /usr/sbin/ip link set dev tun0 up mtu 1500 Thu Jan 23 11:41:38 2014 /usr/sbin/ip addr add dev tun0 local 10.100.6.38 peer 10.100.6.37 RTNETLINK answers: Invalid argument Thu Jan 23 11:41:38 2014 ERROR: Linux route add command failed: external program exited with error status: 2 Thu Jan 23 11:41:38 2014 Initialization Sequence Completed However, the client stays operational. This seems to suggest that the underlying problem exists in both cases, but that NetworkManager detects the error and bails out, while the CLI client ignores it and continues on, and the tunnel appears to be functional. Ignore Comment #2; I'd had a misconfiguration on the server end. ("push route x.x.x.129 255.255.255.224" -- oops, should be .128) This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |