http://www.gentoo.org/main/en/mirrors2.xml Please change the name (URL) for OVH's mirror as follows: current name: mirror.ovh.net future name: gentoo.mirrors.ovh.net This applies to all protocols (ftp/http/rsync). This mirror serves distfiles as well as portage. That will enable us to switch over to a new hardware in near future. Also, since about two years years, we have the following mirror up and running: gentoo.bhs.mirrors.ovh.net location: Canada (Montreal) uplink: 1GBit/s unmetered Sponsor: OVH (http://www.ovh.com/ca/en/) ftp/http/rsync available over ipv4 as well as ipv6 This mirror serves distfiles as well as portage. Please feel free to add it to the list. Thanks, Felix
(In reply to felix.krohn from comment #0) > http://www.gentoo.org/main/en/mirrors2.xml > > Please change the name (URL) for OVH's mirror as follows: > > current name: mirror.ovh.net > future name: gentoo.mirrors.ovh.net > > This applies to all protocols (ftp/http/rsync). > This mirror serves distfiles as well as portage. done. > That will enable us to switch over to a new hardware in near future. If there are IP changes involved, as you are providing rsync2.fr.gentoo.org as well, these addresses are A records, please let us know when to change them. > > > > Also, since about two years years, we have the following mirror up and > running: > > gentoo.bhs.mirrors.ovh.net Please file a separate ticket in the appropriate component, thanks.
Not sure if I should open a separate bug for this, I'll first try without: can you also adapt the rsync ACL on masterportage.gentoo.org in order to accept rsync access from the following addresses to /gentoo-portage please? IPv4: 91.121.188.201 IPv6: 2001:41d0:1:bfc9::1 The existing Ipv4 addresses (91.121.124.139, 91.121.125.139) can be removed after a transitional period of about one week. Thanks! Felix
(In reply to Felix Krohn from comment #2) > Not sure if I should open a separate bug for this, I'll first try without: Usually, separate matters should be done in a separate bug. For changes, it's okay to reuse a bug; new mirrors such as the one you linked in c#0 must have their own bug. > > can you also adapt the rsync ACL on masterportage.gentoo.org in order to > accept rsync access from the following addresses to /gentoo-portage please? > > IPv4: 91.121.188.201 > IPv6: 2001:41d0:1:bfc9::1 done! Can we switch DNS already? > > The existing Ipv4 addresses (91.121.124.139, 91.121.125.139) can be removed > after a transitional period of about one week. > > Thanks! > Felix
Hello Alex, Thanks for looking into it, but the ACL doesn't seem to work yet: $ rsync rsync://masterportage.gentoo.org/gentoo-portage/ Welcome to albatross.gentoo.org / masterportage.gentoo.org, rsync1.us.gentoo.org, rsync0.uk.gentoo.org [...] @ERROR: access denied to gentoo-portage from mir8.ovh.net (2001:41d0:1:bfc9::1) rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.1] $ rsync --ipv4 rsync://masterportage.gentoo.org/gentoo-portage/ Welcome to albatross.gentoo.org / masterportage.gentoo.org, rsync1.us.gentoo.org, rsync0.uk.gentoo.org [...] @ERROR: access denied to gentoo-portage from mir8.ovh.net (91.121.188.201) rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.1] Can you have another look? Felix
(In reply to Felix Krohn from comment #4) oops, it helps to actually push changes. working now? :)
I confirm it works now, thanks! I just changed our DNS-records, you can do the same from your side whenever is good for you. Best regards, Felix
(In reply to Felix Krohn from comment #6) > I confirm it works now, thanks! > > I just changed our DNS-records, you can do the same from your side whenever > is good for you. Our DNS is updated, too. I see that 91.121.125.139 was listed as rsync3.fr.g.o; do I understand correctly, that you only service one IP address (91.121.188.201, aka rsync2.fr.g.o) now? I'll remove the old whitelist entries at the end of the week.
(In reply to Alex Legler from comment #7) > I see that 91.121.125.139 was listed as rsync3.fr.g.o; do I understand > correctly, that you only service one IP address (91.121.188.201, aka > rsync2.fr.g.o) now? No, we have the same setup on this server again: 2x 1 GBit/s unmetered IPv4+IPv6 $ host gentoo.mirrors.ovh.net gentoo.mirrors.ovh.net is an alias for mir8.ovh.net. mir8.ovh.net has address 91.121.188.201 mir8.ovh.net has address 91.121.189.201 mir8.ovh.net has IPv6 address 2001:41d0:1:bfc9::1 mir8.ovh.net has IPv6 address 2001:41d0:1:c0c9::1 So you can hardcode rsync[23].fr.g.o if you want. 91.121.188.201 is equivalent (same NIC) to 2001:41d0:1:bfc9::1 91.121.189.201 is equivalent (same NIC) to 2001:41d0:1:c0c9::1 Best regards, Felix
gentoo.mirrors.ovh.net is now resolving to mir2.ovh.ca, and traceroute shows that it's in Quebec, Canada, not France anymore. OVH: what is a hostname to get the French mirror specifically? The IPs you listed here don't work anymore.
(In reply to Robin Johnson from comment #9) > gentoo.mirrors.ovh.net is now resolving to mir2.ovh.ca, and traceroute shows > that it's in Quebec, Canada, not France anymore. > > OVH: what is a hostname to get the French mirror specifically? The IPs you > listed here don't work anymore. Hi Robin, Yes, I redirected the DNS name to our mirror located in CA for the time being as we had a hardware failure on the node located in France. I'm about to switch it back to France, hopefully by end of this week - This means the DNS hostname won't change. This change will also bring an anycasted and loadbalanced setup - which means the IP for the mirrors in France and Canada will be the same, but routing depend on the source IP's location. However, I'd first need an ACL update on rsync::masterportage.gentoo.org::gentoo-portage in order to proceed, the IPv4 to whitelist is 178.32.10.115. The following two whitelist entries can be deleted: 91.121.188.201, 2001:41d0:1:bfc9::1 Thanks and best regards, Felix
(In reply to Felix Krohn from comment #10) > Yes, I redirected the DNS name to our mirror located in CA for the time > being as we had a hardware failure on the node located in France. > I'm about to switch it back to France, hopefully by end of this week - This > means the DNS hostname won't change. This change will also bring an > anycasted and loadbalanced setup - which means the IP for the mirrors in > France and Canada will be the same, but routing depend on the source IP's > location. I'm familiar with anycast ;-). Would still like to have seperate non-anycast IPs for each side, so that they can be independently monitored. > However, I'd first need an ACL update on > rsync::masterportage.gentoo.org::gentoo-portage in order to proceed, the > IPv4 to whitelist is 178.32.10.115. > > The following two whitelist entries can be deleted: 91.121.188.201, > 2001:41d0:1:bfc9::1 ACL updated.
