News: This forum is now permanently frozen.
Pages: [1]
Topic: The Dreaded 192.168.1.x Multiple IPSEC VPN Issue  (Read 2568 times)
« on: July 17, 2008, 17:48:46 »
johndennis *
Posts: 1

Hi All,

Let me preface this by saying that I have several monowalls in production running IPSEC VPN’s, and they are working wonderfully.  So this is not a basic IPSEC VPN question… 

Question: I have multiple customers out there who were to lazy to change their network IP’s from the default (192.168.1.x) addresses that came with their routers.  I would like to know if there is a way to create IPSEC VPNs to these folks using monowall.  In the past on other boxes I have been able present a (1:1 Network) NATed network range (like 192.168.86.x) to the remote VPN device.  The VPN will be between my checkpoint router and the monowalls that we are providing for these sites.

Unfortunately these two customers cannot renumber their networks without a lot of pain, so I am trying to find a workaround.

I will continue to experiment with the latest beta to see if I can get this working.  Thanks for any help that you can provide!

Monowall Rocks!  Kudos to everyone involved with this fantastic product.

-John
« Reply #1 on: July 18, 2008, 01:25:47 »
cmb *****
Posts: 851

No way to do this at this time. The only possible solution is NATing traffic across the VPN, which is possible with Cisco and some other commercial firewalls, but is ugly and won't work for certain services (like Windows file shares for one).
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines