Bug 469806

Summary: pushed openvpn configuration segfaults NetworkManager
Product: [Fedora] Fedora Reporter: gdelx001
Component: NetworkManager-openvpnAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: 9CC: choeger, dcbw, steve, tim
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-14 14:06:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description gdelx001 2008-11-04 05:13:36 UTC 
Description of problem:
Using with OpenVPN server configured to push IP address ends up segfaulting NetworkManager.  Suggests mismatch in protocol in "helper" to service nm-openvpn or from nm-openvpn to NetworkManager...

client config as it appears on server side:
ifconfig-push 192.168.0.4 255.255.255.0



Version-Release number of selected component (if applicable):
NetworkManager-openvpn-0.7.0-16.svn4027.fc9.i386
NetworkManager-0.7.0-0.11.snv4022.4.fc9.i386

How reproducible:
Always


stacktrace on OpenVPN client:
localhost nm-openvpn[8613]: /usr/libexec/nm-openvpn-service-openvpn-helper "tap0"  1500 1574 192.168.0.4 255.255.255.0 init
localhost NetworkManager: <info> VPN connection 'localnet-vpn' (IP Config Get) reply received.
localhost NetworkManager: nm_vpn_connection_ip4_config_get: invalid IP4 config received!
localhost NetworkManager: <WARN>  nm_signal_handler(): Caught signal 11.  Generating backtrace...
localhost nm-openvpn[8613]: Initialization Sequence Completed
localhost NetworkManager: ******************* START **********************************
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: [Thread debugging using libthread_db enabled]
localhost NetworkManager: [New Thread 0xb806e700 (LWP 2004)]
localhost NetworkManager: [New Thread 0xb806db90 (LWP 3283)]
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: (no debugging symbols found)
localhost NetworkManager: #0 0x00110416 in __kernel_vsyscall ()
localhost NetworkManager: #1 0x007f9b7b in waitpid () from /lib/libpthread.so.0
localhost NetworkManager: #2 0x0806eb83 in nm_logging_backtrace ()
localhost NetworkManager: #3 0x0806aa75 in ?? ()
localhost NetworkManager: #4 <signal handler called>
localhost NetworkManager: #5 0x08083f97 in ?? ()
localhost NetworkManager: #6 0x002abf0c in g_cclosure_marshal_VOID_BOXED ()
localhost NetworkManager:   from /lib/libgobject-2.0.so.0
localhost NetworkManager: #7 0x0049a33f in ?? () from /usr/lib/libdbus-glib-1.so.2
localhost NetworkManager: #8 0x0029f11b in g_closure_invoke () from /lib/libgobject-2.0.so.0
localhost NetworkManager: #9 0x002b3985 in ?? () from /lib/libgobject-2.0.so.0
localhost NetworkManager: #10 0x002b4ebe in g_signal_emit_valist () from /lib/libgobject-2.0.so.0
localhost NetworkManager: #11 0x002b5326 in g_signal_emit () from /lib/libgobject-2.0.so.0
localhost NetworkManager: #12 0x0049b597 in ?? () from /usr/lib/libdbus-glib-1.so.2
localhost NetworkManager: #13 0x00446175 in dbus_connection_dispatch () from /lib/libdbus-1.so.3
localhost NetworkManager: #14 0x0049204d in ?? from /isr/lib/libdbus-glib-1.so.2
localhost NetworkManager: #15 0x001e9008 in g_main_context_dispatch (0 from /liblibglib-2.0.so.0
localhost NetworkManager: #16 0x001ec6b3 in ?? () from /lib/libglib-2.0.so.0
localhost NetworkManager: #17 0x001ecbd2 in g_main_loop_run () from /lib/libglib-2.0.so.0
localhost NetworkManager: #18 0x0806b1e3 in main ()
.
.
.
Comment 1 Bug Zapper 2009-06-10 03:10:13 UTC 
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 WONTFIX if it remains open with a Fedora 
'version' of '9'.

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 prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Bug Zapper 2009-07-14 14:06:24 UTC 
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

Thank you for reporting this bug and we are sorry it could not be fixed.