On 01/04/16 00:03, Sascha Spreitzer wrote:
PS.: The frontend is loadbalanced, so the backend ip is different.
To clarify:
Frontend IPs: 212.51.128.169, 2a02:168:7a0e::1
Backend IP (ip to authorize): 2a02:168:7a0e:6:5054:ff:fe77:b410 _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Well, so does that mean that your backend mirror has no ipv4 connectivity at all ? (for outgoing connections that is), or is that the one from the frontend that is used for outgoing connections (and so that needs to be allowed) ? Problem is that actually nodes in our msync network only have ipv4 (something I'd like to change, but you'd be surprised how many DC don't provide ipv6)