Anyone else with awfull download speeds on package install?
-
Title is the question.
Since yesterday most pfSense boxes I manage are painfully slow to download packages. I searched but didn't found any thread or person reporting the same issue.
-
So I picked a big one:
$ fetch -v https://files.pfsense.org/packages/10/All/asterisk-1.8.26.1-amd64.pbi looking up files.pfsense.org connecting to files.pfsense.org:443 SSL options: 81004bff Peer verification enabled Using CA cert file: /usr/local/etc/ssl/cert.pem Verify hostname SSL connection established using ECDHE-RSA-AES256-GCM-SHA384 Certificate subject: /OU=Domain Control Validated/OU=PositiveSSL Wildcard/CN=*.pfsense.org Certificate issuer: /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA requesting https://files.pfsense.org/packages/10/All/asterisk-1.8.26.1-amd64.pbi remote size / mtime: 123351755 / 1398121307 asterisk-1.8.26.1-amd64.pbi 100% of 117 MB 1701 kBps 01m11s
Pretty much maxes out the downlink; would need to turn off the IPTV STBs to get faster.
-
So I picked a big one:
$ fetch -v https://files.pfsense.org/packages/10/All/asterisk-1.8.26.1-amd64.pbi looking up files.pfsense.org connecting to files.pfsense.org:443 SSL options: 81004bff Peer verification enabled Using CA cert file: /usr/local/etc/ssl/cert.pem Verify hostname SSL connection established using ECDHE-RSA-AES256-GCM-SHA384 Certificate subject: /OU=Domain Control Validated/OU=PositiveSSL Wildcard/CN=*.pfsense.org Certificate issuer: /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA requesting https://files.pfsense.org/packages/10/All/asterisk-1.8.26.1-amd64.pbi remote size / mtime: 123351755 / 1398121307 asterisk-1.8.26.1-amd64.pbi 100% of 117 MB 1701 kBps 01m11s
Pretty much maxes out the downlink; would need to turn off the IPTV STBs to get faster.
Strange… maybe a route problem between my region and the servers. Do you know where the ESF servers are located? Austin?
-
files.pfsense.org is at NYI's New Jersey datacenter. Generally at least 900 Mbps of bandwidth available at any given time. I'm getting about 7 MB/sec from home in Austin right now via either v4 or v6, with wife watching Netflix and misc other going on.
If your systems are dual stack, it'd be good to try the fetch doktornotor showed once with -4 and once with -6. Also throw in a '-o /dev/null' to take disk performance out of the equation. Like:
fetch -v -4 -o /dev/null https://files.pfsense.org/packages/10/All/asterisk-1.8.26.1-amd64.pbi
Nothing's changed on this end, and there aren't any problems. Guessing something somewhere in between you and NYI. What's a traceroute(6) from you to files.pfsense.org look like?
-
@cmb:
files.pfsense.org is at NYI's New Jersey datacenter. Generally at least 900 Mbps of bandwidth available at any given time. I'm getting about 7 MB/sec from home in Austin right now via either v4 or v6, with wife watching Netflix and misc other going on.
I was thinking from the start is was some problem between here(São Paulo - Brasil) and our beloved(hated) connection through Level3. I asked just to be sure.
Every time the route goes through Miami I have issues with bandwidth on servers hosted on Austin or anything north of it. Not only on pfSense, Spiceworks for example are there and I get similar problems.
Anyway, thanks for the feedback.