Skip to content

Conversation

@r00ta
Copy link

@r00ta r00ta commented Jul 23, 2025

In some environments clients are requesting a blocksize that is not compatible with the MTU of the network infrastructure. In TFTPD there is a max_blocksize option https://manpages.debian.org/testing/tftpd-hpa/tftpd.8.en.html

[--blocksize max-block-size, -B max-block-size](https://manpages.debian.org/testing/tftpd-hpa/tftpd.8.en.html#blocksize)
    Specifies the maximum permitted block size. The permitted range for this parameter is from 512 to 65464. Some embedded clients request large block sizes and yet do not handle fragmented packets correctly; for these clients, it is recommended to set this value to the smallest MTU on your network minus 32 bytes (20 bytes for IP, 8 for UDP, and 4 for TFTP; less if you use IP options on your network.) For example, on a standard Ethernet (MTU 1500) a value of 1468 is reasonable.

so this MP aims to add the same to this TFTP server.

Any feedback is very welcome!

@r00ta
Copy link
Author

r00ta commented Jul 23, 2025

Hi @shylent (or @allenap if you have the rights to contribute to this repo), may I ask you to review this?

@r00ta r00ta changed the title Adding max_blocksize setting to deal with clients not Adding max_blocksize setting Jul 23, 2025
@allenap
Copy link
Contributor

allenap commented Jul 24, 2025

@r00ta I don't have access to this repo, nor do I work with this library any more. More importantly, @shylent does not appear to have been active on GitHub for ~5 years or more. You may want to continue development in your own fork.

@r00ta
Copy link
Author

r00ta commented Jul 24, 2025

@r00ta I don't have access to this repo, nor do I work with this library any more. More importantly, @shylent does not appear to have been active on GitHub for ~5 years or more. You may want to continue development in your own fork.

It's fine, thank you anyways!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants