Skip to content

Fix egress DNS deployment firewall - #9

Merged
arslnb merged 1 commit into
mainfrom
codex/egress-deploy-dns
Jun 26, 2026
Merged

Fix egress DNS deployment firewall#9
arslnb merged 1 commit into
mainfrom
codex/egress-deploy-dns

Conversation

@arslnb

@arslnb arslnb commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • make the sandbox nftables table reload-safe with destroy table inet sandboxd
  • allow sandbox bridge traffic to the controlled DNS proxy through UFW
  • keep provisioning/install scripts aligned with the deployed network model

Validation

  • bash -n deploy/install.sh deploy/provision-node.sh
  • git diff --check
  • cargo test -p sandboxd egress
  • EX44: nft -c -f against the patched nftables file
  • EX44: ufw --dry-run allow in on wdbr0 to 10.200.0.1 port 53 proto udp/tcp

Live smoke context

The first EX44 egress smoke run passed egress none, CIDR/port allowlists, and policy rejection, but domain policies timed out on DNS. Kernel logs showed UFW blocking sandbox bridge packets to the host DNS proxy, so this patch adds the missing controlled DNS ingress allow.

@arslnb
arslnb merged commit fea8ef6 into main Jun 26, 2026
4 checks passed
@arslnb
arslnb deleted the codex/egress-deploy-dns branch June 26, 2026 07:17
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