Skip to content

Restore managed C-Gate LAN access and release 1.34.7 - #106

Merged
dougrathbone merged 3 commits into
masterfrom
dougrathbone/fix-remote-cgate-access-d06b
Sep 6, 2026
Merged

dougrathbone merged 3 commits into
masterfrom
dougrathbone/fix-remote-cgate-access-d06b

Conversation

@dougrathbone

Copy link
Copy Markdown
Owner

Summary

Fixes #104: after an add-on upgrade, C-Bus Toolkit and other LAN clients could not reach managed C-Gate. Home Assistant left the C-Gate ports unpublished unless they were remapped, and Docker NAT often presented the PC as the container gateway so access.txt never matched.

This PR also lands Dependabot #101 (Alpine 3.24 builder) and #103 (QEMU 4.3.0 and action-gh-release 3.0.3), and bumps the add-on to 1.34.7.

Changes

  • Publish C-Gate ports 20023-20025 and 20123-20125 on the host by default. Disable unused ones in the Network panel. C-Gate still refuses anyone not in cgate_external_clients.
  • When external clients are listed, also grant the Docker default gateway at the highest configured level so SNATted Toolkit connections match.
  • Alpine 3.24 for the npm-ci builder only; runtime stays on Home Assistant 3.21 bases.
  • Pin docker/setup-qemu-action v4.3.0 and softprops/action-gh-release v3.0.3.
  • Release 1.34.7.

Supersedes #101 and #103.

Test plan

  • npm test passes locally (3088 tests)
  • npm run lint and npm run typecheck pass
  • New access-control tests for NAT gateway grant, public-gateway rejection, duplicate skip, and no grant without clients
  • Addon integration asserts C-Gate ports are numeric host defaults, 8080 stays unmapped
Open in Web Open in Cursor 

Alpine 3.24 is only the npm-ci builder stage; runtime stays on the
Home Assistant 3.21 bases. QEMU 4.3.0 and action-gh-release 3.0.3
match Dependabot PRs #101 and #103.
Home Assistant was leaving C-Gate ports unpublished unless they were
remapped after every add-on update, so Toolkit never reached the
container. Publish 20023-20025 and 20123-20125 on the host by default.

When external clients are listed, also grant the container default
gateway at the highest configured level, because Docker SNAT often
presents every LAN peer as that address instead of the PC.

Fixes #104.
@dougrathbone
dougrathbone merged commit a205f99 into master Sep 6, 2026
25 checks passed
@cursor
cursor Bot deleted the dougrathbone/fix-remote-cgate-access-d06b branch September 8, 2026 23:23
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.

Remote C-Gate access refused

2 participants