fix(openclaw): bind gateway to loopback interface#1857
Open
felipevicens wants to merge 6 commits into
Open
Conversation
Add Bind: loopback to the openclaw gateway bootstrap configuration so the local gateway only listens on the loopback interface rather than all network interfaces. Signed-off-by: Felipe Vicens <felipejose.vicensgonzalez@telefonica.com>
Collaborator
|
thanks for the PR! Could you also just update the unit test here, so it also check the bind value being set correctly? |
Signed-off-by: Felipe Vicens <felipejose.vicensgonzalez@telefonica.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a Bind: "loopback" field to the openclaw gateway bootstrap config so the local gateway listens only on the loopback interface, matching the sandbox's iptables restrictions and making the gateway reachable from the TUI inside the sandbox network namespace.
Changes:
- Add
Bindfield togatewaySectionstruct, serialized as JSONbind. - Set
Bind: "loopback"when building the core bootstrap document. - Extend test to assert the generated gateway config contains
"bind": "loopback".
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| go/core/pkg/sandboxbackend/openshell/openclaw/types.go | Adds Bind field to gatewaySection. |
| go/core/pkg/sandboxbackend/openshell/openclaw/bootstrap.go | Sets Bind: "loopback" in generated bootstrap. |
| go/core/pkg/sandboxbackend/openshell/openclaw/bootstrap_test.go | Asserts bind value in generated JSON. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
peterj
approved these changes
May 13, 2026
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.
Add Bind: loopback to the openclaw gateway bootstrap configuration
so the local gateway only listens on the loopback interface rather
than all network interfaces.
Without this setting, OpenClaw defaults to 0.0.0.0. However, the sandbox iptables rules block all non-proxy traffic, so the TUI can only reach the gateway through loopback inside the sandbox network namespace. As a result, binding to 0.0.0.0 makes the gateway unreachable from the TUI (not connected to gateway).
Setting "bind": "loopback" fixes the issue at the source in the generated config, instead of requiring a manual post-creation patch to openclaw.json.