[TriLUG] OpenBSD 3.1 & a Sun Netra T1 105 (longish)
Jaimie Livingston
Jaimie.Livingston at haht.com
Sat Sep 28 21:58:36 EDT 2002
Thanks, Jon... I caught and corrected that after I sent the message, but
that didn't fix the problem. The second system has had the the correct
gateway info thruout, and it still has the same problem. I suppose the error
crept in as I was trying different settings...
Here's an nslookup that may help:
# nslookup www.haht.com
*** Can't find server name for address 216.54.164.2: Timed out
*** Can't find server name for address 216.54.164.5: Timed out
Server: cajun2.srvr.haht.com
Address: 10.1.1.20
Non-authoritative answer:
Name: www.haht.com
Address: 216.54.164.40
Here's the routes on the system. Maybe something jumps out...
# route show
Routing tables
Internet:
Destination Gateway Flags
default 216.54.164.1 UG
10.0.0.0 link#2 U
ipt-haht.srvr.ha 0:10:4b:72:d4:f6 UH
cajun2.srvr.haht 0:20:af:2c:e8:9a UH
10.1.3.104 0:10:4b:72:d4:f6 UH
10.2.1.200 0:2:b3:a:35:1b UH
127.0.0.0 localhost UG
localhost.haht.c localhost UH
216.54.164.0 link#1 U
216.54.164.1 link#1 UH
rdudns02.haht.co localhost UGH
BASE-ADDRESS.MCA localhost U
Internet6:
Destination Gateway Flags
default localhost.haht.com UG
default localhost.haht.com UG
localhost.haht.c localhost.haht.com UH
::127.0.0.0 localhost.haht.com UG
::224.0.0.0 localhost.haht.com UG
::255.0.0.0 localhost.haht.com UG
::ffff:0.0.0.0 localhost.haht.com UG
2002:: localhost.haht.com UG
2002:7f00:: localhost.haht.com UG
2002:e000:: localhost.haht.com UG
2002:ff00:: localhost.haht.com UG
fe80:: localhost.haht.com UG
fe80::%hme0 link#1 U
fe80::%hme1 link#2 U
fe80::%lo0 fe80::1%lo0 U
fec0:: localhost.haht.com UG
ff01:: localhost.haht.com U
ff02::%hme0 link#1 U
ff02::%hme1 link#2 U
ff02::%lo0 fe80::1%lo0 U
Sigh....
Jaimie
-----Original Message-----
From: Jon Carnes [mailto:jonc at nc.rr.com]
Sent: Saturday, September 28, 2002 8:54 AM
To: trilug at trilug.org
Subject: Re: [TriLUG] OpenBSD 3.1 & a Sun Netra T1 105 (longish)
Don't know if you're going to be happy to hear this or not, but the problem
is a typo in your gateway:
> $ cat mygate
> 216.54.165.1
I believe you want 216.54.164.1 :-)
Take care - Jon
BTW: all those symptoms point to a bad route - so that should be your first
suspect... should it happen again!
_______________________________________________
TriLUG mailing list
http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ:
http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.trilug.org/pipermail/trilug/attachments/20020928/bcf9818d/attachment.html>
More information about the TriLUG
mailing list