I was able to figure out the solution to this problem but like most things
it spawned another. By changing the networks to just the 192.168.100.0/24
and 192.168.222.0/24 on the main and remote firewalls respectively I was
able to establish the tunnel. The problem I face now is that the main site
routes about 20 different subnets and I only have access to the 100 network
over the tunnel. Do I need to add static routes somewhere?

Thanks in advance

-----Original Message-----
From: Fritz Platzke [mailto:fritz at milkpotato dot org] 
Sent: Thursday, April 13, 2006 3:44 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] Ipsec tunnel problem

I have two boxes that I'm trying to create a tunnel between and I'm having
absolutely no luck. Following is a rundown of my settings. What am I doing
wrong?

Main Site
Internal IP		192.168.100.252
IPSec local net	192.168.221.0/24
IPSec remote net	192.168.222.0/24
IPSec interface	WAN
IPSec remote gw	xx.xx.xx.xx
P1			aggressive
P1 encr		blowfish
P1 hash		md5

Remote site
Internal IP		192.168.222.254
IPSec local net	LAN
IPSec remote net	192.168.221.0/24
IPSec interface	WAN
IPSec remote gw	xx.xx.xx.xx
P1			aggressive
P1 encr		blowfish
P1 hash		md5

Did I do something wrong?
I see nothing in the Diagnostics -> IPSec -> SAD SPD on the other hand shows
the local and remote nets. What else do I need to check?

Thanks in advance
Fritz Platzke


---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch