<br><br><div><span class="gmail_quote">On 27/12/06, <b class="gmail_sendername">Dave Briggs</b> <<a href="mailto:d@vebrig.gs">d@vebrig.gs</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
dave@dave-desktop:~$ wget <a href="http://slashdot.org">http://slashdot.org</a><br>--19:13:44-- <a href="http://slashdot.org/">http://slashdot.org/</a><br> => `index.html'<br>Resolving slashdot.org... <a href="http://1.0.0.0">
1.0.0.0</a><br>Connecting to slashdot.org|1.0.0.0|:80...<br><br>[endlessly]<br><br>Gah! Any more ideas?<br><br>--<br>Dave Briggs<br></blockquote></div><br><br>Sorry if this has been covered already, but it looks like there might be some oddities about the way the Linksys ADSL2 modem forwards the ISP DNS details. (You did say that that was the modem you were using, I think?)
<br><br>Your output for the wget seems to be resolving slashdot to <a href="http://1.0.0.0">1.0.0.0</a><br><br>This guy <a href="http://linux.derkeiler.com/Mailing-Lists/Ubuntu/2006-05/msg01681.html">http://linux.derkeiler.com/Mailing-Lists/Ubuntu/2006-05/msg01681.html
</a> seems to be having a similar problem, and he mentions a workaround <a href="https://wiki.ubuntu.com/StaticDnsWithDhcp">(https://wiki.ubuntu.com/StaticDnsWithDhcp)</a> which appears to involve setting static DNS entries.
<br><br>I'd try the static dns entries if you haven't already.<br><br>Another interesting page mentioning a similar issue is <a href="http://blog.maniacmartin.com/2006/12/07/turning-a-modem-into-a-router/">http://blog.maniacmartin.com/2006/12/07/turning-a-modem-into-a-router/
</a><br><br>good luck,<br><br>Pat<br>