[gentoo-mirrors] IPv6-enabled rsync mirrors

[gentoo-mirrors] IPv6-enabled rsync mirrors

[Bernhard Schmidt]

Dear colleagues,

or better said former and not-yet colleagues, I was the administrator of 
rsync17.de back in 2003 before the use of IPv6 in portage rsync was 
eliminated by the change to sync twice to the same server (once for 
timestamp, once for the actual sync), which moved the name resolving 
from rsync to the portage code (which was IPv4-only).

After 2.5 years and due to the help of many people (including several 
Gentoo gurus^Wdevelopers) the necessary code has finally been added to 
portage and is now available in >=sys-apps/portage-2.1.1_pre3-r1. See 
the bug for yourself, http://bugs.gentoo.org/show_bug.cgi?id=37124 .

The reason I'm writing this mail is that in 2004 all AAAA records were 
pulled from the rotations (since it wasn't supported by portage anyway). 
What about adding IPv6 records to the rotation again (maybe no more than 
three per hostname to allow it to fail gracefully in the unexpected case 
that an IPv4-only box chooses IPv6 for sync)?

I'm standing by with a fast machine on native GE to chime in if needed. 
Who here would be able to provide _decent_ (that means no crappy 
tunnelbrokers like HE.net, no transcontinental tunnels and IMHO no 6to4, 
but a decent native link or low-latency tunnel with enough available 
bandwidth) IPv6-enabled mirror for the rotations? Please remember that 
if this is about pushing IPv6 usage having mirrors with overall bad 
connection is actually the worst thing to do.

Any opinions?

Regards,
Bernhard
-- 
gentoo-mirrors@gentoo.org mailing list

Re: [gentoo-mirrors] IPv6-enabled rsync mirrors

[Travis Morgan]

> Who here would be able to provide _decent_ (that means no crappy 
> tunnelbrokers like HE.net, no transcontinental tunnels and IMHO no 6to4, 
> but a decent native link or low-latency tunnel with enough available 
> bandwidth) IPv6-enabled mirror for the rotations? Please remember that 
> if this is about pushing IPv6 usage having mirrors with overall bad 
> connection is actually the worst thing to do.
> 
> Any opinions?
> 
> Regards,
> Bernhard

It may take some time as I'm really busy and probably have to recompile
half the stuff on the box, but I may be able to oblige with a mirror. We
have several other machines already using IPv6 at our location and the
connection is fast and solid.

Let me know how things pan out.

Trav

-- 
gentoo-mirrors@gentoo.org mailing list

Re: [gentoo-mirrors] IPv6-enabled rsync mirrors

[Derk-Jan Hartman]

On 19-jul-2006, at 1:03, Bernhard Schmidt wrote:

> Dear colleagues,
>
> or better said former and not-yet colleagues, I was the  
> administrator of rsync17.de back in 2003 before the use of IPv6 in  
> portage rsync was eliminated by the change to sync twice to the  
> same server (once for timestamp, once for the actual sync), which  
> moved the name resolving from rsync to the portage code (which was  
> IPv4-only).
>
> After 2.5 years and due to the help of many people (including  
> several Gentoo gurus^Wdevelopers) the necessary code has finally  
> been added to portage and is now available in >=sys-apps/ 
> portage-2.1.1_pre3-r1. See the bug for yourself, http:// 
> bugs.gentoo.org/show_bug.cgi?id=37124 .
>
> The reason I'm writing this mail is that in 2004 all AAAA records  
> were pulled from the rotations (since it wasn't supported by  
> portage anyway). What about adding IPv6 records to the rotation  
> again (maybe no more than three per hostname to allow it to fail  
> gracefully in the unexpected case that an IPv4-only box chooses  
> IPv6 for sync)?
>
> I'm standing by with a fast machine on native GE to chime in if  
> needed. Who here would be able to provide _decent_ (that means no  
> crappy tunnelbrokers like HE.net, no transcontinental tunnels and  
> IMHO no 6to4, but a decent native link or low-latency tunnel with  
> enough available bandwidth) IPv6-enabled mirror for the rotations?  
> Please remember that if this is about pushing IPv6 usage having  
> mirrors with overall bad connection is actually the worst thing to do.

The ftp.snt.utwente.nl (rsync2.nl.gentoo.org) mirror should already  
be fully ipv6 enabled.
It's a native link and we'd love to be in the ipv6 rotation.

DJ

Trying "ftp.snt.utwente.nl"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22962
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

;; QUESTION SECTION:
;ftp.snt.utwente.nl.            IN      ANY

;; ANSWER SECTION:
ftp.snt.utwente.nl.     86400   IN      CNAME   vlaai.snt.utwente.nl.

;; AUTHORITY SECTION:
snt.utwente.nl.         86400   IN      NS      ns3.utwente.nl.
snt.utwente.nl.         86400   IN      NS      ns1.utwente.nl.
snt.utwente.nl.         86400   IN      NS      ns2.utwente.nl.

;; ADDITIONAL SECTION:
ns1.utwente.nl.         86400   IN      A       130.89.1.2
ns2.utwente.nl.         86400   IN      A       130.89.1.3
ns3.utwente.nl.         86400   IN      A       192.87.17.19

Received 158 bytes from 130.89.1.2#53 in 1 ms

machine:~ hartman$ host -a vlaai.snt.utwente.nl
Trying "vlaai.snt.utwente.nl"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5996
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 3, ADDITIONAL: 6

;; QUESTION SECTION:
;vlaai.snt.utwente.nl.          IN      ANY

;; ANSWER SECTION:
vlaai.snt.utwente.nl.   86400   IN      A       130.89.175.1
vlaai.snt.utwente.nl.   86400   IN      MX      100 mx.utwente.nl.
vlaai.snt.utwente.nl.   86400   IN      AAAA     
2001:610:1908:8000::175:1

;; AUTHORITY SECTION:
snt.utwente.nl.         86400   IN      NS      ns3.utwente.nl.
snt.utwente.nl.         86400   IN      NS      ns1.utwente.nl.
snt.utwente.nl.         86400   IN      NS      ns2.utwente.nl.

;; ADDITIONAL SECTION:
mx.utwente.nl.          86400   IN      A       130.89.2.13
mx.utwente.nl.          86400   IN      A       130.89.2.14
mx.utwente.nl.          86400   IN      A       130.89.2.12
ns1.utwente.nl.         86400   IN      A       130.89.1.2
ns2.utwente.nl.         86400   IN      A       130.89.1.3
ns3.utwente.nl.         86400   IN      A       192.87.17.19

Received 251 bytes from 130.89.1.2#53 in 16 ms


====== RSYNC ipv6 connect =====

hartman$ rsync -6 rsync://ftp.snt.utwente.nl/gentoo-portage
                 Welcome to the ftp.snt.utwente.nl archive.
This service is provided to you by:

Studenten Net Twente (SNT)    http://www.snt.utwente.nl/
the University of Twente      http://www.utwente.nl/

This system may be used 24 hours a day, 7 days a week.

All transfers are logged with your hostname and email address.
If you don't like this policy, disconnect now!

We are available on:
   http://ftp.snt.utwente.nl/
    ftp://ftp.snt.utwente.nl/
rsync://ftp.snt.utwente.nl/


Sponsors:
Murphy Software B.V.      http://www.murphy.nl
Virtu Secure Webservices  http://www.virtu.nl
Utwente Faculty of TNW    http://www.tnw.utwente.nl
Sjoerd van Groning


DISCLAIMER: Neither University of Twente nor SNT are liable for any use,
storage or transmission of any files stored on this archive. Since
much of our archive is mirrored from other servers, we can not check
all files for virusinfections.  Please proceed with caution.

If you have any problems or comments about this archive, please send
them via e-mail to ftpcom_at_snt.utwente.nl. Please also let us know
if there is something we don't have that you think we should!




drwxr-xr-x      155648 2006/09/01 17:00:01 .
-r--r--r--           1 2006/09/01 17:00:01 Archive-Update-in-Progress- 
kruimel.snt.utwente.nl
drwxr-xr-x        4096 2006/07/04 06:36:06 app-accessibility
drwxr-xr-x        4096 2006/09/01 16:06:34 app-admin
drwxr-xr-x          64 2006/02/17 23:05:24 app-antivirus
drwxr-xr-x        4096 2006/09/01 16:06:34 app-arch
drwxr-xr-x        4096 2006/09/01 16:06:34 app-backup
drwxr-xr-x        4096 2006/09/01 16:06:34 app-benchmarks
drwxr-xr-x        4096 2006/09/01 16:06:34 app-cdr
drwxr-xr-x        4096 2006/09/01 16:06:34 app-crypt
drwxr-xr-x        4096 2006/09/01 16:06:34 app-dicts
drwxr-xr-x        4096 2006/09/01 16:06:34 app-doc
drwxr-xr-x        4096 2006/09/01 16:06:34 app-editors
drwxr-xr-x        4096 2006/09/01 16:06:34 app-emacs
drwxr-xr-x        4096 2006/09/01 16:06:34 app-emulation
drwxr-xr-x        4096 2006/09/01 16:06:34 app-forensics


DJ
-- 
gentoo-mirrors@gentoo.org mailing list

[gentoo-mirrors] Scheduled downtime rsync4.no + distfiles mirror

[Richard Werner]

Downtime scheduled for:
rsync4.no.gentoo.org + mirror.gentoo.no

There is a scheduled maintenance to the cooling system where our machine is 
hosted. All machines will be shut down at aprox 18.00 (UTC+2) on the 5th. 

The maintenance window is set to 10hrs because of the extent of the repairs.
We will hopefully be back sooner than later ;)


