Jonathan Schleifer <js-netbsd-users%webkeks.org@localhost> writes: > Sixxs is known to have very unreliable routes. The routes look pretty sane to me, although my tunnel is to chicago - and then it connects to HE. traceroute6 to www.netbsd.org (2001:4f8:4:7:2e0:81ff:fe52:9a6b) from 2001:4978:1fb:6240::47, 64 hops max, 12 byte packets 1 t1-f 0.369 ms 0.294 ms 0.24 ms 2 gw-627.chi-02.us.sixxs.net 36.597 ms 59.177 ms 53.68 ms 3 sixxs.ge-0.0.0-30.core1.chi.bb6.your.org 87.181 ms 47.716 ms 31.785 ms 4 gige-g2-19.core1.chi1.he.net 34.149 ms 97.654 ms 29.952 ms 5 10gigabitethernet3-2.core1.sjc2.he.net 119.977 ms 114.442 ms 91.388 ms 6 10gigabitethernet3-2.core1.pao1.he.net 117.23 ms 95.389 ms 90.447 ms 7 he.pao1.isc.org 122.844 ms 140.33 ms 124.139 ms 8 int-1-2-0-800.r2.sfo2.isc.org 129.735 ms 98.822 ms 89.253 ms 9 sfo2-sql1.r1.sql1.isc.org 243.779 ms 315.544 ms 90.957 ms 10 www.NetBSD.Org 90.724 ms 91.522 ms 150.179 ms > I only get 130 KB/s and it's no difference whether I use IPv4 or > IPv6. Don't know why. But ftp.netbsd.org has always been slow for me. Just tried again - 184KB/s v6, 745KB/s v4. Connecting to my own server at MIT from BBN (direct v6 tunnel), I am getting 3.5 MB/s either way, with v6 a little more variable. My boxes are a mix of netbsd-4 and netbsd-5.
Attachment:
pgp_At4RSyytU.pgp
Description: PGP signature