General Questions

No disrespect either but, I quoted your question above, which I answered, yes it can do DHCP, which you verify that it is working.

That's fine, we will move on.

You can't browse websites, but you can ping.

So that means your can resolve DNS to ping. The next step is to look at the firewall states in m0n0wall and see if the clients are actually trying to establish a connection on port 80 to the website. If your firewall states table is empty, check the firewall logs and see if packets on port 80 are being blocked.

The fact that m0n0wall is on the same subnet and range (both LAN and WAN) means that with m0n0wall you need to make sure the "Block private networks" for the WAN setup is turned off. Otherwise, you'll encounter exactly what it sounds like where you can ping, but nothing else can get through.

My point was that in this thread, I have already verified about 3 or 4 times that DHCP and routing through the default gateway are working, and it's frustrating to have to start over from scratch.

Still, I don't want to be an unappreciative a$$h0l3.     sorry
I really do apprecaite you picking this up and working on it with me.
So, thank you.   

On now....
I looked and the 'Block private networks' check box is still unchecked.

Next? 

Thanks.
steven

You're in luck. I had a spare m0n0wall machine. I was setting up a mini network exactly as you described.

While doing it, I caught the problem. You have the LAN and WAN in the same IP range. You can't do that, you need to offset your LAN by just 1, so given your example of 10.0.0.222 for the LAN, change it to 10.0.1.222, change your DHCP range to reflect that, and the clients on the LAN side via DHCP will be able to do anything through m0n0wall again like you had before with web surfing and other fun things.

That may be why no one else has replied here, I didn't catch that at first because I thought you already had them separate, but I see now they were in the identical IP range.

I hope that helps. 

You're in luck. I had a spare m0n0wall machine. I was setting up a mini network exactly as you described.

While doing it, I caught the problem. You have the LAN and WAN in the same IP range. You can't do that, you need to offset your LAN by just 1, so given your example of 10.0.0.222 for the LAN, change it to 10.0.1.222, change your DHCP range to reflect that, and the clients on the LAN side via DHCP will be able to do anything through m0n0wall again like you had before with web surfing and other fun things.

That may be why no one else has replied here, I didn't catch that at first because I thought you already had them separate, but I see now they were in the identical IP range.

I hope that helps. 

Ok....ignorance speaking again here......sorry, but I can't do this (or so I think ).
If I change the LAN IP for my M0n0wall as you suggested, then I can't get to it anymore from my LAN (right?).

So, since the LAN interface is the one I have in DNS, I changed the WAN one (I know...not what you said to do), but no change; DHCP client still can't surf web.

So, do you really mean for me to change the LAN interface IP?
If so, how will I get to it from my LAN?

Sorry, I know a little about a lot of things and a lot about a few things, but this is not my main thing. 

steven

     ?

Ok....ignorance speaking again here......sorry, but I can't do this (or so I think ???).
If I change the LAN IP for my M0n0wall as you suggested, then I can't get to it anymore from my LAN (right?).

So, since the LAN interface is the one I have in DNS, I changed the WAN one (I know...not what you said to do), but no change; DHCP client still can't surf web.

So, do you really mean for me to change the LAN interface IP?
If so, how will I get to it from my LAN?

Sorry, I know a little about a lot of things and a lot about a few things, but this is not my main thing.  :)

steven

Sorry about the long delay in the reply, I don't frequent the forums here that much, hehe.

Yes, only the LAN IP, you can change it at Interfaces / LAN in the configuration. Just add another number after the XX.XX. <-  . XX part.

So if you were using 10.0.0.1 for the LAN IP, change it up one to 10.0.1.1.  Save changes, but don't reboot yet. The reason being, DHCP is still set for the old range of 10.0.0.0, so before you reboot, go into the DHCP settings at Services / DHCP server and change the range to reflect the new LAN range. So for example, if it was assigning 10.0.0.5 to 10.0.0.10 IP range, you would add the one up to it, so you get 10.0.1.5 to 10.0.1.10 as the new range.

After you reboot, you'll be able to access m0n0wall at the *new* LAN IP that you just set instead of the old one.  So using the example above, the old way was http://10.0.0.1, but the new way would be typing http://10.0.1.1 in your web browser to access the m0n0wall web based GUI config page.

I hope that explains it better, let me know if you need more help.