Tim, thanks for the response.

1) Yes, the DMZ is in a private address space (10.100.2.x).
2) Yes, all appropriate rules have been added.
3) I just added a temporary rule on that box that allowed everything to pass to the WAN interface,
and nothing changed.

Something worth mentioning is that this monowall works PERFECTLY on the physical computer I am
attempting to replace.  I'm thinking it has something to do with the networking on the host
machine...possibly?  The host machine is a Windows 2003 server for what it's worth.

I'm not so sure about you, but this Nelson is definitely in some trouble!

-----Original Message-----
From: Tim Nelson [mailto:tnelson at rockbochs dot com]
Sent: Monday, August 13, 2007 1:59 PM
To: Marty Nelson
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Need Monowall in VMWare Help!

Marty-

Check the following:

1. Is your DMZ in a private address space? Uncheck the "Block Private
Networks" option at the bottom of your WAN interface page.
2. Did you add any firewall rules to allow traffic through the box?
You'll need to add a rule to allow traffic Source:LAN and
Destination:ANYWHERE for starters.
3. Since you can't ping the WAN, try adding a rule to start with that
allows all traffic on the WAN interface. At the very least, add a rule
to allow ICMP (ping).

If that doesn't work, then I guess we "Nelsons" are in some trouble...

Tim Nelson
Technical Consultant
Rockbochs Inc.


Marty Nelson wrote:
> Afternoon all.
>
> I'm attempting to turn a couple of physical boxes I have running monowall into virtual boxes and
am running into problems.  Currently the physical computer is a gateway of sorts that is sitting
with the LAN interface in my LAN, and the WAN interface sitting in my DMZ (See my previous postings
as to why this is the way it is if you'd like)
>
> Here's what I've done so far:
>
>
> *         Downloaded and installed VMWare Server 1.0.3.
>
>
> *         Downloaded Chris' virtual appliance from here:
http://chrisbuechler.com/m0n0wall/vmware/challenge/ the one thing I did off the bat was drop the
updated cdrom-1.231.iso into the folder and had VMWare point to it as the virtual ISO vs. the
1.2.iso that's in there.
>
>
>
> *         I then fired up the machine and changed the local address to an address I could connect
to on my network.
>
>
>
> *         From there I uploaded the config that I downloaded from the physical monowall into the
virtual monowall, and rebooted.  When it came back up I assigned the network ports, lnc0 for LAN and
lnc1 for WAN, and rebooted again.
>
>
>
> *         Here's where it falls apart.  I can connect to the virtual monowall just fine on the LAN
interface.  Everything operates as you'd expect.  The problem is that the WAN interface doesn't seem
to want to respond to anything.  I've gone through VMWare's network settings and have done the
following:
>
>
>
> o   Bridged Ethernet 1 to VMnet0 (Which is physically connected to my LAN)
>
> o   Bridged Ethernet 2 to VMnet4 (Which is physically connected to my DMZ)
>
> I'm unable to ping the WAN interface, nothing shows up in the log, nada.
>
> Any help or suggestions would be greatly appreciated.
>
> Thanks,
>
> -Marty
>
>