From owner-freebsd-questions@FreeBSD.ORG Fri Nov 10 02:42:13 2006 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 C4CB316A407 for ; Fri, 10 Nov 2006 02:42:13 +0000 (UTC) (envelope-from cdtelting-ml@comcast.net) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63B7443D45 for ; Fri, 10 Nov 2006 02:42:13 +0000 (GMT) (envelope-from cdtelting-ml@comcast.net) Received: from mail.local ([76.168.219.28]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20061110024212.TWVV11275.mta10.adelphia.net@mail.local> for ; Thu, 9 Nov 2006 21:42:12 -0500 Received: from [192.168.1.63] (unknown [192.168.1.63]) by mail.local (Postfix) with ESMTP id 37249C for ; Thu, 9 Nov 2006 18:42:12 -0800 (PST) Message-ID: <4553E70A.9020501@comcast.net> Date: Thu, 09 Nov 2006 18:42:18 -0800 From: Chris User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: TFTP Problems 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: Fri, 10 Nov 2006 02:42:13 -0000 I'm still trying to figure out why the standard tftp won't accept ack connections from 0.0.0.0. It will recv ack's from a normal IP address just fine. It can't be the firewall because I can set it to "pass all" and restart with the same results. The tftp daemon is started from inetd. The server process is somewhat different for a inetd daemon as it recieves on socket 0 instead after it starts. It creates a socket for further communication after it retries the initial UDP packet sent. It sucessfully sends the first packet on this socket but it doesn't recv ack's for the packet though tcpdump see's them come in. The recv timesout and then it resends the first packet. The only thing I can think of is that inetd must initialize it's sockets in some special way to recieve from 0.0.0.0. Chris