VERY slow System Update
-
Use:
https://files00.netgate.com/packages/
The master branch there is 2.6.I'm not seeing any slowness with 2.6 snapshots here though.
Steve
-
@stephenw10 said in VERY slow System Update:
Use:
https://files00.netgate.com/packages/
The master branch there is 2.6.I'm not seeing any slowness with 2.6 snapshots here though.
Steve
Thank You for answering.
TRACEROUTE - ICMP - files00.netgate.com w/ name resolve
1 isp.net (AAA.BBB.CCC.DDD) 0.512 ms 0.531 ms 0.474 ms 2 isp.ip.twelve99-cust.net (AAA.BBB.CCC.DDD) 13.723 ms 13.682 ms 13.987 ms 3 bpt-b2-link.ip.twelve99.net (80.239.128.61) 22.058 ms 21.952 ms 21.846 ms 4 win-bb3-link.ip.twelve99.net (62.115.119.38) 130.719 ms 130.862 ms 130.449 ms 5 ffm-bb1-link.ip.twelve99.net (62.115.137.202) 130.181 ms 130.281 ms 130.278 ms 6 * prs-bb1-link.ip.twelve99.net (62.115.123.13) 127.522 ms * 7 ldn-bb1-link.ip.twelve99.net (62.115.135.24) 54.606 ms 54.434 ms 54.787 ms 8 nyk-bb2-link.ip.twelve99.net (62.115.113.20) 130.036 ms 130.075 ms 130.027 ms 9 nyk-b3-link.ip.twelve99.net (62.115.139.151) 128.414 ms 128.288 ms 128.258 ms 10 nyi-ic345091-nyk-b3.ip.twelve99-cust.net (62.115.175.141) 124.150 ms 124.082 ms 123.097 ms 11 64.147.115.3 (64.147.115.3) 140.721 ms 140.689 ms 140.703 ms 12 cs80.cs99new.v.ewr.nyinternet.net (96.47.77.214) 140.709 ms 140.643 ms 140.665 ms 13 162.208.119.41 (162.208.119.41) 128.929 ms 128.651 ms 128.609 ms
TRACEROUTE - UDP - files00.netgate.com w/name resolve
1 * * * 2 ISP.ip.twelve99-cust.net (AAA.BBB.CCC.DDD) 14.551 ms 14.348 ms 14.066 ms 3 bpt-b2-link.ip.twelve99.net (80.239.128.61) 23.828 ms 23.872 ms 23.852 ms 4 win-bb3-link.ip.twelve99.net (62.115.119.38) 129.599 ms 130.403 ms 132.482 ms 5 ffm-bb1-link.ip.twelve99.net (62.115.137.202) 132.099 ms 130.269 ms 129.537 ms 6 * prs-bb1-link.ip.twelve99.net (62.115.123.13) 127.047 ms * 7 ldn-bb1-link.ip.twelve99.net (62.115.135.24) 56.178 ms 53.879 ms 54.535 ms 8 nyk-bb2-link.ip.twelve99.net (62.115.113.20) 132.087 ms 132.434 ms 132.604 ms 9 nyk-b3-link.ip.twelve99.net (62.115.139.151) 130.013 ms 127.570 ms 128.564 ms 10 nyi-ic345091-nyk-b3.ip.twelve99-cust.net (62.115.175.141) 124.704 ms 124.851 ms 124.232 ms 11 64.147.115.3 (64.147.115.3) 139.984 ms 141.058 ms 139.911 ms 12 cs80.cs99new.v.ewr.nyinternet.net (96.47.77.214) 143.101 ms 142.207 ms 142.255 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * *
Hmmm ... Please give me suggestion how to locate the problem?
-
What happens if you just try to fetch a file from there?:
[2.6.0-DEVELOPMENT][admin@26dev.stevew.lan]/root: fetch -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211005.0100.pkg /dev/null 86 MB 5648 kBps 16s
Steve
-
@stephenw10 said in VERY slow System Update:
What happens if you just try to fetch a file from there?:
[2.6.0-DEVELOPMENT][admin@26dev.stevew.lan]/root: fetch -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211005.0100.pkg /dev/null 86 MB 5648 kBps 16s
Steve
fetch: https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211005.0100.pkg: Not Found /dev/null 0 B 0 Bps 00s fetch: 86: No such file or directory
-
Those files change every time there's a new build so you need to use one that currently exists.
[22.01-DEVELOPMENT][root@2100-2.stevew.lan]/root: fetch -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211007.1158.pkg /dev/null 86 MB 6686 kBps 13s
-
Do you have IPv6 on that system?
I think I may have just hit this on a system that does. Can you test disabling IPv6 if so?
Steve
-
@stephenw10 said in VERY slow System Update:
Those files change every time there's a new build so you need to use one that currently exists.
[22.01-DEVELOPMENT][root@2100-2.stevew.lan]/root: fetch -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211007.1158.pkg /dev/null 86 MB 6686 kBps 13s
[2.6.0-DEVELOPMENT][root@gamma-fw-dev.local.lan]/root: fetch -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211007.1158.pkg /dev/null 0% of 86 MB 7368 Bps 03h24m
-
@stephenw10 said in VERY slow System Update:
Do you have IPv6 on that system?
I think I may have just hit this on a system that does. Can you test disabling IPv6 if so?
Steve
In System / Advanced / Networking ?
Yes, I try to turn OFF all about IPv6. Even restart, but nothing changed, still SLOWWW
P.S. In the location where this pfSense installed most of ISP unable to routing IPv6, clearly say "99,9% of ISPs in this area IPv4 only"
-
Mmm, not that then. It would fail to get that file with fetch too. I assume that firewall doesn't actually have IPv6 connectivity at all?
What happens if you run
pkg-static -d up-date
?
It complete that in a few seconds. Does it stall anywhere?Steve
-
@stephenw10 said in VERY slow System Update:
Mmm, not that then. It would fail to get that file with fetch too. I assume that firewall doesn't actually have IPv6 connectivity at all?
What happens if you run
pkg-static -d up-date
?pkg-static -d update
[2.6.0-DEVELOPMENT][gamma-fw-dev.local.lan]/root: pkg-static -d update DBG(1)[52270]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[52270]> PkgRepo: verifying update for pfSense-core DBG(1)[52270]> Pkgrepo, begin update of '/root/var/db/pkg/repo-pfSense-core.sqlite' DBG(1)[52270]> Request to fetch pkg+https://packages-beta.netgate.com/packages/pfSense_master_amd64-core/meta.conf DBG(1)[52270]> opening libfetch fetcher DBG(1)[52270]> Fetch > libfetch: connecting DBG(1)[52270]> Fetch: fetching from: https://files00.netgate.com/packages/pfSense_master_amd64-core/meta.conf with opts "i" DBG(1)[52270]> Fetch: fetcher chosen: https DBG(1)[52270]> Request to fetch pkg+https://packages-beta.netgate.com/packages/pfSense_master_amd64-core/packagesite.pkg DBG(1)[52270]> opening libfetch fetcher DBG(1)[52270]> Fetch > libfetch: connecting DBG(1)[52270]> Fetch: fetching from: https://files00.netgate.com/packages/pfSense_master_amd64-core/packagesite.pkg with opts "i" DBG(1)[52270]> Fetch: fetcher chosen: https DBG(1)[52270]> Request to fetch pkg+https://packages-beta.netgate.com/packages/pfSense_master_amd64-core/packagesite.txz DBG(1)[52270]> opening libfetch fetcher DBG(1)[52270]> Fetch > libfetch: connecting DBG(1)[52270]> Fetch: fetching from: https://files00.netgate.com/packages/pfSense_master_amd64-core/packagesite.txz with opts "i" DBG(1)[52270]> Fetch: fetcher chosen: https pfSense-core repository is up to date. Updating pfSense repository catalogue... DBG(1)[52270]> PkgRepo: verifying update for pfSense DBG(1)[52270]> Pkgrepo, begin update of '/root/var/db/pkg/repo-pfSense.sqlite' DBG(1)[52270]> Request to fetch pkg+https://packages-beta.netgate.com/packages/pfSense_master_amd64-pfSense_devel/meta.conf DBG(1)[52270]> opening libfetch fetcher DBG(1)[52270]> Fetch > libfetch: connecting DBG(1)[52270]> Fetch: fetching from: https://files01.netgate.com/packages/pfSense_master_amd64-pfSense_devel/meta.conf with opts "i" DBG(1)[52270]> Fetch: fetcher chosen: https DBG(1)[52270]> Request to fetch pkg+https://packages-beta.netgate.com/packages/pfSense_master_amd64-pfSense_devel/packagesite.pkg DBG(1)[52270]> opening libfetch fetcher DBG(1)[52270]> Fetch > libfetch: connecting DBG(1)[52270]> Fetch: fetching from: https://files01.netgate.com/packages/pfSense_master_amd64-pfSense_devel/packagesite.pkg with opts "i" DBG(1)[52270]> Fetch: fetcher chosen: https DBG(1)[52270]> Request to fetch pkg+https://packages-beta.netgate.com/packages/pfSense_master_amd64-pfSense_devel/packagesite.txz DBG(1)[52270]> opening libfetch fetcher DBG(1)[52270]> Fetch > libfetch: connecting DBG(1)[52270]> Fetch: fetching from: https://files01.netgate.com/packages/pfSense_master_amd64-pfSense_devel/packagesite.txz with opts "i" DBG(1)[52270]> Fetch: fetcher chosen: https pfSense repository is up to date. All repositories are up to date.
It complete that in a few seconds. Does it stall anywhere?
No stall.
But no few sec
approx 12sec to completeThank You for help.
-
iperf3 from the pfSense itself also good
(it was downloading some updates from office lan, so 67-75 Mbits/sec is ok in this case)[2.6.0-DEVELOPMENT][root@gamma-fw-dev.local.lan]/root: iperf3 -c iperf.scottlinux.com Connecting to host iperf.scottlinux.com, port 5201 [ 5] local AAA.BBB.CCC.DDD port 17173 connected to 45.33.39.39 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 348 KBytes 2.85 Mbits/sec 0 122 KBytes [ 5] 1.00-2.00 sec 4.75 MBytes 39.9 Mbits/sec 0 3.00 MBytes [ 5] 2.00-3.00 sec 8.46 MBytes 71.0 Mbits/sec 0 3.00 MBytes [ 5] 3.00-4.00 sec 8.59 MBytes 72.1 Mbits/sec 0 3.00 MBytes [ 5] 4.00-5.00 sec 8.51 MBytes 71.4 Mbits/sec 0 3.00 MBytes [ 5] 5.00-6.00 sec 8.29 MBytes 69.5 Mbits/sec 0 3.00 MBytes [ 5] 6.00-7.00 sec 8.33 MBytes 69.9 Mbits/sec 0 3.00 MBytes [ 5] 7.00-8.00 sec 8.42 MBytes 70.7 Mbits/sec 0 3.00 MBytes [ 5] 8.00-9.00 sec 8.59 MBytes 72.1 Mbits/sec 0 3.00 MBytes [ 5] 9.00-10.00 sec 8.24 MBytes 69.1 Mbits/sec 0 3.00 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 72.5 MBytes 60.8 Mbits/sec 0 sender [ 5] 0.00-10.20 sec 72.5 MBytes 59.7 Mbits/sec receiver iperf Done.
-
So, to confirm, you do not have a routable IPv6 IP on that firewall?
Just to be sure try running:
fetch -4 -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211008.0500.pkg
Compare that with:
fetch -6 -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211008.0500.pkg
The issue I hit yesterday was a local setting I had forgotten about.
As far as I know there are no issues with the repo.Steve
-
@stephenw10 said in VERY slow System Update:
So, to confirm, you do not have a routable IPv6 IP on that firewall?
Just to be sure try running:
fetch -4 -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211008.0500.pkg
[2.6.0-DEVELOPMENT][root@gamma-fw-dev.local.lan]/root: fetch -4 -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211008.0500.pkg /dev/null 0% of 86 MB 6851 Bps 03h35m
Compare that with:
fetch -6 -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211008.0500.pkg
The issue I hit yesterday was a local setting I had forgotten about.
As far as I know there are no issues with the repo.[2.6.0-DEVELOPMENT][root@gamma-fw-dev.local.lan]/root: fetch -6 -o /dev/null https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211008.0500.pkg fetch: https://files00.netgate.com/packages/pfSense_master_amd64-core/All/pfSense-kernel-debug-pfSense-2.6.0.a.20211008.0500.pkg: No route to host
-
@stephenw10 said in VERY slow System Update:
The issue I hit yesterday was a local setting I had forgotten about.
As far as I know there are no issues with the repo.More that sure the repo are OK
-
Hmm, so something specifically to that host from where you are.
MTU problem?
You see the same in files00 and files01?
-
@stephenw10 said in VERY slow System Update:
Hmm, so something specifically to that host from where you are.
MTU problem?
I do not make any modification in NIC settings.
You see the same in files00 and files01?
Yes, the same
-
@sergei_shablovsky said in VERY slow System Update:
I do not make any modification in NIC settings.
That doesn't mean something didn't change in the route though.
What do you see in a packet capture of the traffic? A lot of fragmentation perhaps?
-
@stephenw10 said in VERY slow System Update:
Hmm, so something specifically to that host from where you are.
To this pfSense we have 2 WAN with static IPs from local ISP.
MTU problem?
I was a little play with this: 1500, 1350 - not solving my problem.
-
@stephenw10 said in VERY slow System Update:
@sergei_shablovsky said in VERY slow System Update:
I do not make any modification in NIC settings.
That doesn't mean something didn't change in the route though.
What do you see in a packet capture of the traffic? A lot of fragmentation perhaps?
But if fragmentation or something miss-working on a TCP level, iperf also could be affected. But iperf working as many days before - the same measurement.
Please point me with sample what You mean about “measuring level of fragmentation by packet capturing”.
Thank You for help. This issue slowly make me sad...
-
Indeed iperf would also be affected if it was going over the same route but that's unlikely. We ca say whatever part of the route that is shared does not have a problem.
Run a pcap for traffic to/from the update server. Look for fragmentation.
Steve
-
@stephenw10 said in VERY slow System Update:
Indeed iperf would also be affected if it was going over the same route but that's unlikely. We ca say whatever part of the route that is shared does not have a problem.
Run a pcap for traffic to/from the update server. Look for fragmentation.
Thank You, Steve for suggestions!
No fragmentation, checked at the first step.
BTW, when doing “pkg upgrade” from command line on local console, after downloading first packet the output from pkg looks like stopped. No, system working and no freeze, all other LANs working...
I even trying to “pkg unlock -a”, but this also no impact on situation...
-
So it sends and then never receives a reply? And doesn't just timeout?
That sounds more like something broken in the pkg system locally.
Steve
-
@stephenw10 said in VERY slow System Update:
So it sends and then never receives a reply? And doesn't just timeout?
Thank You for patience with this case, Steve.
Not looks like this.
When come into local shell, trying to make manually
pkg upgrade
after depositories checks, the packet downloading process starting, even first .pkg in Queue downloaded fast (at 70-90Mb/s), but after this first .pkg (or just from start of Queue), the download speed on screen indicated as
16,4kB/s 01:43:17ETA
(this is for pfSense-kernel-pfSense-2.6.0.a.20211029.0500.pkg fetching for example)
and on a big .pkg size connection closed, may be from the NetGate updates server sideLet me remind, any other downloads or third party .pkg downloaded on full available bandwidth, I test this more than triple-twice.
That sounds more like something broken in the pkg system locally.
I also thinking about this, so try to pkg unlock -a, purging pkg cache....
But still unsuccessfully...[UPDATE]
Today I have a little bit more time to make some experiments. And found that the SLOW speed only for 2nd, 3rd, and down the list .pkg files, but FIRST FILE ALWAYS DOWNLOADING AT FULL AVAILABLE BANDWITH. (i.e. from 24 to 80MB/s).q -
Hmm, that really looks like a routing issue or an IPv6 issue. But I believe we already ruled that out?
Do you have a VPN or some other tunnel you could try to route that traffic across as a test?
Steve
-
@stephenw10
Today I have a little bit more time to make some experiments. And found that the SLOW speed only for 2nd, 3rd, and down the list .pkg files, but FIRST FILE ALWAYS DOWNLOADING AT FULL AVAILABLE BANDWITH. (i.e. from 24 to 80MB/s). -
@stephenw10 said in VERY slow System Update:
Hmm, that really looks like a routing issue or an IPv6 issue. But I believe we already ruled that out?
The routing - is the first that I thinking on. But if something wrong with routing **why this not impact on any other traffic from/to any other destination/source.
Do you have a VPN or some other tunnel you could try to route that traffic across as a test?
I'm a little bit stupid today, could You be so please to write in details what exactly you mean and how doing that? Thx a lot!!!
-
If there is something specifically in the route that traffic is taking that throttling it then routing if over a VPN will likely change that route and might allow full speed repeatedly. It would at least prove the routing issue theory.
I have an OpenVPN tunnel setup to an instance in GCP for that purpose. But almost anywhere would change the route to test it.
Steve
-
@stephenw10 said in VERY slow System Update:
If there is something specifically in the route that traffic is taking that throttling it then routing if over a VPN will likely change that route and might allow full speed repeatedly. It would at least prove the routing issue theory.
I have an OpenVPN tunnel setup to an instance in GCP for that purpose. But almost anywhere would change the route to test it.
Thank You for all help here, Stephen!
Task SOLVED, due the source of this sow pfSense update was in speed/control settings for NIC's interface: need to be changed from 100TX full-duplex to 100TX (mean 100TX half-duplex).
After this speed of update come from fixed 16,4k to 1,5-2,5M.I do not know why *the exactly pfSense updates are so slow and no other netflow affected”, but anyway, this certain issue closed and finding the source of problem come to another level, please see Errors In, but no Errors Out and No Collisions on both WAN.
-
@sergei_shablovsky said in [SOLVED] - VERY slow System Update:
[UPDATE]
Today I have a little bit more time to make some experiments. And found that the SLOW speed only for 2nd, 3rd, and down the list .pkg files, but FIRST FILE ALWAYS DOWNLOADING AT FULL AVAILABLE BANDWITH. (i.e. from 24 to 80MB/s).qNeed to note about this “full speed” I make wrong conclusion: the speed on screen are just measured from already readed cache, so extremely hi-speed to view possible, like 1,200Mb on 100M physical connection & port speed. ;)
But the real speed are with the same limitation 16,4kBs.I make some extra experiments on this server:
trying to download the 420Mb full pfSense install by fetchfetch -v -o /dev/null https://snapshots.netgate.com/amd64/pfSense_master/installer/pfSense-CE-memstick-2.6.0-DEVELOPMENT-amd64-latest.img.gz
The speed and ETA on screen was:
6770 Bps 18h08m
I conclude this speed are max per one connect from Netgate hosting provider.
-
@sergei_shablovsky said in [SOLVED] - VERY slow System Update:
I conclude this speed are max per one connect from Netgate hosting provider.
Not true at all.. Maybe from your ISP and peering issue to there.. But its clearly not a "netgate" connection or server issue.
-
@johnpoz said in [SOLVED] - VERY slow System Update:
@sergei_shablovsky said in [SOLVED] - VERY slow System Update:
I conclude this speed are max per one connect from Netgate hosting provider.
Not true at all.. Maybe from your ISP and peering issue to there.. But its clearly not a "netgate" connection or server issue.
I also love Netgate ;)
And really thankful for their support the pfSense's User Community.But as I wrote before in this tread (and other see Errors In, but no Errors Out and No Collisions on both WAN), the iperf3 to different geographic servers (USA, UK, France, HonKong, Latvia, ...) in different regions give me 70-88Mb/s on 100M physical connection.
The SAME ISP and the SAME physical connection. -
@sergei_shablovsky said in [SOLVED] - VERY slow System Update:
the iperf3 to different geographic servers (USA, UK, France, HonKong, Latvia, ...)
How does that have anything to do with downloading from the netgate servers?
-
@johnpoz said in [SOLVED] - VERY slow System Update:
How does that have anything to do with downloading from the netgate servers?
Shaping on some AS.
Because in fact iperf3 give me ~80Mb/s worldwide, but fetch from Netgate server - only 16.4kB/s on same physical connection.
-
Downloaded this one, and got around 2.5 MB/s
https://snapshots.pfsense.org/amd64/pfSense_master/installer/pfSense-CE-2.6.0-DEVELOPMENT-amd64-20211104-0500.iso.gz
-
@ciscox said in [SOLVED] - VERY slow System Update:
Downloaded this one, and got around 2.5 MB/s
https://snapshots.pfsense.org/amd64/pfSense_master/installer/pfSense-CE-2.6.0-DEVELOPMENT-amd64-20211104-0500.iso.gz
Slowly we collecting pfSense speed on images download worldwide ;)
-
@stephenw10 said in [SOLVED] - VERY slow System Update:
there is something specifically in the route that traffic is taking that throttling
That’s what about this post ;)
Even on clean pfSense installation (no any rules, nothing) on that particular machinepkg upgrade
or
pkg update
where fetch command used
give me 16,4KB/s ;)
-
On an old pfSense 1.x - and upgraded gradually to 2.5.2 CE - so probably not clean at all :
20Mbits is my WAN-down.
-
@gertjan said in VERY slow System Update:
On an old pfSense 1.x - and upgraded gradually to 2.5.2 CE - so probably not clean at all :
20Mbits is my WAN-down.
Thank You!
Is this graph only for fetch image from Netgate server (I mean dev version, nor mirrors in US and other countries) ? -
@sergei_shablovsky
The answer is : no.
My iPhone also decides to update itself to 15.1 (2 GB download) and the rest of the companies network was also actif.I also use an IPv6 connection, that tunnel IPv4 packets out over the WAN with IPv6 traffic in it. So my IPv6 goes over the IPv4 WAN (technically, I have a double WAN setup).
I've shut down our main switch, so I was using the only PC on the network :
Test again :[2.5.2-RELEASE][admin@pfsense.my-local-network.net]/root: fetch -v -o /dev/null https://snapshots.netgate.com/amd64/pfSense_master/installer/pfSense-CE-memstick-2.6.0-DEVELOPMENT-amd64-latest.img.gz resolving server address: snapshots.netgate.com:443 SSL options: 82004854 Peer verification enabled Using CA cert file: /usr/local/etc/ssl/cert.pem Verify hostname TLSv1.2 connection established using ECDHE-RSA-AES256-GCM-SHA384 Certificate subject: /CN=*.netgate.com Certificate issuer: /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA requesting https://snapshots.netgate.com/amd64/pfSense_master/installer/pfSense-CE-memstick-2.6.0-DEVELOPMENT-amd64-latest.img.gz remote size / mtime: 439979895 / 1636700812 /dev/null 419 MB 1868 kBps 03m50s
That is close to 19 Mbits / sec, my ADSL down bandwidth.
It was using IPv4 - as IPv6 (ipv6.he.net) would be slower for me.