Opened 9 years ago
Closed 5 years ago
#11825 closed bug (invalid)
IPv6 connectivity problems on baron
| Reported by: | zooey | Owned by: | haiku-web |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Sys-Admin | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Some of our buildbot slaves fail when they use IPv6 to do a git clone from git.haiku-os.org. The error message is something along the lines of "network unreachable", i.e. indicating a routing problem.
The same buildslaves are able to connect to the buildbot master running on baron fine, most likely using IPv6, too, which leads me to think that only the VMs "behind" baron are affected by the problem.
A likely cause for the routing problems is that we are doing something wrong in our IPv6 setup with respect to router advertisements. AFAICS, baron needs to advertise all IPv6 hosts (i.e. the VMs) in its internal network to the router sitting directly in front of baron.
I remember having had problems when I set up the IPv6 support initially, which had the effect that none of the outside IPv6 traffic targetting any of the VMs was reaching baron (i.e. Hetzner's router must have filtered them out). When I asked Hetzner about it, they told me that they would switch their router to "automatic" mode. I can only assume that this means that the router now passes on all IPv6 traffic targetting our /64 network to baron. Maybe this isn't reliable and the routing stops to work when the VMs haven't produced any IPv6 traffic for some time?
The haiku-sysadmin user no longer exists, changing to haiku-web.