:: Pann McCuaig writes: >> telnet localhost 80 >> >> This is what I get here: >> >> telnet: could not resolve localhost/80: Temporary failure in name resolution
> Sounds like it may be a name resolution problem. Here's my experience: > [EMAIL PROTECTED]:~$ telnet localhost 80 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > ^] telnet> quit > Connection closed. > [EMAIL PROTECTED]:~$ cat /etc/hosts > 127.0.0.1 localhost > 192.168.1.5 potato.ourmanpann.com potato > 192.168.1.1 firewall.ourmanpann.com firewall > 192.168.1.2 rescue.ourmanpann.com rescue > 192.168.1.3 win95.ourmanpann.com win95 > 192.168.1.4 openbsd.ourmanpann.com openbsd > And I'm not running bind on this box, FWIW. That's what I get when I'm connected. It's something with the ip-up and ip-down scripts, I guess... Here's my /etc/hosts: socrates provas$ cat /etc/hosts 127.0.0.1 localhost socrates loghost # The following lines are desirable for IPv6 capable hosts # (added automatically by netbase upgrade) ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts With this, w3m doesn't find localhost... Because telnet localhost 80 doesn't work. Are you running potato or woody? TThis is woody, here. J. -- Jeronimo Pellegrini Institute of Computing - Unicamp - Brazil http://www.ic.unicamp.br/~jeronimo mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
