Red Hat Bugzilla – Bug 739949
Openswan net-to-net not work with unencrypted connection on specific port, when all other connections are encrypt.
Last modified: 2015-03-02 00:26:37 EST
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):
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
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
On GW-left and GW-right I have this:
: PSK "whatever"
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
Connection on port 30000 fail (nc output is connection timeout)
Connection on port 20000 (or other) is all right and encrypted
Connection on port 30000 pass
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.
This is really the same issue as #742126
(note a workaround is to specify both ends of the protoport= line, in this case:
But this will be resolved for rhel-6.6 to work without adding the leftprotoport as well.
A bug was found and fixed in netlink_shunt_eroute() that addresses this issue
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.