[Openswan Users] UPDATE: Tunnel up, can ping, cannot connect!! :S

simon charles charlessimon at hotmail.com
Thu Dec 2 18:43:08 EST 2010

RM ,
     Is that your complete iptables ruleset on that xxx.1 box ? Could you post your complete iptables ruleset. I see that you have rules defined for your OUTPUT filter - what is your default policy on that chain ? You might want to look into incorporating the following if your default policy on the INPUT chain is DROP/REJECT
"iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT".  If your default policy on the OUTPUT chain is anything other than ACCEPT then you would have to add those traffic to the exclusion list on that OUTPUT chain.

- Simon Charles - 

From: rodrigomf at bl.com.mx
Date: Thu, 2 Dec 2010 14:25:55 -0600
To: paul at xelerance.com; wgillespie+openswan at es2eng.com
CC: users at openswan.org
Subject: Re: [Openswan Users] UPDATE: Tunnel up, can ping,	cannot connect!! :S

Update to this question. (I think with this update this question should become a simple one for experts)
I disabled iptables on my server xxx.xxx.xxx.1 and the connection is ESTABLISHED. This means iptables is stopping the SYN|ACK packages from zzz.zzz.zzz.3 somehow.
This are the iptables rules I'm applying:
iptables -I OUTPUT -p udp --dport 500 -j ACCEPTiptables -I INPUT -p udp --dport 500 -j ACCEPTiptables -I INPUT -p udp --dport 4500 -j ACCEPTiptables -I OUTPUT -p udp --dport 4500 -j ACCEPTiptables -I INPUT -p 50 -j ACCEPTiptables -I OUTPUT -p 50 -j ACCEPT
I think this is the last step to have mi first fully functional OpenSWAN VPN. Please help! :D
Thank you!RM
El 02/12/2010, a las 12:36, Ing. Rodrigo Méndez escribió:Hi again
You helped me last week in setting up a VPN that went apparently successful, but there's a problem.
I remind you my configuration: xxx.xxx.xxx.1 (my public centos box) <-----> yyy.yyy.yyy.2 (Juniper vpn concentrator) <---> zzz.zzz.zzz.3 (box in private lan)
I can ping the machine in the remote LAN perfectly (xxx.1 to zzz.3) but cannot connect to any port through telnet. The interesting part of this is that I see the ESP traffic coming out of xxx.1, the admin of the Juniper Concentrator (yyy.2) can see my traffic coming through and also the guy in the zzz.3 box (private lan).
But this guy (zzz.3) sees the connection dropping each time. See example:
[admwsph at WebSphere2pt ~]$ while true; do netstat -na | grep 9082; sleep 3; done 
tcp        0      0 zzz.zzz.zzz.3:9082          xxx.xxx.xxx.1:46650       SYN_RECV     
tcp        0      0 :::9082                     :::*                        LISTEN    
This command is run in zzz.3
Do you have any idea of what can be going on here?
Thank you very much for your help.Saludos!RM
El 23/11/2010, a las 14:51, Paul Wouters escribió:On Tue, 23 Nov 2010, "Ing. Rodrigo Méndez" wrote:

This is the result from ipsec verify:

Looks good.

The people from the Juniper VPN concentrator say they don't see any traffic coming from our IPs, so it would seem there's no traffic coming out from Box 1
(CentOS box). The strange thing is it doesn't work even if iptables is disabled (so no blocking is apparently occurring, or at least it isn't the main
My best guess now is that I'm having a routing problem. 

I don't think so...

Any ideas on how to tell Linux to route the packages going to zzz.zzz.zzz.3 through the tunnel?? (I'm using netkey, not KLIPS)

manual routing should not be used. netlink will snatch the packets.

I can't find any route to yyy.yyy.yyy.2 or zzz.zzz.zzz.3 (the box in the private lan) anywhere in the routing table. I'm not sure if this is OK.

that's fine.

It seems you have one interface online. Are you behind a port forward? Is your upstream
router filtering packets?

Try adding forceencaps=yes ?


Users at openswan.org
Micropayments: https://flattr.com/thing/38387/IPsec-for-Linux-made-easy
Building and Integrating Virtual Private Networks with Openswan: 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openswan.org/pipermail/users/attachments/20101202/56a542c7/attachment-0001.html 

More information about the Users mailing list