luci-app-tailscale-community: clarify subnet routing setup and refine UI strings #8252
+193
−118
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.
Signed-off-by: Tokisaki Galaxy <moebest@outlook.jp>row (viagit commit --signoff)luci-app-tailscale-community: titlefirst line subject for packagesPKG_VERSIONin the MakefileFirst of all, I sincerely apologize for submitting this follow-up PR so soon (less than 12 hours) after the initial merge of this package.
After immediate community feedback and further testing, it became clear that the "Auto Configure Firewall" button—while technically a helper—is a hard requirement for the "Site-to-Site" and "Exit Node" features. The previous wording labeled it as "Experimental," which discouraged users from clicking it, leading to common forwarding issues.
To ensure the best out-of-the-box experience for users installing via opkg, this PR refines the UI strings to be more goal-oriented.
Changes:
My goal is to minimize common support requests regarding "pings working but no data transfer" by providing clearer guidance directly within the LuCI interface.