Topic: FreeSwan IPSEC tunnel

[Randall Perry]

HELL-OH

I am trying to setup an IPSEC tunnel here at the office (in Indiana) before I have to drag the other box down to Orlando, FL.  I installed the freeswan RPMs and made entries to the IPSEC VPN panel, but they do not connect.  I can't ping from 10.0.0.0/8 to 192.168.2.0/24.  I have not been able to get it to setup under Local Networks panel because it does not recognize the other SME router as on the local network.

Would this have anything to do with they are actually both using the same Cisco router as an external gateway?
 
at the Bash prompt, when looking at route tables, it shows that it has to pass through that router.

I know it sounds like I just answered my own question, but I will be flying down there to install cabling for the phones and network, install and program the PBX and voicemail and setup all the PCs.  I am crammed for time and won't have time to properly troubleshoot-it is just going to have to work.

[Rob Wellesley]

Assuming you are testing two SME boxes - connect the EXT NICs together with a cross-over cable. Make the IP of the other box the gateway for the local box. You should be able to ping the internal nic (and therefore the remote lan) of the remote host from the local host.

ifconfig will show sent/recieve amounts for the IPSEC connection. these should increase with each ping. this is to verify the secure conection is being used and not just a route.

[ryan]

Randall,

I attempted to set up an IPSEC VPN using the same router and could not get it to work.  I am using SME 5.1.2 servers.  In general, IPSEC vpn on SME using Freeswan is quick to set up and has proven very reliable for my WAN.

Good Luck,

Ryan