At 11:09 AM 3/6/2007, Chris Lale wrote:
Are you using the expert install ("expert" at the installer boot screen)?
AFAIR, there is then an option to supply nameservers manually. I had
to do this when I was using a particular ADSL modem/router-in-a-box
to connect to my ISP. The modem/router did not have an option to set
nameservers, so DHCP was detected OK but would not work during a
normal "install". Setting the nameservers in "expert" install solved
the problem. I did report this as a bug, but it was a couple of years ago.
Yes, I am using the expert install ("expert" on etch and "expert26"
on sarge), but that's not the problem. It gets the nameservers fine,
like I said: /etc/resolv.conf is fine. And when I do "route" to try
and figure out why it says "no route to host" it displays my
gateway's hostname. And "ifconfig" shows my eth device configured
correctly. It's just not getting anywhere.
There has got to be some weird combination of problems with the DHCP
client in Debian and my ISP, because like I said, it worked passing
through another box, it worked in woody that I used to use, and it
worked in two different versions of Slackware, all with absolutely
nothing of any kind except DHCP autoconfiguration.
Right now I'm using Slackware until I can figure this out. If there
are any files or details I can provide to help diagnose this, please
tell me, but other than my hardware or logs of some kind, it's
absolutely the vanilla installation and I'm not changing a single
thing. I appreciate your time.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
