Thanks to Vincent, et al. I got this resolved.

When LAN and DMZ clients had no internet connectivity:

Assigning m0n0wall WAN port another unused IP and being, careful not to
enable proxyARP on that IP.

When external clients cannot access internal server normally:

Enabling proxyARP on IPs in question fixed that right away. So I did
need proxyARP on the VIPs.

And everything works.

Man, I love this software. Many many thanks Mr. Kasper, Mr. Buechler,
and Mr. McBeath, and everyone else.

Dave

-----Original Message-----
From: Will Dyson [mailto:will dot dyson at gmail dot com] 
Sent: Friday, March 25, 2005 12:09 PM
To: David Cavanaugh
Subject: Re: [m0n0wall] Just need some clarification (or I need some
had-holding)

On Fri, 25 Mar 2005 11:30:41 -0500, David Cavanaugh
<dcavanaugh at thewebpros dot net> wrote:
> O.K. Now I feel like an idiot:
> 
> I have ten public IPs. I want to route five of them through m0n0wall's
> WAN port to the OPT1 (now called DMZ) port. I set appropriate entries
in
> the Server NAT dialogue, Proxy ARP, inbound NAT / firewall rules.
> 
> Suffice to say it didn't work-- no internet connectivity from LAN or
> DMZ.
 
It always helps to tell us the version of the m0n0wall firmware.
Without that and an example of the non-working configuration file, it
is really hard to help you.

-- 
Will Dyson

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