Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Testing openswan net to net funcionality.
When all connections are encrypted, funcionality is all right. But if I want unencrypted connection on specific port and all other connections encrypted, the funcionlity is broken.. Encrypted connections are fine, but unencrypted connection on specific port doesn't work.
Version-Release number of selected component (if applicable):
openswan-2.6.32-6.el6
How reproducible:
always
Steps to Reproduce:
I have this test case net topology:
left subnet: 192.168.111.0/24
right subnet: 192.168.100.0/24
middle subnet: 192.168.50.0/24
GW-left GW-right
192.168.111.179 | | 192.168.50.5 -----192.168.50.6 | | 192.168.100.212
/ ipsec \
/ \
/ \
192.168.111.81 | | | | 192.168.100.226
PC-left PC-right
On GW-left and GW-right I have this:
/etc/ipsec.secrets
: PSK "whatever"
/etc/ipsec.conf
conn test
left=192.168.50.5
right=192.168.50.6
leftsubnet=192.168.111.0/24
rightsubnet=192.168.100.0/24
auto=add
authby=secret
type=tunnel
ike=aes256-md5
phase2=esp
conn pass
left=192.168.50.5
right=192.168.50.6
leftsubnet=192.168.111.0/24
rightsubnet=192.168.100.0/24
auto=add
authby=secret
type=passthrough
ike=aes256-md5
phase2=esp
rightprotoport=tcp/30000
On both GW run
ip xfrm state flush
ip xfrm policy flush
service ipsec restart
ipsec auto --route pass
ipsec auto --route test
On PC-right run:
nc -l 192.168.100.226 30000
nc -l 192.168.100.226 20000
On PC-left run:
echo "Hi" | nc -v -w 30 192.168.100.226 30000
echo "Hi" | nc -v -w 30 192.168.100.226 20000
Actual results:
Connection on port 30000 fail (nc output is connection timeout)
Connection on port 20000 (or other) is all right and encrypted
Expected results:
Connection on port 30000 pass
Comment 1RHEL Program Management
2012-05-03 05:00:46 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
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.
(note a workaround is to specify both ends of the protoport= line, in this case:
rightprotoport=tcp/30000
leftprotoport=tcp
But this will be resolved for rhel-6.6 to work without adding the leftprotoport as well.
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-2014-1588.html
Description of problem: Testing openswan net to net funcionality. When all connections are encrypted, funcionality is all right. But if I want unencrypted connection on specific port and all other connections encrypted, the funcionlity is broken.. Encrypted connections are fine, but unencrypted connection on specific port doesn't work. Version-Release number of selected component (if applicable): openswan-2.6.32-6.el6 How reproducible: always Steps to Reproduce: I have this test case net topology: left subnet: 192.168.111.0/24 right subnet: 192.168.100.0/24 middle subnet: 192.168.50.0/24 GW-left GW-right 192.168.111.179 | | 192.168.50.5 -----192.168.50.6 | | 192.168.100.212 / ipsec \ / \ / \ 192.168.111.81 | | | | 192.168.100.226 PC-left PC-right On GW-left and GW-right I have this: /etc/ipsec.secrets : PSK "whatever" /etc/ipsec.conf conn test left=192.168.50.5 right=192.168.50.6 leftsubnet=192.168.111.0/24 rightsubnet=192.168.100.0/24 auto=add authby=secret type=tunnel ike=aes256-md5 phase2=esp conn pass left=192.168.50.5 right=192.168.50.6 leftsubnet=192.168.111.0/24 rightsubnet=192.168.100.0/24 auto=add authby=secret type=passthrough ike=aes256-md5 phase2=esp rightprotoport=tcp/30000 On both GW run ip xfrm state flush ip xfrm policy flush service ipsec restart ipsec auto --route pass ipsec auto --route test On PC-right run: nc -l 192.168.100.226 30000 nc -l 192.168.100.226 20000 On PC-left run: echo "Hi" | nc -v -w 30 192.168.100.226 30000 echo "Hi" | nc -v -w 30 192.168.100.226 20000 Actual results: Connection on port 30000 fail (nc output is connection timeout) Connection on port 20000 (or other) is all right and encrypted Expected results: Connection on port 30000 pass