I set up a new openwrt install using Kamikaze on a WRT53G V3.  The only additional package I installed is nodogsplash.  I connect to the router wirelessly from Windows XP.  I can get on the internet, and I can access the router through the web browser, and I can get to it with SSH, but when I try to ping anything I get destination host unreachable.  What did I do wrong?  The router address is set at 192.168.5.1, and the dsl modem is at 192.168.1.1.  Everything is DHCP.

What am I missing?

Thanks,
Igor

Just by reading your post there can be a few things that is going on.

First - If you have a DSL modem make sure that the modem is in "bridged mode" since your router is going to be handling NAT. (if your dsl modem is  also a router)

Second - you will have to turn off DHCP on the modem (again if your dsl modem is a router/modem)

Then you have to make sure your pinging the same subnet that your LAN is on.  Cause in your post I see your modem is 192.168.1.1 and your router is 192.168.5.1 <------ TWO DIFFERENT SUBNETS    1.1 & 5.1,  What IP were you trying to ping a public IP or a private IP ?  Or a dns name?

Regards,
ScarEye

Thanks for the reply!  Let me clarify.  The DSL modem gives the router a WAN address of 192.168.1.1.  I set the router LAN address to be 192.168.5.1, and it gives out 192.168.5.x addresses to the connected PCs.  I get a destination host unreachable message on my pc when I ping any address including 192.168.1.1 and 192.168.5.1.

Why would NAT mode on the DSL modem not work?  The router should route my packets out to the DSL modem, and the DSL modem, in turn, should route them out to the Internet?  What am I missing?

Also, web browsing DOES work, it's just ping that doesn't .

Thanks,
Igor

I just realized that it's nodogsplash that is stopping ping - if I shut it down everything works.  So, I just need to figure out how to connect to my VPN with nodogsplash running.  I probably need to open up some more ports.

Thanks!
Igor

Yes, nodogsplash with the default shipped .conf file is quite restrictive, opening only SSH, DNS, HTTP, and HTTPS to authenticated users.  If you want also to open ping,  put

FirewallRule allow icmp

in the authenticated-users FirewallRuleset.

--Paul