Thanks, i think that helped, i'm now getting data to pass further than
before, but this is what my firewall log shows.  I tried to add a LAN
rule to fix the deny noted below, but it still is denying the hop to
192.168.10.200

deny   	08:49:20.993918  	 LAN  	 X.Y.85.26, port 47626
192.168.10.200, port 80  	 TCP

pass 	08:49:20.993823 	WAN 	X.Y.85.26, port 47626
192.168.10.200, port 80 	TCP

-----Original Message-----
From: Chris Buechler [mailto:cbuechler at gmail dot com] 
Sent: Friday, July 28, 2006 8:22 AM
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] port forward across IPSEC

On 7/28/06, Brandon Hamilton <bhamilton at snowcomputer dot com> wrote:
>
> In testing, I've setup NAT and a Rule that forwards port 21
> 192.168.10.200 (which is an address across the IPSEC VPN) and I cannot
> access it.
>
> What am I missing?
>

I don't know that this will work, but if it does you'll need this
(it's related to anything initiated by m0n0wall, not just SNMP):
http://doc.m0n0.ch/handbook/faq-snmpovervpn.html

-Chris

---------------------------------------------------------------------
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