Re: Networking problem
- From: Howard Eisenberger <howarde@xxxxxxx>
- Date: Wed, 8 Apr 2009 08:08:49 -0400
On 2009-04-08, Moe Trin <ibuprofin@xxxxxxxxxxxxxxxxxxxxxx> wrote:
On Tue, 7 Apr 2009, in the Usenet newsgroup comp.os.linux.setup, in article
<7v9ta6-nke.ln1@xxxxxxxxxxxxxxxxx>, Howard Eisenberger wrote:
Not really an answer, but I use Debian and have a test installation
on another drive on this box which is exhibiting the same symtoms.
It was working fine until I installed, updated and uninstalled a
bunch of browsers to try and solve a problem I was having with
iceweasel/firefox.
Have you tried the packet sniffer?
All I get is something like this, even on the working partition.
This is on a sparc machine, so maybe it doesn't work.
# tcpdump -vvv -n -s 512 port 53
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 512 bytes
0 packets captured
10 packets received by filter
0 packets dropped by kernel
Suddenly even lynx stopped working, at which point I abandoned the
whole thing, especially since the original browser problem had in
the meantime been resolved. I figured I would install from scratch
the next time.
Hmmm, lynx has been pretty bullet resistant for me.
DNS failure with wget as well.
I pretty well forgot about it until I read this discussion. I just
re-booted into the other drive to try it again. "host" and "nslookup"
work,
STOP RIGHT THERE!
[compton ~]$ whatis dig dnsquery host nslookup
dig (1) - send domain name query packets to name servers
dnsquery (1) - query domain name servers using resolver
host (1) - look up host names using domain server
nslookup (8) - query Internet name servers interactively
[compton ~]$
The magic thing about those four is that they query DNS servers to
resolve hostname <-> address questions only. They don't look at the
/etc/host.conf and/or /etc/nsswitch.conf file, nor do the look at NIS
or /etc/hosts. That they work says the name servers are alive and
well. Says nothing for any application on your system (and that
includes 'avahi' if you have that security hole installed), and any
errors in the /etc/host.conf and/or /etc/nsswitch.conf files. Look at
the 'host' line in the later:
[compton ~]$ grep host /etc/nsswitch.conf
hosts: files nis dns
[compton ~]$
hosts: files dns
on both
If you have any mention of 'mdns' you've got that libnss_mdns crap
associated with avahi.
I have seen avahi in dmesg, but not here.
but with lynx, I get a 404 error from the server even using the IP
address.
Is the 404 actually coming from the remote web server, or from some
proxy? The '404' _NORMALLY_ means you reached the server, but
something in your request caused it unhappyness. I'd expect lynx
to report "Alert: Unable to connect to remote host". I'd normally
suggest using a packet sniffer to see what you are requesting of
the web server.
I get a 404 error when I give lynx the IP address and the "Unable
to connect" when I give it a host, which it can't resolve.
Unlike the OP, I have Debian running here on at least a half a
dozen machines, both sparc and x86, without this "network" problem,
which I see now may not even be the same as his. It is only the
test partition on this box that I somehow managed to mess up.
Regards,
Howard E.
.
- Follow-Ups:
- Re: Networking problem
- From: Moe Trin
- Re: Networking problem
- References:
- Networking problem
- From: philo
- Re: Networking problem
- From: Moe Trin
- Re: Networking problem
- From: philo
- Re: Networking problem
- From: Moe Trin
- Re: Networking problem
- From: philo
- Re: Networking problem
- From: Moe Trin
- Re: Networking problem
- From: Hal Murray
- Re: Networking problem
- From: philo
- Re: Networking problem
- From: Moe Trin
- Re: Networking problem
- From: philo
- Re: Networking problem
- From: Howard Eisenberger
- Re: Networking problem
- From: Moe Trin
- Networking problem
- Prev by Date: Re: Networking problem (add'l info)
- Next by Date: Re: CVS server installation
- Previous by thread: Re: Networking problem
- Next by thread: Re: Networking problem
- Index(es):
Relevant Pages
|