docs(share_wifi): document the WiFi sharing scripts and link from README#103
Merged
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
1 participant
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
Rewrites
docs/share_wifi.mdto properly documentscripts/share_wifi.shandscripts/stop_share_wifi.sh, and links it from the README's More documentation section.Problem
The share-wifi doc existed as an unlinked stub: it wasn't reachable from the README, and it told users to hand-edit interface names and subnet even though the script auto-detects both. It also didn't explain what the scripts actually do or their side effects.
Solution
Rewrite the doc to match the current scripts: how detection works, what the host side sets up (IP forwarding + NAT), what the Jetson already provides out of the box (address, DHCP, default route via 192.168.55.100 — verified in L4T's
nv-l4t-usb-device-mode-config.sh), the missing-DNS gotcha with a one-line fix, and caveats (iptables flushing clobbers existing firewall rules, nothing persists across reboot). Add the doc to the README's More documentation list.