Hi, On Sat, 4 Nov 2006 07:24:51 -0500 (GMT-05:00) Jeff Cranmer <[EMAIL PROTECTED]> wrote:
> For the /etc/resolv.conf file, I have: > search belkin > nameserver 192.168.2.1 > nameserver 207.69.188.185 > nameserver 207.69.188.186 > nameserver 207.69.188.187 Given that the router runs a local DNS (caching) server, that should be alright. > route -n returns > Kernel IP routing table > Destination Gateway Genmask Flags > Metric Ref Use Iface > 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 looks good. > Comparing this with the equivalent working connection via my Mandriva > Linux boot-up, /etc/resolv.conf is the same, but route -n returns > [...] > The main difference is that the metric column is all 0 on my > non-working install, and I'm missing the 169.254.0.0 row from route -n That doesn't matter. That 169.254.0.0 subnet is the Windows autoconfiguration range (when there's no DHCP server, but IP address gathering is set to "automatic") and the metric doesn't matter because you don't have concurrent routes. > I'm not using genkernel. Is it possible that a kernel > misconfiguration is responsible for the problems I'm having? Unlikely, because in that case DHCP wouldn't work at all. Maybe the Belkin is blocking your pings? Maybe the Belkin is misconfigured and does not have Internet access? Maybe some firewall, either on the Belkin or on your Gentoo machine (you can check by issuing "iptables -vnL")? You should also try to monitor traffic with tcpdump when issuing those test pings. BTW, you cannot ping "http://www.google.de"; since that isn't a domain name but a URL. But you probably *did* ping the domain name, didn't you? -hwh -- gentoo-user@gentoo.org mailing list
