Hide Forgot
+++ This bug was initially created as a clone of Bug #641068 +++ Description of problem: When using NM-vpnc (and NM-openvpn, but it is not that much relevant there, because it is more stable) I can see when the VPN connection is down (because of failed 23 hours rekeying or something), because then NM icon in the status bar looses the padlock icon. Unfortunately, when using NM-openswan the padlock icon is still there even though ping <server inside of VPN> doesn't give any response. If nothing else is possible, couldn't NM-openswan ping some computer inside of VPN to check the connection is actually up? Version-Release number of selected component (if applicable): NetworkManager-openswan-0.8.0-5.20100411git.fc14.x86_64 How reproducible: 100% Steps to Reproduce: 1.make VPN connection with NM-openswan 2.wait 3. Actual results: When the connection falls down, there is still padlock on the NM icon Expected results: When the connection is down, padlock should be removed Additional info: --- Additional comment from avagarwa on 2010-10-13 15:20:11 MDT --- I looked at this, here is the reason. Openswan does not create any interface like tun0 something done by vpnc. When tun0 is down, NM gets to know about it, and takes care of removing the padlock. However, as there is no such interface with Openswan, NM never comes to know about it, and does not take padlock icon away. It will probably require changes in NM, so that when openswan connection goes down, and it should take this padlock away, or it will require creating tun like interface in Openswan (but Openswan upstream does not seem comfortable with it). --- Additional comment from mcepl on 2010-10-15 06:11:11 MDT --- So, what to do? Switch this to NM bug? --- Additional comment from avagarwa on 2010-10-15 08:34:25 MDT --- Specifically, if NM can track ip address add/delete events in addition to network interface up/down events, then it can work for Openswan. I will send email to Dan Williams, and see what are his views. --- Additional comment from mmosesoh on 2010-12-14 15:43:26 MST --- this affects RHEL 6.0 also
FYI, the Fedora maintainer is orphaning vpnc: http://lists.fedoraproject.org/pipermail/devel/2011-August/156218.html With attendant worry about building up unaddressed issues.
Created attachment 521276 [details] openswan cisco interop issue patch
Created attachment 521277 [details] NM-openswan patch
I have attahced 2 patches one for openswan and another one for networkmanager-openswan . Following are links of test builds: openswan: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3604015 nm-openswan: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3604017 With the attached patches, I am not able to reproduce the issue. I would appreciate any feedback by testing the above builds.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
(In reply to comment #13) > I have attahced 2 patches one for openswan and another one for > networkmanager-openswan . > > Following are links of test builds: > > openswan: > http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3604015 > > nm-openswan: > http://brewweb.devel.redhat.com/brew/taskinfo?taskID=3604017 > > > With the attached patches, I am not able to reproduce the issue. I would > appreciate any feedback by testing the above builds. I am still wondering if there is any feedback to the above builds. Otherwise I will go ahead commit the fixes if acks are set.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1771.html