From owner-freebsd-questions@FreeBSD.ORG Sat Mar 11 11:03:08 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DE8D16A41F for ; Sat, 11 Mar 2006 11:03:08 +0000 (GMT) (envelope-from pietro.cerutti@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E24543D67 for ; Sat, 11 Mar 2006 11:03:04 +0000 (GMT) (envelope-from pietro.cerutti@gmail.com) Received: by nproxy.gmail.com with SMTP id l36so646529nfa for ; Sat, 11 Mar 2006 03:03:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=mS1N2PTaJIf87curyc+xMk3rSD+2kZh7xN4tMxCegeSJHC8xO8yhKZoAIkMlQE1q8iGU/CQQwZ+CVPEp++6S0/gX6f1vY0Gn++r4JtIMZDIyrPLo2OkVXcuwBoS8LIAdbsEN9/lDs4VqwrSSNgpSfAfwYstiZMkevbMeatKlGSE= Received: by 10.49.39.4 with SMTP id r4mr758245nfj; Sat, 11 Mar 2006 03:03:04 -0800 (PST) Received: by 10.49.30.6 with HTTP; Sat, 11 Mar 2006 03:03:04 -0800 (PST) Message-ID: Date: Sat, 11 Mar 2006 12:03:04 +0100 From: "Pietro Cerutti" To: freebsd MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Arplookup strange messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2006 11:03:08 -0000 Hi list, today in the daily security report (periodic) of a i386 machine there is this message repeated about 30 times: +arplookup 0.0.0.0 failed: host is not on local network The machine is the router (ipnat) and firewall (ipfilter) for a small home network. It runs postfix, sshd and nfsd. Since I'm away from home now, I can't sit in front of it and check what's wrong. Furthermore, it seams that the machine is not accepting ssh logins anymore, after those strange messages. Any ideas about the cause of it? Thanks, -- Pietro Cerutti Non lasciar calpestare i TUOI diritti! Don't let 'em take YOUR rights! NO al Trusted Computing! Say NO to Trusted Computing! www.no1984.org www.againsttcpa.com