Thank you for the replies now that they are coming through, but, I figured 
it out the next day after I emailed the list.  The problem was with the tcp 
idle timeout on the system advance settings page.  I had this set to 30 
minutes , then changed it to 3 hours.

What was happening is, someone would bring up a client program to access a 
server on the other side of the vpn and then they would not use the client 
application for a while.  When they needed it they alt tabed to it and boom 
it said they were not connected to the server no more.

I apologize for asking the list before researching like the archives etc, 
but at the time the website was down and I couldn't get into anything.  I 
figured maybe the list was still working and tried it.

Thanks
Matthew

----- Original Message ----- 
From: "Chris Buechler" <cbuechler at gmail dot com>
Cc: <m0n0wall at lists dot m0n0 dot ch>
Sent: Saturday, August 05, 2006 2:32 AM
Subject: Re: [m0n0wall] firewall blocking vpn subnets


> On 8/2/06, mwagley at cox dot net <mwagley at cox dot net> wrote:
>>
>> I even created rules on the LAN side in the Firewall with 172.16.1.0 to 
>> 172.16.2.0 to allow > all type tcp,udp, etc and all ports.   It still 
>> pops this up.  And the block still occurs.
>>
>> Am I missing something?  Why would m0n0wall block traffic going across 
>> the vpn?
>>
>
> http://doc.m0n0.ch/handbook/faq-legit-traffic-dropped.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
>
>