From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] network cfg help, pls.
Date: Fri, 27 Sep 2002 09:58:02 -0400 [thread overview]
Message-ID: <e6ea221d4cc31ad44583927faea4633d@plan9.bell-labs.com> (raw)
Assuming you are not using DHCP,
sys=neXt
ip=147.231.139.4 ipgw=147.231.137.1 ipmask=255.255.0.0
dns=147.231.136.10
The only part of that entry that actually gets
used is your own IP address (to locate the appropriate
entry) and the DNS server IP address (to start dns).
What really matters is your ip/ipconfig line in termrc.
ip/ipconfig -g 147.231.137.1 ether /net/ether0 add 147.231.139.4 255.255.0.0
Russ
next reply other threads:[~2002-09-27 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 13:58 Russ Cox [this message]
2002-10-04 15:39 ` peter a. cejchan
-- strict thread matches above, loose matches on Subject: below --
2002-09-27 10:53 Peter A. Cejchan
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=e6ea221d4cc31ad44583927faea4633d@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).