From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: ip resolving
Date: Wed, 19 Feb 2003 12:46:27 -0500 [thread overview]
Message-ID: <fd93504843c4bda78755a8bc910d95f5@plan9.bell-labs.com> (raw)
In-Reply-To: <20030219161025.30186.qmail@mail.prosyst.com>
> Now it works. Why I can't use 132.187.1.1 instead 192.168.79.2 ?
> I have nat what is the problem?
did you change it manually to 132.187.1.1?
i have a hard time believing vmware set it to that.
how did it get set to 132.187.1.1 in the first place?
first of all, 132.187.1.1 is likely to be a router
rather than a dns server. vmware may be blocking
dns packets except the ones to itself. i don't know.
just use the vmware ones.
next prev parent reply other threads:[~2003-02-19 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 15:31 [9fans] " Nikolay Paskov
2003-02-19 15:38 ` Russ Cox
2003-02-19 15:42 ` [9fans] " Nikolay Paskov
2003-02-19 15:49 ` Russ Cox
2003-02-19 16:10 ` Nikolay Paskov
2003-02-19 17:46 ` Russ Cox [this message]
2003-02-20 10:13 ` Nikolay Paskov
2003-02-20 14:24 ` Russ Cox
2003-02-20 14:35 ` Nikolay Paskov
2003-02-19 16:45 ` andrey mirtchovski
2003-02-19 15:44 [9fans] " Steve Simon
2003-02-19 15:50 ` [9fans] " Nikolay Paskov
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=fd93504843c4bda78755a8bc910d95f5@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).