Solved

Checkpoint VPN through Iptables

Posted on 2010-08-23
5
859 Views
Last Modified: 2012-05-10
My company have a firewall Linux / iptables, managed by firewallbuilder.

There is a user in my company, that needs to access a another company using a VPN client (Check Point VPN-1 SecureClient NGX R60 HFA2). But I am not able to perform this configuration in firewallbuilder / iptables.

The another company IT, which has firewall checkpoint, said that I needed just allow udp 500 port to ther firewall and put the rule as stateful. I confirmed that all rules in firewallbuilder are stateful by default and even allow all ports from client to destination, the VPN client does not work.

How can I troubleshoot this problem?
0
Comment
Question by:strausswalter
  • 2
  • 2
5 Comments
 
LVL 8

Accepted Solution

by:
jimmyray7 earned 500 total points
ID: 33503902
Try also allowing UDP port 4500, which is sometimes used if a client is behind NAT.
0
 
LVL 33

Expert Comment

by:Dave Howe
ID: 33519914
I have a cp secureclient (r60, but r56 works too) behind a nat. the boxes to tick are office mode and both udp encapsulation boxes in the advanced settings properties page for the connection.
0
 

Author Comment

by:strausswalter
ID: 33521468
I am concluding that the problem is not about ports, I already allow all ports. The problem apparently, is NAT related. I sow that IPSec is not compatible with traditional NAT, I would have to enable NAT-T. I am researching how to setup this type of NAT in iptables.

Using a direct Internet link at client computer (without NAT), the VPN client run normally.
0
 

Author Comment

by:strausswalter
ID: 33585750
Problem solved.

With the help of the company that use this vpn client, I downloaded the VPN client and tried re-install the vpn client in another computer. Looking for the client IP in iptables logs (tail -f /var/log/messages | grep 10.220.2.4) I could see a connect to another company firewall IP (201.x.x.x) at 4500 port. But in a secound connection the VPN client attempted to connect in a strange internal IP (10.1.x.x) at port 500.

The problem was that another company already owned the network 10.220.0.0, but they did not realize it. We assume, after these results, that after the first access the VPN client downloaded the another company network topology and the vpn client thought that it was in the company network and attempted to access a internal server.

We create a separate VLAN to this client, with another network address.

Now it is working properly.
0
 
LVL 33

Expert Comment

by:Dave Howe
ID: 33586747
no company owns 10.x.x.x - its an rfc1918 subnet :)
0

Featured Post

Free Gift Card with Acronis Backup Purchase!

Backup any data in any location: local and remote systems, physical and virtual servers, private and public clouds, Macs and PCs, tablets and mobile devices, & more! For limited time only, buy any Acronis backup products and get a FREE Amazon/Best Buy gift card worth up to $200!

Join & Write a Comment

Introduction We as admins face situation where we need to redirect websites to another. This may be required as a part of an upgrade keeping the old URL but website should be served from new URL. This document would brief you on different ways ca…
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now