Um 12:07 existierte das Problem noch, jetzt scheint es behoben zu sein, zumindest liefert die Maschine jetzt Bandbreite satt, auch via IPv6. Danke erstmal! Wodran lag es?
Beiträge von tichy
-
-
Bei meinem Server scheint es ein Problem mit dem IPv6 Upstream zu geben. Ich hab mal eine Testdatei online gestellt:
http://2.7183.org/test.img
https://2.7183.org/test.imgvon meinem Sixxs-Tunnel aus:
Codecurl -6 -o /dev/null http://2.7183.org/test.img % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 50.0M 0 193k 0 0 1722 0 8:27:26 0:01:54 8:25:32 4086Codecurl -4 -o /dev/null http://2.7183.org/test.img % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 50.0M 100 50.0M 0 0 3988k 0 0:00:12 0:00:12 --:--:-- 4642kCode
Alles anzeigengateway6 ~ # traceroute6 2.7183.org traceroute to 2.7183.org (2a03:4000:2:3a2::2:7183) from 2a01:198:200:2ad::2, 30 hops max, 16 byte packets 1 gw-686.dus-01.de.sixxs.net (2a01:198:200:2ad::1) 13.81 ms 14.782 ms 14.888 ms 2 * * * 3 edge1.dus1.de.as34225.net (2a01:198::1) 14.394 ms 14.789 ms 15.252 ms 4 ddf-b2-link.telia.net (2001:2000:3080:6a::1) 18.614 ms 17.16 ms 14.539 ms 5 ldn-b5-v6.telia.net (2001:2000:3018:b::1) 23.902 ms 20.754 ms 24.779 ms 6 level3-ic-153380-ldn-b5.c.telia.net (2001:2000:3080:4d6::2) 22.624 ms 49.886 ms 28.37 ms 7 vl-52.edge4.London1.Level3.net (2001:1900:101:2::9) 22.75 ms 23.951 ms 21.109 ms 8 vl-4060.edge4.Amsterdam1.Level3.net (2001:1900:5:1::206) 26.149 ms 22.069 ms 24.321 ms 9 vl-4081.edge3.Amsterdam1.Level3.net (2001:1900:5:1::10d) 25.618 ms 29.525 ms 25.017 ms 10 vl-4040.car1.Dusseldorf1.Level3.net (2001:1900:5:1::20e) 30.484 ms 117.894 ms 29.414 ms 11 vl-4080.car2.Dusseldorf1.Level3.net (2001:1900:5:1::112) 125.001 ms 197.655 ms 208.374 ms 12 vl-4060.edge4.Frankfurt1.Level3.net (2001:1900:5:1::211) 29.003 ms 28.625 ms 25.521 ms 13 vl-4082.edge3.Frankfurt1.Level3.net (2001:1900:5:1::121) 28.242 ms 28.317 ms 30.952 ms 14 xae0-3356.nbg20.core-backbone.com (2001:1900:5:2:2::1a86) 32.315 ms 35.433 ms 29.097 ms 15 2a01:4a0:0:2014::21 (2a01:4a0:0:2014::21) 33.581 ms 34.231 ms 29.917 ms 16 2a01:4a0:1338:24::2 (2a01:4a0:1338:24::2) 31.971 ms 32.881 ms 31.887 ms 17 2.7183.org (2a03:4000:2:3a2::2:7183) 34.015 ms 34.582 ms 33.321 msvon einer Maschine im DFN mit 1GBit-Anbindung aus:
Code~ $ curl -6 -o /dev/null http://2.7183.org/test.img % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 50.0M 0 118k 0 0 8843 0 1:38:48 0:00:13 1:38:35 5959Code~ $ curl -4 -o /dev/null http://2.7183.org/test.img % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 50.0M 100 50.0M 0 0 45.7M 0 0:00:01 0:00:01 --:--:-- 45.7MCode
Alles anzeigen~ $ /usr/sbin/traceroute6 2.7183.org traceroute to 2.7183.org (2a03:4000:2:3a2::2:7183) from 2001:638:502:811:225:64ff:febd:11dc, 30 hops max, 24 byte packets 1 2001:638:502:811::2 (2001:638:502:811::2) 0.71 ms 0.529 ms 0.52 ms 2 coren-gebE0.uni-paderborn.de (2001:638:502:f058::1) 1.906 ms 2.177 ms 2.569 ms 3 xr-pad1-ge6-1.x-win.dfn.de (2001:638:c:a044::1) 0.525 ms 0.436 ms 0.383 ms 4 xr-kas1-te1-3.x-win.dfn.de (2001:638:c:c01b::2) 2.314 ms 1.938 ms 1.887 ms 5 xr-mar1-te1-3.x-win.dfn.de (2001:638:c:c083::1) 3.525 ms 3.362 ms 3.286 ms 6 xr-gie1-te2-1.x-win.dfn.de (2001:638:c:c078::1) 15.355 ms 30.563 ms 4.129 ms 7 xr-gie1-te1-1.x-win.dfn.de (2001:638:c:c088::2) 5.014 ms 4.871 ms 4.828 ms 8 cr-fra1-te0-7-0-0.x-win.dfn.de (2001:638:c:c081::1) 7.449 ms 7.431 ms 7.625 ms 9 xae0-499.fra20.core-backbone.com (2001:7f8::8463:0:1) 17.002 ms 16.69 ms 16.26 ms 10 xae0-2002.nbg20.core-backbone.com (2a01:4a0:0:2002::2) 20.213 ms 19.567 ms 32.862 ms 11 2a01:4a0:0:2014::21 (2a01:4a0:0:2014::21) 19.682 ms 20.016 ms 19.532 ms 12 2a01:4a0:1338:24::2 (2a01:4a0:1338:24::2) 55.12 ms 20.028 ms 19.521 ms 13 2.7183.org (2a03:4000:2:3a2::2:7183) 19.803 ms 20.168 ms 19.575 msDer Downstream ist etwa so schnell wie erwartet.