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