From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usb and dns suddenly not working
Date: Wed, 25 Apr 2007 19:12:04 -0400 [thread overview]
Message-ID: <20070425231201.8E4BC1E8C48@holo.morphisms.net> (raw)
In-Reply-To: <7871fcf50704251551i10a7b58dv48dd0fb0a478b972@mail.gmail.com>
> The applicable line in /rc/term/termrc is
> ip/ipconfig -g 199.98.16.1 ether /net/ether0 199.98.17.238
> 255.255.248.0 > /dev/null >[2=1]
>
> It looks like something's misconfigured -- but this configuration
> *used* to work!
you're not totally lost.
you need to check whether you have any
connectivity at all.
ip/ping 199.98.16.1 # your gateway
ip/ping 199.98.16.9 # your dns server
ip/ping 18.26.4.9 # somewhere on the internet
then see if you can resolve something
using your dns server:
ndb/dnsdebug @199.98.16.9 www.google.com
or someone else's dns server:
ndb/dnsdebug @18.26.4.9 www.google.com
also, this part of your mail looks wrong:
term% ndb/dnsdebug
> www.google.com
!dns: dns failure
dnsdebug doesn't print lines like !dns: dns failure.
only dnsquery does. are you sure you didn't
run dnsquery twice?
dnsdebug prints things like the output below.
even if nothing is working you should get the
'sending to' line.
(the fact that you are typing into the interactive
prompt instead of specifying it on the command
line like in my example is not relevant.)
russ
% ndb/dnsdebug @18.26.4.9 plan9.bell-labs.com
20654.1: sending to 18.26.4.9/18.26.4.9 plan9.bell-labs.com ip
20654: rcvd OK from 18.26.4.9 ( recurse can_recurse)
Q: plan9.bell-labs.com ip
Ans: plan9.bell-labs.com 12 hr ip 204.178.31.2
Auth: bell-labs.com 11 hr 1 min 2 s ns dirty.research.bell-labs.com
bell-labs.com 11 hr 1 min 2 s ns crufty.research.bell-labs.com
bell-labs.com 11 hr 1 min 2 s ns ns1.research.bell-labs.com
bell-labs.com 11 hr 1 min 2 s ns ns2.research.bell-labs.com
Hint: ns1.research.bell-labs.com 4 hr 27 min 28 ip 204.178.16.6
ns2.research.bell-labs.com 1 hr 16 min 11 ip 204.178.16.49
dirty.research.bell-labs.com 1 hr 16 min 11 ip 204.178.16.6
crufty.research.bell-labs.com 11 hr 1 min 2 s ip 204.178.16.49
----------------------------
answer plan9.bell-labs.com 12 hr ip 204.178.31.2
----------------------------
%
next prev parent reply other threads:[~2007-04-25 23:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 21:20 Joel C. Salomon
2007-04-25 21:25 ` erik quanstrom
2007-04-25 21:31 ` Joel C. Salomon
2007-04-25 22:05 ` Joel C. Salomon
2007-04-25 22:07 ` erik quanstrom
2007-04-25 22:29 ` Joel C. Salomon
2007-04-25 22:37 ` geoff
2007-04-25 23:06 ` Joel C. Salomon
2007-04-25 22:32 ` Steve Simon
2007-04-25 22:51 ` Joel C. Salomon
2007-04-25 22:59 ` geoff
2007-04-25 23:11 ` Joel C. Salomon
2007-04-25 23:14 ` erik quanstrom
2007-04-25 23:20 ` Uriel
2007-04-25 23:22 ` Skip Tavakkolian
2007-04-25 23:52 ` Joel C. Salomon
2007-04-25 23:27 ` Joel C. Salomon
2007-04-25 23:12 ` Russ Cox [this message]
2007-04-25 23:25 ` Joel C. Salomon
2007-05-21 8:54 ` [9fans] " Gabriel Diaz
2007-05-21 11:32 ` erik quanstrom
2007-05-21 11:45 ` Gabriel Diaz
2007-05-21 11:52 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070425231201.8E4BC1E8C48@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).