From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7fe2e5b3cad2e80df8f549fcfb3767ba@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: ip resolving
From: "Russ Cox" <rsc@plan9.bell-labs.com>
In-Reply-To: <20030220101316.14994.qmail@mail.prosyst.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu, 20 Feb 2003 09:24:58 -0500
Topicbox-Message-UUID: 6b0abbe6-eacb-11e9-9e20-41e7f4b1d025

> No, 132.187.1.1 is not a router I'm using it as DNS server on my linux box.
> I changed it manually of course. But may be you are right about blocking
> from vmware side. I have to check this. BTW now I have a problem with the
> DHCP server. Nothing is changed in configuration only rebooted and now I
> have no response from the DHCP server.

reboot again.  there appears to be a bug in the
new ip drop-if-no-default-route code.

russ