[ previous ] [ next ] [ threads ]
 From:  "Brandon Holland" <brandon at cookssaw dot com>
 To:  "'Manuel Kasper'" <mk at neon1 dot net>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Static routes not working in 24!
 Date:  Wed, 21 Jan 2004 16:01:40 -0600
Thanks, so I was right :)

I had just upgraded to 24 the day it came out, and didn't see any need
for dynamic vpn.

The m0n0 "Change log" was cryptic enough that I didn't realize that pb25
had anything to do with "fixed" static routes :) but I guess it did.

At any rate, I guess I should have checked before reporting a bug. (I
however wasn't sure it was a bug though)

1. Sorry about that.
2. Please forgive me.
3. Thanks.


-----Original Message-----
From: Manuel Kasper [mailto:mk at neon1 dot net] 
Sent: Wednesday, January 21, 2004 12:25 PM
To: Brandon Holland
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Static routes not working in 24!

On 21.01.2004, at 18:15, Brandon Holland wrote:

> The above exception is: the m0n0wall router (which is a .22 client)
> cannot ping the .23 subnet - a ping attempt results in a "no route to
> host" response for each packet, but it can ping the local subnet and
> ping the internet (and as said earlier, it gives the .22 subnet 
> internet
> access)

Please use the latest version before reporting problems (this goes for 
everybody!). Pre-pb25, m0n0wall restricted itself with respect to the 
outbound connections (including ping) it could establish (and the rule 
generator didn't care about static routes when generating the rules to 
allow outbound pings from m0n0wall itself), so the "no route to host" 
error might as well mean that the packet has been dropped by ipfilter, 
which returned that error to the ping application. So could you please 
upgrade to pb25 and try again?

- Manuel

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