From mboxrd@z Thu Jan  1 00:00:00 1970
References: <6df078c3-da6d-4267-b6b5-41d653d3201e@googlegroups.com>
	<47321d0ab055389a9d08b8a0d2440ca6@lyons.quanstro.net>
In-Reply-To: <47321d0ab055389a9d08b8a0d2440ca6@lyons.quanstro.net>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <98EDDBAD-FADF-4594-B1AF-98506DD191A7@bitblocks.com>
Content-Transfer-Encoding: quoted-printable
From: Bakul Shah <bakul@bitblocks.com>
Date: Mon, 24 Jun 2013 10:39:17 -0700
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] VMware: Can't use DNS because cs fails?
Topicbox-Message-UUID: 6813f742-ead8-11e9-9d60-3106f5b1d025

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

>> Looking in /net/ndb, my network looks like this:
>>=20
>>    ip=3D127.0.0.1 ipmask=3D/104 ipgw=3D::
>>        sys=3Dgnot
>>        sys=3Dgnot
>>        dom=3Dgnot.localdomain
>>        dns=3D192.168.220.2
>>=20
>> I don't know if that's correct.
>=20
> i think this is the issue.  if the ip network is 127.0.0.1/104,
> then the gateway (:: =3D 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.=20

> 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.