Kyle McBride wrote:
> Are your clients getting DHCP leases from the m0n0wall? If so, are they
> getting DNS server and default gateway?  Could just be a name resolution
> problem.  Can you ping a public IP address (other than your m0n0wall's) from
> a client?
>
> Maybe you need dns forwarder turned on on the m0n0wall.
>
> (just read your post again...) if you can't ping yahoo.com from m0n0wall's
> diagnostics area then even m0n0wall is not getting name resolution and
> routing out to internet site given its dns servers and wan link.  That's a
> problem.  Maybe compare information with ipcop and see what's different.
>
> Kyle
>
> -----Original Message-----
> From: Mark [mailto:markryan at cfl dot rr dot com] 
> Sent: Saturday, November 04, 2006 5:35 AM
> To: monowall
> Subject: [m0n0wall] help with my new WRAP and m0n0wall
>
> Hi,
> I just received a m0n0wall WRAP firewall and I am having some weird 
> problems.
>
> The firewall boots fine and grabs a dhcp from my cable service no 
> problem.  I bring the clients up and I have no internet at all on the LAN.
>
> I can ping the monowall box from the client and i can ping the client 
> from the monowall interface.  I can ping the public ip from the client 
> also.  The problems is getting out from the monowall.  There is 
> nothing.  I cannot ping yahoo.com from either the monowall 
> troubleshooting area or the client.
>
> Any idea what is going on here?
>
> The monowall has the correct ip and dns servers which it gets through 
> dhcp.  It just doesn't seem to be communicating with the outside after that.
>
> When i plug my ipcop computer back in, everything works just fine.
>
> Heeeelp please!
>
> Mark
>
>
> ---------------------------------------------------------------------
> 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
>
>
>   
I am totally mistified as to whats wrong

its like there is no connection past the wan gateway at my isp.

mark