Title: cluster: bridge the Colima node VM to the Mac's Ethernet when attached, with Wi-Fi as the fallback · Issue #201 · ExaDev/github-runner · GitHub
Open Graph Title: cluster: bridge the Colima node VM to the Mac's Ethernet when attached, with Wi-Fi as the fallback · Issue #201 · ExaDev/github-runner
X Title: cluster: bridge the Colima node VM to the Mac's Ethernet when attached, with Wi-Fi as the fallback · Issue #201 · ExaDev/github-runner
Description: Owner's ask (2026-11-03): the Macs have both Wi-Fi and Ethernet, and each node should use Ethernet and fall back to Wi-Fi. Read live today: macOS already prefers Ethernet on m1 and m3 (the network service order lists the USB LAN services...
Open Graph Description: Owner's ask (2026-11-03): the Macs have both Wi-Fi and Ethernet, and each node should use Ethernet and fall back to Wi-Fi. Read live today: macOS already prefers Ethernet on m1 and m3 (the network ...
X Description: Owner's ask (2026-11-03): the Macs have both Wi-Fi and Ethernet, and each node should use Ethernet and fall back to Wi-Fi. Read live today: macOS already prefers Ethernet on m1 and m3 (the netw...
Opengraph URL: https://github.com/ExaDev/github-runner/issues/201
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"cluster: bridge the Colima node VM to the Mac's Ethernet when attached, with Wi-Fi as the fallback","articleBody":"Owner's ask (2026-11-03): the Macs have both Wi-Fi and Ethernet, and each node should use Ethernet and fall back to Wi-Fi.\n\nRead live today: macOS already prefers Ethernet on m1 and m3 (the network service order lists the USB LAN services before Wi-Fi) and falls back to Wi-Fi by itself, but only host traffic follows it. Each node's Colima profile (`node`, vmType vz) is bridged by Colima's own vmnet daemon to one fixed interface, `network.interface: en0`, which on m1 and m3 is the built-in Wi-Fi (on the mini it is the built-in Ethernet). The node's VM NIC (col0) therefore stays on Wi-Fi when an adapter is plugged in, and a VM bridged to an Ethernet interface would have no Wi-Fi path at all if that cable dropped. No Ethernet adapter is attached to m1 or m3 yet.\n\nConstraints found: Colima 0.10.3 passes a single bridged interface to Lima 2.1.2 (one vmnet socket, `networks: - socket: .../vmnet.sock, interface: col0`), so a second bridged NIC for an in-VM active-backup bond is not available through Colima's configuration; the role does not create or change VMs today (cluster role README, node network modes); a watcher that re-bridges on link change restarts the VM, which for a voter is a node restart.\n\nProposed design: bridge each Mac's node VM to its Ethernet interface once an adapter is attached (the role maps the profile's interface to its medium through `networksetup -listallhardwareports`), so the node has the wired direct LAN path; Wi-Fi is the fallback at the cluster level: if the cable drops the host's own routes carry Tailscale over Wi-Fi (DERP relay), the role controller sees the node's round trips and fsync rise and moves the vote to a fit standby (fleet issue 29 decision: no voter is pinned). Open questions for the build: how the role chooses and changes the interface (an inventory variable naming the adapter by a stable property such as its hardware port name, since USB adapter interface names change with the port), and how that change is applied to a running profile through the existing quorum guard, one server at a time.\n\nRevisit trigger: the Ethernet adapters are attached to m1 and m3 (adapter choice and purchase are the owner's, researched on 2026-11-03: fleet issue 29).\n","author":{"url":"https://github.com/Mearman","@type":"Person","name":"Mearman"},"datePublished":"2026-11-03T17:14:33Z","url":"https://github.com/ExaDev/github-runner/issues/201"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:3f17093b-ff22-3e6c-228f-f36d8225a2e5 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E5BA:3B9289:2FA445:436366:6B006C29 |
| html-safe-nonce | 9e45e6d32e7b5633de0a41272eb4fe2b6cc2a13a8a9c1b70045b78fb895ead52 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNUJBOjNCOTI4OToyRkE0NDU6NDM2MzY2OjZCMDA2QzI5IiwidmlzaXRvcl9pZCI6IjQ5NDAxNzY0MTkwNzk2MTM0ODIiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | c966b62f7ce8e60813cbb6ac413e0192ed92e9915e34e8499a2278e63b2445a6 |
| hovercard-subject-tag | issue:6187570717 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/ExaDev/github-runner/201/issue_layout |
| twitter:image | https://opengraph.githubassets.com/688243efa3d47c503a5375f2d0ffae5f617ebc13ceea040a8a71cac6befc205c/ExaDev/github-runner/issues/201 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/688243efa3d47c503a5375f2d0ffae5f617ebc13ceea040a8a71cac6befc205c/ExaDev/github-runner/issues/201 |
| og:image:alt | Owner's ask (2026-11-03): the Macs have both Wi-Fi and Ethernet, and each node should use Ethernet and fall back to Wi-Fi. Read live today: macOS already prefers Ethernet on m1 and m3 (the network ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Mearman |
| hostname | github.com |
| expected-hostname | github.com |
| None | 6527e91c60c0b29d16606ff32ac5df8ecdc37a2a62205ea057a14d7762c870fa |
| turbo-cache-control | no-preview |
| go-import | github.com/ExaDev/github-runner git https://github.com/ExaDev/github-runner.git |
| octolytics-dimension-user_id | 140118018 |
| octolytics-dimension-user_login | ExaDev |
| octolytics-dimension-repository_id | 1388126104 |
| octolytics-dimension-repository_nwo | ExaDev/github-runner |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1388126104 |
| octolytics-dimension-repository_network_root_nwo | ExaDev/github-runner |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 46f1cd2ae3cd8ae1a81019b5d619742e76f13bbd |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width