RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 705890 - Doesn't work as an idicator of the VPN connection
Summary: Doesn't work as an idicator of the VPN connection
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager-openswan
Version: 6.1
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: 6.1
Assignee: Avesh Agarwal
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 641068
Blocks: 637248 738385 750914
TreeView+ depends on / blocked
 
Reported: 2011-05-18 19:38 UTC by Jacob Hunt
Modified: 2018-11-14 12:38 UTC (History)
11 users (show)

Fixed In Version: NetworkManager-openswan-0_8_0-7_el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 641068
: 738385 (view as bug list)
Environment:
Last Closed: 2011-12-06 19:04:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
openswan cisco interop issue patch (12.04 KB, patch)
2011-09-02 19:30 UTC, Avesh Agarwal 		no flags Details | Diff
NM-openswan patch (1.02 KB, patch)
2011-09-02 19:31 UTC, Avesh Agarwal 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1771 0 normal SHIPPED_LIVE NetworkManager-openswan bug fix update 2011-12-06 01:01:32 UTC

Description Jacob Hunt 2011-05-18 19:38:13 UTC 
+++ 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
Comment 10 Paul W. Frields 2011-08-30 20:01:54 UTC 
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.
Comment 11 Avesh Agarwal 2011-09-02 19:30:26 UTC 
Created attachment 521276 [details]
openswan cisco interop issue patch
Comment 12 Avesh Agarwal 2011-09-02 19:31:10 UTC 
Created attachment 521277 [details]
NM-openswan patch
Comment 13 Avesh Agarwal 2011-09-02 19:35:24 UTC 
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.
Comment 14 RHEL Program Management 2011-09-14 17:08:20 UTC 
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.
Comment 15 Avesh Agarwal 2011-09-30 20:05:56 UTC 
(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.
Comment 22 errata-xmlrpc 2011-12-06 19:04:21 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.