The project network was IPv4 only, so Docker relayed IPv6 connections through docker-proxy and the server saw every IPv6 client as the gateway, 172.31.253.1. SPF/DMARC/iprev were checked against it, and IPv6 clients shared one set of bans and rate limits. With --proxy snippets (or front ends on the host) that address is also on the server's allowed list.
On a machine with IPv6, compose.yaml gives the network fd69:6e62:7578::/64 beside the IPv4 subnet. Re-running install converges an existing deployment (compose recreates the network).
Docker before 27 still relays IPv6 unless ip6tables is on, which there also needs experimental. deps / --install-deps now offers to set both in /etc/docker/daemon.json and restart Docker (old file kept as daemon.json.before-inbuxa, put back if Docker won't start). Without --install-deps the plan warns. Podman and Docker 27+ need nothing.
Outbound is unchanged in practice: the server tries IPv4 first by default.
Tested in the Debian 13 lab (Docker 26.1.5): new e2e/cases/ipv6-sources.sh 13/13 with OLD_REF=origin/main (bug shown, then fixed by converge) and 11/11 fresh; install-local 26/26, proxy-snippets 25/25. gofmt, vet (amd64 + arm64) and go test ./... clean.
Fixes #65.
The project network was IPv4 only, so Docker relayed IPv6 connections through docker-proxy and the server saw every IPv6 client as the gateway, 172.31.253.1. SPF/DMARC/iprev were checked against it, and IPv6 clients shared one set of bans and rate limits. With `--proxy snippets` (or front ends on the host) that address is also on the server's allowed list.
- On a machine with IPv6, compose.yaml gives the network `fd69:6e62:7578::/64` beside the IPv4 subnet. Re-running `install` converges an existing deployment (compose recreates the network).
- Docker before 27 still relays IPv6 unless `ip6tables` is on, which there also needs `experimental`. `deps` / `--install-deps` now offers to set both in `/etc/docker/daemon.json` and restart Docker (old file kept as `daemon.json.before-inbuxa`, put back if Docker won't start). Without `--install-deps` the plan warns. Podman and Docker 27+ need nothing.
- Outbound is unchanged in practice: the server tries IPv4 first by default.
Tested in the Debian 13 lab (Docker 26.1.5): new `e2e/cases/ipv6-sources.sh` 13/13 with `OLD_REF=origin/main` (bug shown, then fixed by converge) and 11/11 fresh; `install-local` 26/26, `proxy-snippets` 25/25. gofmt, vet (amd64 + arm64) and `go test ./...` clean.
The network the installer writes was IPv4 only. Docker relays an IPv6
connection to a published port of an IPv4-only container through
docker-proxy, so the server saw every client that connected over IPv6 as
the network's gateway, 172.31.253.1: SPF, DMARC and iprev were checked
against it, IPv6 senders shared one set of bans and rate limits, and
with --proxy snippets (or front ends on the host) the gateway is on the
server's allowed list, so IPv6 clients were never banned at all.
On a machine with IPv6, compose.yaml now gives the network a unique
local /64 (fd69:6e62:7578::/64) beside the IPv4 subnet. Re-running
install converges an existing deployment: compose recreates the network.
That is enough with Docker 27 and later and with podman, which forward
both families themselves. Docker before 27 still relays IPv6 unless
ip6tables is on, which there also takes "experimental" (with ip6tables
alone the daemon does not start). The survey now reads the engine
version and /etc/docker/daemon.json, and deps offers to set both keys,
keeping the old file as daemon.json.before-inbuxa and putting it back if
Docker does not come up on the new one. Without --install-deps the plan
warns instead, and it never writes over a daemon.json it cannot parse.
Outbound mail is unchanged in practice: the server tries IPv4 first by
default and uses IPv6 only for hosts that have no IPv4 address.
e2e/cases/ipv6-sources.sh opens SMTP sessions from a second network
namespace with addresses of its own; with OLD_REF it shows the bug on an
install from before the fix, then converges it.
Fixes#65
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #65.
The project network was IPv4 only, so Docker relayed IPv6 connections through docker-proxy and the server saw every IPv6 client as the gateway, 172.31.253.1. SPF/DMARC/iprev were checked against it, and IPv6 clients shared one set of bans and rate limits. With
--proxy snippets(or front ends on the host) that address is also on the server's allowed list.fd69:6e62:7578::/64beside the IPv4 subnet. Re-runninginstallconverges an existing deployment (compose recreates the network).ip6tablesis on, which there also needsexperimental.deps/--install-depsnow offers to set both in/etc/docker/daemon.jsonand restart Docker (old file kept asdaemon.json.before-inbuxa, put back if Docker won't start). Without--install-depsthe plan warns. Podman and Docker 27+ need nothing.Tested in the Debian 13 lab (Docker 26.1.5): new
e2e/cases/ipv6-sources.sh13/13 withOLD_REF=origin/main(bug shown, then fixed by converge) and 11/11 fresh;install-local26/26,proxy-snippets25/25. gofmt, vet (amd64 + arm64) andgo test ./...clean.