From owner-freebsd-ipfw@FreeBSD.ORG Sat Oct 4 10:38:10 2003 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 940AC16A4BF for ; Sat, 4 Oct 2003 10:38:10 -0700 (PDT) Received: from netlx014.civ.utwente.nl (netlx014.civ.utwente.nl [130.89.1.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 288E043FF9 for ; Sat, 4 Oct 2003 10:38:09 -0700 (PDT) (envelope-from r.s.a.vandomburg@student.utwente.nl) Received: from gog (gog.student.utwente.nl [130.89.165.107]) by netlx014.civ.utwente.nl (8.11.7/HKD) with SMTP id h94Hbx031180; Sat, 4 Oct 2003 19:38:01 +0200 Message-ID: <007d01c38a9e$73883cc0$6ba55982@gog> From: "Roderick van Domburg" To: "Marcin Gryszkalis" References: <006b01c38a90$dea3b420$6ba55982@gog> <3F7EFDFA.4060703@fork.pl> Date: Sat, 4 Oct 2003 19:39:21 +0200 Organization: University of Twente MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean cc: freebsd-ipfw@freebsd.org Subject: Re: When to use setup keyword? X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2003 17:38:10 -0000 > > All services run just fine, but I was thinking that excluding 'setup' here > > and there would make for a cleaner solution? For example, I don't think that > > HTTP (even 1.1) requires the setup keyword does it? > > Please refer to ipfw manual *and* some TCP/IP reference. > ipfw is TCP/IP level firewall, while HTTP is application level > protocol (higher). ipfw knows nothing about HTTP. I know, but HTTP/1.1 does allow for ``threaded sessions'', so to speak. What I don't know without glancing at any RFC's is whether HTTP/1.1 clients open multiple sockets on port 80 or several sockets in the dynamic range. Hence my question: which services require the setup keyword and which don't? Regards, Roderick