From owner-freebsd-questions Wed Jun 13 11:25:56 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fac13.ds.psu.edu (fac13.ds.psu.edu [146.186.61.98]) by hub.freebsd.org (Postfix) with ESMTP id D2CC037B401 for ; Wed, 13 Jun 2001 11:25:51 -0700 (PDT) (envelope-from hawk@fac13.ds.psu.edu) Received: from fac13.ds.psu.edu (localhost [127.0.0.1]) by fac13.ds.psu.edu (8.11.3/8.11.3) with ESMTP id f5DHVAZ67314 for ; Wed, 13 Jun 2001 13:31:10 -0400 (EDT) (envelope-from hawk@fac13.ds.psu.edu) Message-Id: <200106131731.f5DHVAZ67314@fac13.ds.psu.edu> To: freebsd-questions@FreeBSD.ORG Subject: natd "host is down" messages From: "Richard E. Hawkins" Date: Wed, 13 Jun 2001 13:31:10 -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I installed natd so that vmware machines could access the network and my own machine. When I'm notusing it (and haven't used it since boot), I get gaggles of console messages that Jun 13 13:03:12 fac13 natd[171]: failed to write packet back (Host is down) Jun 13 13:03:30 fac13 last message repeated 12 times Jun 13 13:05:40 fac13 last message repeated 4 times Jun 13 13:09:38 fac13 last message repeated 7 times Jun 13 13:26:01 fac13 last message repeated 25 times As I understand things (which is probably wrong), nothing should be talking to natd anyway. My machine is up, its gateway is up, and the virtual machine on the 192. network is not up--which means that it shouldn't be sending anything for natd to worry about. hawk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message