Date: Mon, 5 Mar 2001 10:23:12 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Jean-Christophe Varaillon <jcv@vbc.net> Cc: freebsd-net@FreeBSD.ORG Subject: Re: - TFTP: Time out - Message-ID: <20010305102312.U8663@fw.wintelcom.net> In-Reply-To: <Pine.BSF.4.10.10103051805400.47293-100000@brunel.uk1.vbc.net>; from jcv@vbc.net on Mon, Mar 05, 2001 at 06:17:19PM %2B0000 References: <Pine.BSF.4.10.10103051805400.47293-100000@brunel.uk1.vbc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Jean-Christophe Varaillon <jcv@vbc.net> [010305 10:17] wrote: > > +-----------+ +------------+ > |FreeBSD 4.1|<--------->| Cisco 3640 | > +-----------+ +------------+ > > I want to transfer a file from the FreeBSD machine to the Cisco. > My machine is configured as a TFTP server and the cisco is "configured" > as a client. > > The TFTP communication is stopped because of a timeout. > > Why should I have a timeout ? Because afaik tftp has a really terrible client/server notion, there's no good way to tell if a client has 'gone away'. Without the timeout, if a client was to disappear the tftpd server would hang around forever. > BUT, I can transfer a files from the Cisco to my machine witout any > trouble. at this moment, the cisco is configured as a TFTP Server, and I > think that my machine also, but it reacts as a client. You should probably be able to fix this by changing the value of "TIMEOUT" in /usr/src/libexec/tftpd/tftpd.c, then doing this in /usr/src/libexec/tftpd: make ; make install -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010305102312.U8663>