[Openswan Users] really basic peer-to-peer setup

[Alan McKay]

On Fri, May 3, 2013 at 9:18 PM, Simon Deziel <simon at xelerance.com> wrote:
> You have some options but the simplest/cleanest would be to run IPsec
> directly on 192.168.160.10. If that's not possible I see two possible
> solutions:

Eventually I want to have it running on both firewalls - I'm doing it
first on 160.11 because it is a new Ubuntu release.  160.10 is RHEL5
and I just don't want to be playing with old releases and
complications that come with them.   160.10 runs NAT as well.   If
this will run fine with the RHEL5 RPMs then I can do that.

> dirty: NAT'ing when exiting solexa1 to 192.168.160.0/24

That's NAT in the wrong direction - definitely do not want to do that.

> clean: on the other machines part of 192.168.160.0/24 configure a route
> to 172.16.0.0/24 and 172.30.0.0/24 pointing to 192.168.160.11. Make sure
> to enable forwarding on solexa1.

That is pretty easy to do - good idea.

> ping 172.16.0.1 -I 192.168.160.11

Still not working :-(   What the heck?  :-(

root at solexa1:~# ping 172.16.0.1 -I 192.168.160.11
PING 172.16.0.1 (172.16.0.1) from 192.168.160.11 : 56(84) bytes of data.
^C
--- 172.16.0.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9071ms





-- 
“Don't eat anything you've ever seen advertised on TV”
         - Michael Pollan, author of "In Defense of Food"