Add flag to enable/disable TFTP support #29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
InvoxiPlayGames
left a comment
InvoxiPlayGames
left a comment
There was a problem hiding this comment.
LGTM apart from a small nitpick.
(Granted it'd be better to actually fix the TFTP server rather than smooth over it by letting it be disabled... but easier said than done)
InvoxiPlayGames
approved these changes
Nov 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Being that TFTP support has some issues (most visibly with the RRQ errors that are spammed to the console), I found it very useful to have a method to disable TFTP support but retain functionality of the WebUI.
I've been using code equivalent to the "no TFTP support" case in my own fork of XeLL without any ill effects.