Comments on: IPSec Communication for VPN Setup in CentOS 6 / RHEL 6.3

By: Rahul Panwar

Rahul Panwar — Wed, 13 Nov 2013 18:22:19 +0000

Hi Apoorv,
Thanks for showing your interest on my blog. :-)
I also like your blog’s contents, you are a creative writer, hope you will continue this thing.
All the best.

By: Apoorv Dwivedi

Apoorv Dwivedi — Wed, 13 Nov 2013 17:54:05 +0000

well the stuff like this really made me interested in your blog..

By: Rahul Panwar

Rahul Panwar — Fri, 11 Oct 2013 02:50:44 +0000

This post is a how to of a simple configuration of ipsec. But you can configure it as showing in diagram with this method. Please use the public IP addresses in the ipsec configuration instead of private IP 192.168.1.1 and 192.168.1.2 given in this post.
In this case your ipsec devices will also communicate directly on public IP addresses and real clients will communicate through gateways.
All the best :-)

By: davidcsi

davidcsi — Wed, 09 Oct 2013 12:43:07 +0000

Hello, This is a great step-by-step guide… But i’m missing something.

You talk about networks 192.168.1.1 and 192.168.2.1, which (I assume) are behind either gateways. And this is what you set up on the configs, correct?

My question is: Where do you setup the PUBLIC addresses for each gateways? With this setup I understand both networks will be able to “see” each other by way of the gateways, but I don’t see where the public IPs are setup…

Thanks!

By: Rahul Panwar

Rahul Panwar — Wed, 25 Sep 2013 05:03:06 +0000

Hi Charles,
Thanks for feedback and solution. :-)

By: Charles Kozler

Charles Kozler — Tue, 24 Sep 2013 19:42:41 +0000

Thank you for the excellent post. As a heads up I was getting a compile time error with GCC 4.4 which uses strict aliasing. As a work around do the following before configure (this is in CentOS 6.4)

export CFLAGS=”-fno-strict-aliasing”

By: Rahul Panwar

Rahul Panwar — Mon, 16 Sep 2013 18:26:54 +0000

Preshared key has to be added to /etc/racoon/psk.txt. The syntax is very simple, each line contains a host IP address and a key. These parameters are separated with a tab or space. For example:
192.168.1.2 somekey
Replace “somekey” with the password (plain text) of your choice.

By: jibin

jibin — Mon, 16 Sep 2013 10:19:37 +0000

may i know how to create pre_shared_key….?

By: Rahul Panwar

Rahul Panwar — Fri, 06 Sep 2013 11:00:45 +0000

Yes, if your setkey.conf is in /etc/raccoon directory. Both system can have same setkey.conf file.

By: Patrick

Patrick — Thu, 05 Sep 2013 09:18:46 +0000

You wrote:
The same /etc/setkey.conf can be created on the 192.168.1.2…

Didn’t you mean:
The same /etc/raccoon/setkey.conf can be created on the 192.168.1.2 ?