From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] networking troubles
Date: Sat, 4 May 2002 01:52:18 -0400 [thread overview]
Message-ID: <72cdc41e787fc8f1d016b52a33f8f481@plan9.bell-labs.com> (raw)
> * How does one test whether the network connection is up? ip/ping?
netstat -i
is a good start.
> * Does 'ip/ipconfig ether /net/ether0 unbind' set the card to a
> state where it can be reassigned with 'ip/ipconfig -g ga.te.way.addr
> ether /net/ether0 ip.a.d.dr net.m.a.sk' or is there more to do?
i think so. to be sure, you can do
echo -n unbind >/net/ipifc/0/ctl
> * Must the first server on the network (which will be the dhcp and
> auth server) set it's ip in /rc/bin/termrc (or cpurc) or can a well
> formed /ndb/local assign it?
i think you have to set it in termrc or cpurc.
for example, our standalone auth/dhcp server has
two addresses and uses:
# start network
if(test -e /net/ipifc/clone){
ip/ipconfig -g 135.104.9.1 ether /net/ether0 135.104.9.7 255.255.255.0
ip/ipconfig ether /net/ether0 add 135.104.9.115 255.255.255.0
}
> * If after assigning the ip in /rc/bin/termrc and not getting a
> "cant look up my ip" error from /ndb/dns, one can't ip/ping anything
> what are the possible problems?
perhaps your routing table is wrong.
cat /net/iproute
try pinging yourself. that should work
as long as the ip interface is set up,
independent of routing.
russ
next reply other threads:[~2002-05-04 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 5:52 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 19:09 Russ Cox
2002-05-04 18:52 Michael Warnock
2002-05-03 21:20 Michael Warnock
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=72cdc41e787fc8f1d016b52a33f8f481@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).