You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Dan Armbrust (JIRA)" <ji...@apache.org> on 2008/02/24 00:32:20 UTC
[jira] Issue Comment Edited: (NET-181) tftp client limited to ~32
MB file sizes
[ https://issues.apache.org/jira/browse/NET-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571803#action_12571803 ]
armbrust edited comment on NET-181 at 2/23/08 3:31 PM:
-----------------------------------------------------------
Attached file is same patch as above.
was (Author: armbrust):
Same patch as above.
> tftp client limited to ~32 MB file sizes
> ----------------------------------------
>
> Key: NET-181
> URL: https://issues.apache.org/jira/browse/NET-181
> Project: Commons Net
> Issue Type: Improvement
> Environment: All
> Reporter: Dan Armbrust
> Priority: Minor
> Attachments: TFTPClient.java.patch
>
>
> I just noticed that the TFTPClient class does not support a block wraparound - hence, when the block number exceeds the max allowed by the rfc (65535) - about a 32 mb file - bad things will happen.
> I can't find any rfc that specifies how the wraparound is supposed to occur, but this wiki page mentions it:
> http://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol
> And I am working on implementing a TFTPServer - and in my tests with the tftp client that is shipped with fedora, I have determined that that tftp client expects the next block number after 65535 to be 0.
> So it appears that the TFTPClient should wrap its block number so that it properly supports larger files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.