From owner-freebsd-security Thu May 18 6:43:30 2000 Delivered-To: freebsd-security@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id 2CD6E37B69C for ; Thu, 18 May 2000 06:43:26 -0700 (PDT) (envelope-from fpscha@ns1.via-net-works.net.ar) Received: (from fpscha@localhost) by ns1.via-net-works.net.ar (8.9.3/8.9.3) id KAA22457; Thu, 18 May 2000 10:35:46 -0300 (GMT) From: Fernando Schapachnik Message-Id: <200005181335.KAA22457@ns1.via-net-works.net.ar> Subject: Re: ipfw: HTTP(S) is working but everything else doesn't... In-Reply-To: <1574492519.20000518151205@buz.ch> from Gabriel Ambuehl at "May 18, 0 03:12:05 pm" To: gabriel_ambuehl@buz.ch (Gabriel Ambuehl) Date: Thu, 18 May 2000 10:35:46 -0300 (GMT) Cc: freebsd-security@FreeBSD.ORG Reply-To: Fernando Schapachnik X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org En un mensaje anterior, Gabriel Ambuehl escribió: > my ipfw is driving me nuts. I want to allow SMTP (both incoming and > outgoing), POP3, HTTP, HTTPS and DNS (well, FTP should work as well > but that one has got it's own problems because of that FTP-data thingy) > for the firewall box itself and all boxes which use it as gateway [1]. You can try tcpdumping the interfaces to see what you get. Also, you can try adding a deny log rule at the bottom to see what gets dropped by the firewall. Good luck! Fernando P. Schapachnik Administración de la red VIA NET.WORKS ARGENTINA S.A. fernando@via-net-works.net.ar (54-11) 4323-3333 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message