Subject: Network problems; no name lookups, no real connection?
To: None <tech-net@netbsd.org>
From: Jan Danielsson <jan.danielsson@gmail.com>
List: tech-net
Date: 02/02/2006 15:03:17
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigEB0871A6A6F97B3827158A1E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello all,

   On a system I administrate remotely, I can no longer look up host
names. Actually, the problems seem to be bigger than that.

   First of all, there are two systems, both running NetBSD. The once
causing my grief, I'll call A, and the other one, which is physically
located 2 cm from A, I'll call B.

   A and B are connected to the internet via a cablemodem + DHCP. They
are also connected via an internal network (which I used to be able to
reach A (through B).. It has changed it's public IP, but due to the
problems I'm about to describe, that announcement never reached me).

   This is on system A:

# ping www.uu.se
ping: Cannot resolve "www.uu.se" (Host name lookup failure)

   On system B:

$ ping www.uu.se
PING www.uu.se (130.238.7.10): 56 data bytes
64 bytes from 130.238.7.10: icmp_seq=3D0 ttl=3D245 time=3D52.342 ms
64 bytes from 130.238.7.10: icmp_seq=3D1 ttl=3D245 time=3D44.546 ms
64 bytes from 130.238.7.10: icmp_seq=3D2 ttl=3D245 time=3D49.839 ms
^C

   Now back to system A again; let's assume that it's only the host name
lookup that is failing:

# ping -n 130.238.7.10
PING 130.238.7.10 (130.238.7.10): 56 data bytes
^C

   ... it just sits there doing nothing, until I break. So, obviously
we're not getting very far. Let's review the routing table on A:

# route show
Routing tables

Internet:
Destination       Gateway            Flags
default           85.228.128.1       UG
85.228.128.0/18   link#1             U
85.228.128.1      00:b0:c2:3c:7c:00  UH
85.228.147.21     127.0.0.1          UGH
85.228.172.105    127.0.0.1          UGH
loopback          127.0.0.1          UGR
localhost         127.0.0.1          UH
192.168.0.0/24    link#2             U

   And try to ping A's gateway:

# ping 85.228.128.1
PING 85.228.128.1 (85.228.128.1): 56 data bytes
64 bytes from 85.228.128.1: icmp_seq=3D0 ttl=3D255 time=3D33.267 ms
64 bytes from 85.228.128.1: icmp_seq=3D1 ttl=3D255 time=3D32.393 ms
64 bytes from 85.228.128.1: icmp_seq=3D2 ttl=3D255 time=3D33.481 ms
^C

   Works.

   I also checked the netmasks on the external interfaces for systems A
and B, and they match (they are assigned by the dhcp).

   As I stated earlier, A and B and physically next to each other, and
they share the same cable modem, the same dhcp, same isp, etc. I tried
disabling the firewall, but that didn't change anything.

   I know absolutely nothing about networking, but I feel like blaming
the isp for something. Anyone know what could be wrong? Any suggestions
what I should try?


--=20
Kind Regards,
Jan Danielsson
Te audire non possum. Musa sapientum fixa est in aure.


--------------enigEB0871A6A6F97B3827158A1E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFD4hEp8wBCTJQ8HEIRAkO2AKCJXhq/LCp8yRQJjlIEVrlhgcEAfwCfTmP8
pJ6wJMCLtatsaVsKg2bb/MQ=
=QnaS
-----END PGP SIGNATURE-----

--------------enigEB0871A6A6F97B3827158A1E--