On Fri, Apr 11, 2008 at 3:14 PM, Chris Severance
<severach at users dot sourceforge dot net> wrote:
> Eventually this runs into the problem where you get a collision of RFC
> 1918 subnets and you can't change them. The solution is to map the
> private IPs to public IPs and form an IPSec VPN between the public IP
> addresses. A large company with many VPNs will have already done this
> and using public IPs will be a matter of policy.
> vpn192.168.0.10::peer126.96.36.199 <-> peer188.8.131.52::vpn184.108.40.206
The other problem here is that if the remote side has a large number
of VPN's, they will likely have numerous peers using 192.168.1.0/24 or
similar, so they will require you to use source-NAT over the tunnel,
which m0n0wall does not support.
I would have been trying to configure the type of tunnel you are
describing if it weren't for the NAT problem. I ended up purchasing a