---
Richard Werner
Admin of {mirror,rsync}.gentoo.{no,se}
-- 
gentoo-mirrors@gentoo.org mailing list

Re: [gentoo-mirrors] IPv6-enabled rsync mirrors

[Jin-Shan Tseng]

Hi folks,

    ftp.twaren.net(a.k.a. rsync6.tw.gentoo.org) is also fully ipv6 enabled.

    It's a native link and we would like to be in the ipv6 rotation.

    Thanks !

Regards,
Sam

Derk-Jan Hartman wrote:
> On 19-jul-2006, at 1:03, Bernhard Schmidt wrote:
>
>> Dear colleagues,
>>
>> or better said former and not-yet colleagues, I was the administrator 
>> of rsync17.de back in 2003 before the use of IPv6 in portage rsync 
>> was eliminated by the change to sync twice to the same server (once 
>> for timestamp, once for the actual sync), which moved the name 
>> resolving from rsync to the portage code (which was IPv4-only).
>>
>> After 2.5 years and due to the help of many people (including several 
>> Gentoo gurus^Wdevelopers) the necessary code has finally been added 
>> to portage and is now available in >=sys-apps/portage-2.1.1_pre3-r1. 
>> See the bug for yourself, http://bugs.gentoo.org/show_bug.cgi?id=37124 .
>>
>> The reason I'm writing this mail is that in 2004 all AAAA records 
>> were pulled from the rotations (since it wasn't supported by portage 
>> anyway). What about adding IPv6 records to the rotation again (maybe 
>> no more than three per hostname to allow it to fail gracefully in the 
>> unexpected case that an IPv4-only box chooses IPv6 for sync)?
>>
>> I'm standing by with a fast machine on native GE to chime in if 
>> needed. Who here would be able to provide _decent_ (that means no 
>> crappy tunnelbrokers like HE.net, no transcontinental tunnels and 
>> IMHO no 6to4, but a decent native link or low-latency tunnel with 
>> enough available bandwidth) IPv6-enabled mirror for the rotations? 
>> Please remember that if this is about pushing IPv6 usage having 
>> mirrors with overall bad connection is actually the worst thing to do.
>
> The ftp.snt.utwente.nl (rsync2.nl.gentoo.org) mirror should already be 
> fully ipv6 enabled.
> It's a native link and we'd love to be in the ipv6 rotation.
>
> DJ
>
> Trying "ftp.snt.utwente.nl"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22962
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
>
> ;; QUESTION SECTION:
> ;ftp.snt.utwente.nl.            IN      ANY
>
> ;; ANSWER SECTION:
> ftp.snt.utwente.nl.     86400   IN      CNAME   vlaai.snt.utwente.nl.
>
> ;; AUTHORITY SECTION:
> snt.utwente.nl.         86400   IN      NS      ns3.utwente.nl.
> snt.utwente.nl.         86400   IN      NS      ns1.utwente.nl.
> snt.utwente.nl.         86400   IN      NS      ns2.utwente.nl.
>
> ;; ADDITIONAL SECTION:
> ns1.utwente.nl.         86400   IN      A       130.89.1.2
> ns2.utwente.nl.         86400   IN      A       130.89.1.3
> ns3.utwente.nl.         86400   IN      A       192.87.17.19
>
> Received 158 bytes from 130.89.1.2#53 in 1 ms
>
> machine:~ hartman$ host -a vlaai.snt.utwente.nl
> Trying "vlaai.snt.utwente.nl"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5996
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 3, ADDITIONAL: 6
>
> ;; QUESTION SECTION:
> ;vlaai.snt.utwente.nl.          IN      ANY
>
> ;; ANSWER SECTION:
> vlaai.snt.utwente.nl.   86400   IN      A       130.89.175.1
> vlaai.snt.utwente.nl.   86400   IN      MX      100 mx.utwente.nl.
> vlaai.snt.utwente.nl.   86400   IN      AAAA    2001:610:1908:8000::175:1
>
> ;; AUTHORITY SECTION:
> snt.utwente.nl.         86400   IN      NS      ns3.utwente.nl.
> snt.utwente.nl.         86400   IN      NS      ns1.utwente.nl.
> snt.utwente.nl.         86400   IN      NS      ns2.utwente.nl.
>
> ;; ADDITIONAL SECTION:
> mx.utwente.nl.          86400   IN      A       130.89.2.13
> mx.utwente.nl.          86400   IN      A       130.89.2.14
> mx.utwente.nl.          86400   IN      A       130.89.2.12
> ns1.utwente.nl.         86400   IN      A       130.89.1.2
> ns2.utwente.nl.         86400   IN      A       130.89.1.3
> ns3.utwente.nl.         86400   IN      A       192.87.17.19
>
> Received 251 bytes from 130.89.1.2#53 in 16 ms
>
>
> ====== RSYNC ipv6 connect =====
>
> hartman$ rsync -6 rsync://ftp.snt.utwente.nl/gentoo-portage
>                 Welcome to the ftp.snt.utwente.nl archive.
> This service is provided to you by:
>
> Studenten Net Twente (SNT)    http://www.snt.utwente.nl/
> the University of Twente      http://www.utwente.nl/
>
> This system may be used 24 hours a day, 7 days a week.
>
> All transfers are logged with your hostname and email address.
> If you don't like this policy, disconnect now!
>
> We are available on:
>   http://ftp.snt.utwente.nl/
>    ftp://ftp.snt.utwente.nl/
> rsync://ftp.snt.utwente.nl/
>
>
> Sponsors:
> Murphy Software B.V.      http://www.murphy.nl
> Virtu Secure Webservices  http://www.virtu.nl
> Utwente Faculty of TNW    http://www.tnw.utwente.nl
> Sjoerd van Groning
>
>
> DISCLAIMER: Neither University of Twente nor SNT are liable for any use,
> storage or transmission of any files stored on this archive. Since
> much of our archive is mirrored from other servers, we can not check
> all files for virusinfections.  Please proceed with caution.
>
> If you have any problems or comments about this archive, please send
> them via e-mail to ftpcom_at_snt.utwente.nl. Please also let us know
> if there is something we don't have that you think we should!
>
>
>
>
> drwxr-xr-x      155648 2006/09/01 17:00:01 .
> -r--r--r--           1 2006/09/01 17:00:01 
> Archive-Update-in-Progress-kruimel.snt.utwente.nl
> drwxr-xr-x        4096 2006/07/04 06:36:06 app-accessibility
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-admin
> drwxr-xr-x          64 2006/02/17 23:05:24 app-antivirus
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-arch
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-backup
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-benchmarks
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-cdr
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-crypt
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-dicts
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-doc
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-editors
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-emacs
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-emulation
> drwxr-xr-x        4096 2006/09/01 16:06:34 app-forensics
>
>
> DJ
> --gentoo-mirrors@gentoo.org mailing list
-- 
gentoo-mirrors@gentoo.org mailing list