IPv4-Exit über FFRL: Erfahrungen

Fortsetzung der Diskussion von NW: Internet Geschwindigkeit:

Das ist … interessant.

root@bgp3:~# wget -4 --bind-address=10.255.144.9 -O /dev/null http://cachefly.cachefly.net/100mb.bin
--2015-11-15 02:09:10--  http://cachefly.cachefly.net/100mb.bin
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘/dev/null’

100%[=========================================================================================>] 104,857,600 13.9MB/s   in 12s    

2015-11-15 02:09:23 (8.20 MB/s) - ‘/dev/null’ saved [104857600/104857600]

root@bgp3:~# wget -O /dev/null http://cachefly.cachefly.net/100mb.bin
--2015-11-15 02:09:27--  http://cachefly.cachefly.net/100mb.bin
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘/dev/null’

100%[=========================================================================================>] 104,857,600 58.5MB/s   in 1.7s   

2015-11-15 02:09:29 (58.5 MB/s) - ‘/dev/null’ saved [104857600/104857600]

Ich stelle nämlich fest, daß unsere über den FFRL ausleitenden GWs trotz GBit-Interfaces bei etwas über 100 MBit/sec gedeckelt sind, siehe oben.

Bei unseren direkt ausleitenden Systemen haben wir diese Diskrepanz nicht:

root@bgp1:~# wget -4 --bind-address=10.255.144.1 -O /dev/null http://cachefly.cachefly.net/100mb.bin
--2015-11-15 02:08:22--  http://cachefly.cachefly.net/100mb.bin
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘/dev/null’

100%[=========================================================================================>] 104,857,600 71.8MB/s   in 1.4s   

2015-11-15 02:08:23 (71.8 MB/s) - ‘/dev/null’ saved [104857600/104857600]

root@bgp1:~# wget -O /dev/null http://cachefly.cachefly.net/100mb.bin
--2015-11-15 02:08:28--  http://cachefly.cachefly.net/100mb.bin
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘/dev/null’

100%[=========================================================================================>] 104,857,600 84.4MB/s   in 1.2s   

2015-11-15 02:08:30 (84.4 MB/s) - ‘/dev/null’ saved [104857600/104857600]

FTR, die traces:

root@bgp1:~# traceroute -s 10.255.144.1 cachefly.cachefly.net
traceroute to cachefly.cachefly.net (205.234.175.175), 30 hops max, 60 byte packets
 1  100.64.0.6 (100.64.0.6)  0.305 ms  0.551 ms  0.489 ms
 2  xmws-gtso-de11.nw.mediaways.net (192.251.226.202)  0.746 ms  0.769 ms  0.742 ms
 3  ae1.cr-mira.gut1.he-core.de (80.237.129.49)  0.690 ms  0.658 ms  0.615 ms
 4  xmws-gtso-de31-chan-2.nw.mediaways.net (195.71.9.1)  0.583 ms  0.551 ms  0.493 ms
 5  et-0-1-0-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.59)  6.469 ms  6.466 ms et-7-1-0-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.57)  6.361 ms
 6  et-7-1-0-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.57)  6.007 ms  6.028 ms et-0-1-0-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.59)  17.213 ms
 7  vip1.G-anycast1.cachefly.net (205.234.175.175)  6.018 ms  6.098 ms  6.116 ms
root@bgp1:~# traceroute cachefly.cachefly.net
traceroute to cachefly.cachefly.net (205.234.175.175), 30 hops max, 60 byte packets
 1  xmws-gtso-de11.nw.mediaways.net (192.251.226.202)  0.521 ms  0.507 ms  0.532 ms
 2  ae1.cr-mira.gut1.he-core.de (80.237.129.49)  0.411 ms  0.382 ms  0.354 ms
 3  xmws-gtso-de31-chan-2.nw.mediaways.net (195.71.9.1)  0.400 ms  0.447 ms  0.457 
 4  et-0-1-0-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.59)  6.362 ms  6.320 ms  296 ms
 5  et-0-1-0-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.59)  6.153 ms  6.086 ms 7-1-0-0.0001.prrx.13.fra.de.net.telefonica.de (62.53.2.57)  6.007 ms
 6  vip1.G-anycast1.cachefly.net (205.234.175.175)  6.207 ms  6.317 ms  6.289 ms

 

root@bgp3:~# traceroute -s 10.255.144.9 cachefly.cachefly.net
traceroute to cachefly.cachefly.net (205.234.175.175), 30 hops max, 60 byte packets
 1  100.64.1.144 (100.64.1.144)  16.894 ms  16.876 ms  16.858 ms
 2  strato.ber.ecix.net (194.9.117.61)  21.203 ms  21.194 ms  21.180 ms
 3  ae2.0.morla.as6724.net (85.214.0.65)  21.142 ms  21.137 ms  21.125 ms
 4  vip1.G-anycast1.cachefly.net (205.234.175.175)  29.229 ms  29.222 ms  29.210 ms
root@bgp3:~# traceroute cachefly.cachefly.net
traceroute to cachefly.cachefly.net (205.234.175.175), 30 hops max, 60 byte packets
 1  static.217.167.9.5.clients.your-server.de (5.9.167.217)  0.088 ms  0.069 ms  0.043 ms
 2  static.161.67.9.5.clients.your-server.de (5.9.67.161)  0.951 ms  1.005 ms  1.023 ms
 3  hos-tr3-juniper4.rz16.hetzner.de (213.239.233.65)  0.171 ms hos-tr2-juniper3.rz16.hetzner.de (213.239.230.33)  1.077 ms hos-tr1-juniper3.rz16.hetzner.de (213.239.230.1)  0.237 ms
 4  core22.hetzner.de (213.239.245.145)  1.629 ms  0.270 ms core21.hetzner.de (213.239.245.105)  1.083 ms
 5  core1.hetzner.de (213.239.245.177)  4.905 ms core4.hetzner.de (213.239.245.18)  4.864 ms core1.hetzner.de (213.239.245.218)  4.856 ms
 6  juniper1.ffm.hetzner.de (213.239.245.5)  4.878 ms  5.045 ms  5.014 ms
 7  vip1.G-anycast1.cachefly.net (205.234.175.175)  5.437 ms  5.158 ms  5.176 ms
1 Like