Bridge containers have no outbound TCP/UDP when host FORWARD policy is DROP (no accept or MASQUERADE rules for kiri0)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux, rust
- Domain
- infrastructure, networking
Research direction
Start by tracing how Kiri sets up its default bridge and host networking, then inspect the networking code and tests that configure forwarding and NAT; the issue does not name specific files. Reproduce with FORWARD policy set to DROP and compare bridge traffic with --network host. Done means the bridge can reach external TCP and DNS destinations, or setup and documentation clearly explain the required forwarding and masquerade rules.
Written by the indexing model from the issue text.
Description
Environment
- Kiri engine 0.2.0, Ubuntu with ufw active (iptables-nft)
- The real Docker engine is also installed and was running
FORWARDpolicy isDROP
What happens
- A container on the default bridge (
172.20.0.0/16onkiri0) can ping1.1.1.1. TCP to1.1.1.1:443and DNS to8.8.8.8and1.1.1.1time out. - The same lookup with
--network hostworks. - Builds fail with
lookup registry-1.docker.io: i/o timeout. iptables -S FORWARDandnft list rulesetshow no rule that accepts traffic onkiri0.iptables -t nat -S POSTROUTINGshowsMASQUERADEonly for the Docker, libvirt and Tailscale subnets, none for172.20.0.0/16.
Workaround
- A
ufw route allowrule in and out onkiri0. - A
MASQUERADErule for172.20.0.0/16in/etc/ufw/before.rules.
Expected: one of these:
- Kiri installs its own forward-accept and NAT rules (for example in its own nft table), or
kiri setupdetects aDROPforward policy and prints the needed rules, or- The docs list this requirement.
Repro
- Use a host with
iptables -P FORWARD DROP(ufw or Docker installed). - Start kiri.
- Run
docker run --rm alpine nc -z -w4 1.1.1.1 443. It fails. - Run
docker run --rm --network host alpine nc -z -w4 1.1.1.1 443. It works.
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 329
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 105
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libracoder/kiri
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#289 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 47/100
libracoder/kiri#365 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
libracoder/kiri#362 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 47/100
libracoder/kiri#359 ·
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day