simple problem but i cant seem to get Linux Slackware to run behind my router, it has a domain name failure when trying to go to google, yet can ping every pc on my network, and the router, but as soon as i ping google it says the network is unreachable, could someone help me on this? thanks

edit /etc/resolv.conf

put in
nameserver 123.123.123.123

(get your nameservers from the status page on your router)

Does it resolve www.google.com to an IP? Sounds like it does. As you're getting ICMP unreachable responses, double check that your default gateway is pointing to the IP of the linksys...

Usually I can just put the IP of my router as nameserver and it apparently forwards the DNS requests to the nameservers it gets from DHCP.

# cat resolv.conf
nameserver 192.168.0.1

This is with a D-Link DI-624. Maybe Linksys is diff.

-E

well, when i ping it does say network unreachable, when i acess it by konqeur *sp?* it says could not resolve host *or something similar, i dont have the machine running here for me to look at* ill try cat on that file and see what comes up. if you have anymore information please feel free to tell me. im kinda new to linux but have been real interested in it *if it werent for the lack of gaming support, id use it as my main OS ^^*

well, secesh already pointed you to the right resolution:

edit add to the /etc/resolv.conf
nameserver ip_address_of_your_ISP_provider

next ping your ISP's name. It should resolve ip address.
So unless you do that, there is no point to look for something else.

and no this is wrong to put ip address of your router there.
It will slow down network connection

unfortunately the nameserver on resolv.conf is correct Oo.. so i am still stuck..

so let's back up, then...
let's see the results for:
1) ping -c 3 google.com
2) ping -c 3 216.239.37.99

any ping to googles dns or ip resolves:
network unreachable.

wereas pinging anything on the lan is totally clear

/sbin/route

/sbin/route? turn it off? Oo?

edit> i tried turning the execute option for it off, then back on, still the same results. i cant mod the file cause its in hex Oo..
i also tried adding the network on the routing table, with no sucess...

I have a linksys router also, and ran into the same frustrating problem on a trimmed down Debian install. Theoretically, it should have worked--I had tried to set DNS to either the router's address or to use DHCP (which would have made it go through the router). Either SHOULD have worked, but did not. This was very frustrating because I had other machines were set up to resolve DNS in both ways and they all worked!

Things were really weird because it was able to resolve SOME domains, some of the time. In particular the ftp site I was installing Debian from worked, although the apt-get repositories were only sometimes resolved.

My solution was very heavyhanded--I used apt-get to install a DNS server (apt-get not only installs the daemon software, but also sets it up to run). Mysteriously, this solved ALL of my problems. After some initial sluggishness with taking many seconds to resolve domains, it got zippy with domain name resolution.

I believe that the linksys router is somewhat glitchy, and there must be some particular circumstances under which it simply gets overwhelmed. I was using bittorrent to download the GamesKnoppix iso when the problems started happening, so perhaps the sheer number of open connections made the router unable to happily take on the new computer's NIC.

Installing the DNS server software reduced the number of DNS resolution requests to the linksys router, and also bypassed the strict necessity for the linksys router to perform DNS by going straight to the default nameservers after a timeout (accounting for the initial sluggishness).

run /sbin/route, and let us see the result

something like:
--in particular, i'm interested to see if you have a default gateway

k, i cant code so i have to type this:


localnet * 255.255.255.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo

but no default gateway?

use:
/sbin/route add default gw 192.168.1.1

where the IP above is, in fact, your default gateway...