Date: Fri, 10 Nov 2006 10:07:52 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Chris <cdtelting-ml@comcast.net> Cc: freebsd-questions@freebsd.org Subject: Re: TFTP Problems Message-ID: <443b8re3w7.fsf@be-well.ilk.org> In-Reply-To: <4553E70A.9020501@comcast.net> (Chris's message of "Thu, 09 Nov 2006 18:42:18 -0800") References: <4553E70A.9020501@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris <cdtelting-ml@comcast.net> writes: > 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. 0.0.0.0 is bogus; it's considered a "Martian" address. IP hosts are normally *expected* to ignore them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443b8re3w7.fsf>