From owner-freebsd-questions Fri Aug 10 8:21:43 2001 Delivered-To: freebsd-questions@freebsd.org Received: from pineypl.COM (dsl-216-227-86-197.telocity.com [216.227.86.197]) by hub.freebsd.org (Postfix) with ESMTP id 3CC8737B406 for ; Fri, 10 Aug 2001 08:21:40 -0700 (PDT) (envelope-from bob@pineypl.COM) Received: (from bob@localhost) by pineypl.COM (8.11.3/8.11.3) id f7AFJh849775 for questions@freebsd.org; Fri, 10 Aug 2001 11:19:43 -0400 (EDT) (envelope-from bob) Date: Fri, 10 Aug 2001 11:19:38 -0400 From: Bob Collins To: questions@freebsd.org Subject: RE: natd[135]:failed to write packet back Message-ID: <20010810111938.A49752@kludge.pineypl> Mail-Followup-To: questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 too have been having a lot of weirdness in my log files. In particular I have been seeing many NATD failures on port 240. I have reviewed the security, httpd-access.log, httpd-error.log, and ipfw logs to see a correlation of default.ida requests in the apache logs to the times in the security logs. I figure this is more fallout from the Code Red II. On a side note, there seems to be so much activity with this CRII on Telocity, I have been experiencing more network latency lately. Of course, Telocity allows a static IP for home users, which I guess many are using some level of IIS or peer web services, which might also be suffering from the CRII. -Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message