-
Notifications
You must be signed in to change notification settings - Fork 17
fix: allow host gateway traffic for localhost/Playwright #1435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In chroot mode, this rewrites
localhosttohostGatewayIpthat was computed viadocker network inspect bridge. That IP may not match thehost.docker.internal:host-gatewayvalue for the AWF network (often the awf-net gateway, e.g. 172.30.0.1), which is whatsetup-iptables.shuses when adding NAT RETURN/ACCEPT rules. If these differ, chrooted processes will connect to an IP that is still DNAT’d to Squid (or blocked), so localhost/host access remains broken. Consider deriving the gateway from the actual AWF network (docker network inspect awf-net ... Gateway) or otherwise using the same IP that Docker will inject forhost-gatewayon the awf-net network.This issue also appears on line 848 of the same file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good observation, but this is already handled. The
host-iptables.tsFW_WRAPPER chain adds ACCEPT rules for both gateway IPs:getDockerBridgeGateway()(line 410)AWF_NETWORK_GATEWAY(line 414)Similarly,
setup-iptables.shadds NAT RETURN + FILTER ACCEPT for both thehost.docker.internalIP (resolved viagetent hosts, typically 172.17.0.1) AND the network gateway (172.30.0.1, resolved viaroute -n).The
/etc/hostsuses the Docker bridge gateway IP (172.17.0.1) for thelocalhostentry, which matches thehost.docker.internalIP that Docker injects viaextra_hosts: host-gateway. Traffic to this IP is allowed by both the container-level and host-level rules. The dual-gateway approach ensures it works regardless of which IP the tool resolves to.