Repository navigation
Firmware 3.0.29: USB SIM stick on the home LAN prefix, DNS over the SIM - #46
Merged
Merged
Conversation
…way links Routing: a USB stick or modem network that overlaps the Wi-Fi/Ethernet LAN prefix (192.168.1.0/24 on both sides, as on board A with a TCL Link Key) took the home LAN's traffic, because lwIP picks the newest netif with a matching prefix. cell_overlap_route() sends such destinations to the LAN uplink; the modem's own address and a source bound to it stay on the modem, and its gateway, DHCP server and resolvers only while it carries the Internet uplink (its .1 gateway is often the home router's address). Route lookup reports the reason. Host routing tests cover both states. Web UI: System -> About, the updates page and the USB guide link the RecoveryGateway repository and site; the release-notes link accepts releases of RecoveryGateway (and the redirect repository at the old name).
…ng stick On board A (USB SIM primary, home LAN and stick both 192.168.1.0/24) the global resolver list held the home router (.254, Wi-Fi lease). Routed to the stick, every lookup failed and the control session flapped (about 200 s connected, 200 s reconnecting). Only the stick's gateway and DHCP server follow the stick while it carries the Internet uplink; other resolvers in the shared prefix go to the LAN uplink.
…plink Owner, with the SIM set as the main Internet uplink: lookups should use it too. The route supervisor now swaps a LAN resolver (on the LAN uplink's prefix, or any private one while the LAN uplink is down) for the stick's gateway while the stick carries the Internet uplink, re-asserts it after a Wi-Fi lease renewal, and restores the LAN resolver once Wi-Fi/Ethernet is the uplink again unless it changed meanwhile. Public or user-chosen resolvers and PPP modems are left alone. Host tests cover each case.
…eryGateway Website: 3.0.29 web installer files (the board-tested image b5d26ac7...), NEXT_VERSION 3.0.29. Packaging: Mattboxx/RecoveryGateway is the default release repository (source URL in the licence notices and manifest). Validation: 168/168 offline on 6440d7a; board A with the SIM stick as primary uplink 21/23, the two failures being pings dropped by the test PC's firewall.
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.
Firmware 3.0.29.
Mattboxx/RecoveryGateway, release-notes link accepted for its releases.Mattboxx/RecoveryGateway; 3.0.29 site installer files.Validation:
validate_all.py --build --browser168/168 on 6440d7a; board A with the SIM stick as primary uplink 21/23 with the exact image b5d26ac7… (the two failures are pings dropped by the test PC's Windows firewall); Tailscale connected 8 minutes without a drop.