Skip to content

device-cheetah 0.1.34: prefer Wi-Fi over the USB gateway - #205

Closed
kdegeek wants to merge 1 commit into
derekross:mainfrom
kdegeek:cheetah-usb-gateway-metric
Closed

kdegeek wants to merge 1 commit into
derekross:mainfrom
kdegeek:cheetah-usb-gateway-metric

Conversation

@kdegeek

@kdegeek kdegeek commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Summary

A generic routing fix identified during Comet bring-up, #143.

 [Network]
-Gateway=172.16.42.2
+[Route]
+Gateway=172.16.42.2
+Metric=1024

Keep the USB host as a fallback gateway so NetworkManager's Wi-Fi DHCP route
at metric 600 takes precedence. USB addressing and DNS settings are retained.

Evidence

  • Before: the unqualified USB gateway can take precedence over Wi-Fi.
    After: the package test verifies the gateway and metric belong to
    [Route], with no gateway left in [Network].
  • tests/packages omamobile-device-cheetah: passes with Homebrew Bash and
    GNU coreutils. tools/pr-check origin/main: all seven checks pass.
  • Identifier scan reports no hits. No phone or live route selection was tested.

Merge Danger

Door: two-way.

Blast Radius: cheetah. USB remains the fallback internet path when another
interface supplies a lower-metric default route. Live routing remains a
hardware validation gate.

🤖 Generated with Claude Code

Put the host gateway in a Route section with metric 1024 so Wi-Fi
DHCP routes at metric 600 take precedence. Preserve USB addressing and
public DNS. This generic fix was identified during Comet work (derekross#143).

Check section ownership, gateway and fallback metric in the package test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Thanks, Nate, you found a real problem. #102 fixed it the same way for every phone (the gateway under [Route] at metric 2000, after Wi-Fi and mobile data) and shipped as device-cheetah 0.1.35, so I'm closing this as superseded. Thank you for the test idea.

@derekross derekross closed this Oct 31, 2026
gitColinX added a commit to gitColinX/omarchy-mobile that referenced this pull request Nov 15, 2026
… a third phone

A NOTES entry for the third unit (Samsung 128 GB UFS 3.1) on merged
omamobile at 82f31d3a7 with the firmware from extract-vendor-firmware
(derekross#722): AirPods paired and played over A2DP, two rumble effects felt,
the torch seen, and the gauge reading at boot with no overlay (the bus
on by default since kernel derekross#205). The husky row's Bluetooth, Battery,
Haptics and Torch cells move from testing to works and link it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gitColinX added a commit to gitColinX/omarchy-mobile that referenced this pull request Nov 16, 2026
… a third phone

A NOTES entry for the third unit (Samsung 128 GB UFS 3.1) on merged
omamobile at 82f31d3a7 with the firmware from extract-vendor-firmware
(derekross#722): AirPods paired and played over A2DP, two rumble effects felt,
the torch seen, and the gauge reading at boot with no overlay (the bus
on by default since kernel derekross#205). The husky row's Bluetooth, Battery,
Haptics and Torch cells move from testing to works and link it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants