WIP: Subnet #21

2026-06-22T23:13:39Z

fauno commented

2026-06-22 23:13:39 +00:00

when creating new nodes, garage will inform the private ipv4 address to remote nodes, preventing dial back. i've tested it and garage starts normally, but garage status still reports the unreachable ipv4 address so i'm still not sure if it works as intended. i'll come back to this when i start a new node.

when creating new nodes, garage will inform the private ipv4 address to remote nodes, preventing dial back. i've tested it and garage starts normally, but `garage status` still reports the unreachable ipv4 address so i'm still not sure if it works as intended. i'll come back to this when i start a new node.

fauno added 2 commits 2026-06-22 23:13:40 +00:00

feat: optionally specify subnets ce56135fd4

garage may still prefer the container's private ipv4 address and will
inform it to remote nodes, preventing dialbacks.  it should be useful
for private ipv6 networks.

fix: upgrade config version

continuous-integration/drone/pr Build is failing

Details

a88e56b4c2

fauno requested review from Brooke 2026-06-22 23:13:40 +00:00

Brooke approved these changes

2026-07-08 01:26:49 +00:00

Brooke left a comment

This looks good, my only note is to provide more information in the .env.sample, alternatively link to the documentation. Personally, I would be unsure why I would need to put something there if I had only read the .env comment. I don't think it's a blocking issue, just a note.

https://garagehq.deuxfleurs.fr/reference_manual/configuration.html#rpc_public_addr

This looks good, my only note is to provide more information in the .env.sample, alternatively link to the documentation. Personally, I would be unsure why I would need to put something there if I had only read the .env comment. I don't think it's a blocking issue, just a note. https://garagehq.deuxfleurs.fr/reference_manual/configuration.html#rpc_public_addr

fauno commented

2026-10-09 12:23:52 +00:00

just tried this and it doesn't work because our ipv6 subnet is not assigned to the container, so dialback connections are attempted to the ipv4 internal addresses garage has access to. the only way to stablish two way connections are by using abra app run garage.doma.in app -- /garage node connect new.node.id@ipv6:add:ress

i'll close this pr and open a new one with notes on the README

just tried this and it doesn't work because our ipv6 subnet is not assigned to the container, so dialback connections are attempted to the ipv4 internal addresses garage has access to. the only way to stablish two way connections are by using `abra app run garage.doma.in app -- /garage node connect new.node.id@ipv6:add:ress` i'll close this pr and open a new one with notes on the README

fauno commented

2026-10-25 15:12:57 +00:00

correction: i ran the Inspect the filesystem or processes from another container and i can find the ipv6 address assigned from the ipv6 gateway network, although it's not reported by docker inspect.

i'll keep testing this

correction: i ran the [Inspect the filesystem or processes from another container](https://garagehq.deuxfleurs.fr/documentation/operations/debugging/) and i can find the ipv6 address assigned from the ipv6 gateway network, although it's not reported by `docker inspect`. i'll keep testing this

Some required checks failed

continuous-integration/drone/pr Build is failing

Details

This pull request has changes conflicting with the target branch.

.env.sample

This pull request is marked as a work in progress.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin subnet:subnet

git checkout subnet

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/garage#21