I always had these kinda problems both with
FreeBSD, Linux, etc etc. Found various ways
around them in the end but the best way is if
you are running a version of IOS 12.0 or later
on the Cisco then use the newer copy commands
in IOS that allow ftp eg:-
router> copy ftp://user:[EMAIL PROTECTED]/config.cond startup-config
much better than :-
router> copy tftp startup-config
Regards
Andy
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Alfred Perlstein
> Sent: 05 March 2001 18:23
> To: Jean-Christophe Varaillon
> Cc: [EMAIL PROTECTED]
> Subject: Re: - TFTP: Time out -
>
>
> * Jean-Christophe Varaillon <[EMAIL PROTECTED]> [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 - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
