From owner-freebsd-questions@FreeBSD.ORG Wed Dec 7 18:03:55 2005 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 B1D7F16A420 for ; Wed, 7 Dec 2005 18:03:55 +0000 (GMT) (envelope-from matt.singerman@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id E35C743D66 for ; Wed, 7 Dec 2005 18:03:47 +0000 (GMT) (envelope-from matt.singerman@gmail.com) Received: by zproxy.gmail.com with SMTP id z6so434370nzd for ; Wed, 07 Dec 2005 10:03:46 -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=gmehOqLENSs66i1k/1k831IkijwE1DXL9RlV7vZI3Ah3sW8YZwZyzSYZdats8THqJWHcJQfZTXmd1Rch7oQywnmWulg+eM1tcP3+MjFzjYqN8jkkwgNrejhblYfTJoV0raolQQDxgSuObd/0Mmp5NvLzpbOFrXAPTkknGuhfHx4= Received: by 10.64.249.4 with SMTP id w4mr2026444qbh; Wed, 07 Dec 2005 10:03:46 -0800 (PST) Received: by 10.65.61.19 with HTTP; Wed, 7 Dec 2005 10:03:46 -0800 (PST) Message-ID: <54682af50512071003u64f55fdcxfa35c238b0375b2f@mail.gmail.com> Date: Wed, 7 Dec 2005 13:03:46 -0500 From: Matt Singerman To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: odd problem with firewall server 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: Wed, 07 Dec 2005 18:03:55 -0000 Hi all, This probably isn't a FreeBSD-specific problem, but it's vexing nonetheless= . So we have our servers accessing the outside world through their own firewall on a FreeBSD machine. Nothing too fancy, just routing traffic and shutting off unused ports. However, this morning the ethernet jack that the firewall server's world-accessible ethernet port (dc1) was plugged into. The solution: plug it into another jack :) This amazingly complex solution worked, except that I can now no longer ssh or ping the machine. Any ideas as to what may have caused this? Thanks, Matt