Skip to content

chore(prop): bump to per-interface mDNS advertising (prop#7) - #383

Closed
jonasbark wants to merge 1 commit into
6.6from
chore/bump-prop-mdns-multi-interface
Closed

jonasbark wants to merge 1 commit into
6.6from
chore/bump-prop-mdns-multi-interface

Conversation

@jonasbark

Copy link
Copy Markdown
Collaborator

What

Bumps the prop submodule to the per-interface mDNS responder.

Depends on

OpenBikeControl/prop#7 — kept as a draft until that merges. If prop#7 is squash-merged (new SHA), this pointer will be updated to the merged commit before marking ready. Merging this before prop#7 would point 6.6 at a feature-branch commit, so: do not merge yet.

Why

On a multi-homed host (Ethernet + Wi-Fi, even on the same /24) BikeControl advertised a single address and pinned egress to one interface, so a trainer app on the other interface found it but couldn't connect. Quantified: 21 submitted self-tests flagged advertisedAddress warn. prop#7 announces once per reachable interface, each packet carrying that interface's own address — no single packet ever lists an unreachable address (avoiding the .NET/Mono "No route to host" hazard).

🤖 Generated with Claude Code

Points the prop submodule at the multi-interface mDNS responder
(OpenBikeControl/prop#7): announce per reachable interface, each
carrying that interface's own address, so a multi-homed host (e.g.
Ethernet + Wi-Fi, even same /24) is reachable on every LAN it is on.

Fixes the quantified "advertisedAddress warn / found-but-can't-connect"
class of discovery failures.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@jonasbark jonasbark closed this Sep 18, 2026
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.

1 participant