From owner-freebsd-questions@FreeBSD.ORG Wed Sep 21 21:02:00 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 C59F616A41F for ; Wed, 21 Sep 2005 21:02:00 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2396243D5F for ; Wed, 21 Sep 2005 21:01:59 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 31506 invoked from network); 21 Sep 2005 21:01:59 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Sep 2005 21:01:59 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 4317941; Wed, 21 Sep 2005 17:01:57 -0400 (EDT) Sender: lowell@be-well.ilk.org To: ann kok , freebsd-questions@freebsd.org References: <20050921202013.15670.qmail@web53305.mail.yahoo.com> From: Lowell Gilbert Date: 21 Sep 2005 17:01:56 -0400 In-Reply-To: Message-ID: <44aci6b0e3.fsf@be-well.ilk.org> Lines: 26 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: pls help for ipfw 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, 21 Sep 2005 21:02:00 -0000 Charles Swiger writes: > On Sep 21, 2005, at 4:20 PM, ann kok wrote: > > my rules: > > > > ipfw add allow udp from any to tftpserverip > > ipfw add allow udp from tftpserverip to any > > > > In the freebsd box, I can access tftp server but > > internal users is hanging in the "get" state > > TFTP may also use TCP: > > % grep tftp /etc/services > tftp 69/udp # Trivial File Transfer > tftp 69/tcp # Trivial File Transfer Except that it doesn't. The port is reserved to avoid confusion, but the TFTP protocol doesn't run on TCP. NAT is probably hanging things up. I think that all that's needed is to "add-state" on the outgoing TFTP rule. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/