From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 09:31:16 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 663F816A4CE for ; Tue, 24 Feb 2004 09:31:16 -0800 (PST) Received: from episec.com (episec.com [198.78.65.141]) by mx1.FreeBSD.org (Postfix) with SMTP id 31C4643D1D for ; Tue, 24 Feb 2004 09:31:16 -0800 (PST) (envelope-from edelkind-freebsd-hackers@episec.com) Received: (qmail 97086 invoked by uid 1024); 24 Feb 2004 17:29:03 -0000 Date: Tue, 24 Feb 2004 12:29:03 -0500 From: ari To: freebsd-hackers@freebsd.org Message-ID: <20040224172902.GH33517@episec.com> Mail-Followup-To: ari , freebsd-hackers@freebsd.org References: <6.0.3.0.2.20040224190540.02a65998@202.179.0.80> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: OT: tftp server X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 17:31:16 -0000 You may also wish to look at firewall rules. If return-udp packets are filtered, one may run into transfer problems with tftp, even using "stateful" udp inspection. The return udp source port will be the server's transfer identification number, and this will not often be port 69, as the filter would expect from the state table. If you have implemented filtering, you should check into this. ari rwatson@freebsd.org said this stuff: > > On Tue, 24 Feb 2004, Ganbold wrote: > > > Maybe this is off topic question. I'm looking for good tftp server in > > FreeBSD. I used default tftp server in FreeBSD and had some problems. > > It sometimes hangs without any response. Can somebody recommend me tftp > > server in FreeBSD/Unix/Linux? > > I can't recommend an alternative tftp server, but I can offer some help > debugging the current one -- the tftp server is pretty widely used, and I > haven't seen any other reports of this. Could you expand a bit on "hangs > without any response" -- do individual transfers stall, or the entire tftp > server? What flags are you using to tftpd in inetd.conf? If you use a > second client at the same time, does it also appear to be hung? What > clients are you using? > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"