docs: use scoped UFW rules for Waydroid networking - #103
Open
xDestac wants to merge 1 commit into
Open
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
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.
Summary
waydroid0, the Waydroid subnet, and the selected host uplink.Why
The existing instructions open ports 53 and 67 on every interface and change UFW's forwarding policy globally.
On the tested system, UFW's
FORWARDpolicy dropped Waydroid traffic before it reached the host uplink, even though Waydroid's nftables rules were present. The scoped rules restore connectivity without changing UFW's default forwarding policy.Tested
waydroid0but not the host uplink while UFW blocked forwarded traffic.Related to waydroid/waydroid#1250.