Re: (ASCEND) P50 & forgotten password?

[Phillip Vandry <vandry@Mlink.NET>]

> James Courtier-Dutton[SMTP:jcdutton@lucent.com] asked:
> > At which point did TFTP become un-routable?
> 
> As defined in RFC1350 tftp does not fill in any Internet fields although they a
> re present. Therefore tftp cannot be routed.

Wow, really?

Are you talking about:

   "TFTP does not specify any of the values in the Internet header."

from section 3, paragraph 1? I take this to mean that tftp does not
require anything 'special' out of the IP header (IP options,
fragmentation, etc..) and that it's not tftp's job to insert the correct
values. I don't take this to mean that the source and destination IP
address are blank or something. How could it work at all without that?

In any case I've never seen an implementation that cripples tftp in this
way, in particular, not the Ascend one.

-Phil
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>