9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] VMware: Can't use DNS because cs fails?
Date: Mon, 24 Jun 2013 10:39:17 -0700	[thread overview]
Message-ID: <98EDDBAD-FADF-4594-B1AF-98506DD191A7@bitblocks.com> (raw)
In-Reply-To: <47321d0ab055389a9d08b8a0d2440ca6@lyons.quanstro.net>

On Jun 24, 2013, at 6:07 AM, erik quanstrom <quanstro@quanstro.net> wrote:

>> Looking in /net/ndb, my network looks like this:
>> 
>>    ip=127.0.0.1 ipmask=/104 ipgw=::
>>        sys=gnot
>>        sys=gnot
>>        dom=gnot.localdomain
>>        dns=192.168.220.2
>> 
>> I don't know if that's correct.
> 
> i think this is the issue.  if the ip network is 127.0.0.1/104,
> then the gateway (:: = 0:0:0:0:0:0:0:0) is not on the
> same network.  so 192.168.220.2 can't be reached.

/104 mask for IPv4 doesn't make sense. Can be at most /32. 

> by the way, for reasons that escape me, 127.0.0.1 has
> a mask of /8.  not sure why the local host needs 16777214
> ip addresses.

See rfc1122 - the host requirements rfc - it documented existing practices (as of 1989). Probably because it was quicker to look up in the days of class based addressing, when 32 bit addressing was considered plentiful. 127.x.x.x is a class A address.



  reply	other threads:[~2013-06-24 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  9:09 Ilmari Vacklin
2013-06-24 13:07 ` erik quanstrom
2013-06-24 17:39   ` Bakul Shah [this message]
2013-06-24 18:18   ` [9fans] VMwaCan't " Ilmari Vacklin
2013-06-24 19:46     ` 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=98EDDBAD-FADF-4594-B1AF-98506DD191A7@bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /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).