Update ftp tutorial to use port range#569
Merged
Merged
Conversation
The FTP passive mode data channel requires a range of ports, not a single port. Update the guide to: - Configure vsftpd with a proper passive port range (10100–10200) - Replace the single tcp-backend-port/tcp-frontend-port config for the data channel with tcp-port-mapping=10100-10200:10100-10200 - Add an explanation that the port-mapping attribute is designed for protocols like FTP that operate over a range of ports - Fix the machine number in the jq expression (.machines."5" -> .machines."1")
- Remove spurious double blank line before section heading (MD022) - Add docs/release-notes/artifacts/pr0569.yaml for CI compliance
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR will be in draft until
ingress-configuratoris updated. Updates the FTP guide to use the new port-range featureWhat this PR does
Why we need it
Checklist
docs/changelog.mdwith user-relevant changesdocs/release-notes/artifacts. If no change artifact is necessary, I tagged the PR with the labelno-release-note.(e.g., in
.github/workflows/integration_tests.yaml, ensure themoduleslist is correct)terraform fmtpasses andtflintreports no errors