(Posted to both Win-11 and Linux groups)You send a ton of data one way and time it, then the other way. Seems simple to me.
Some years ago, The Australian Government set up a "company" to connect everyone up to the Internet. Commercial Buildings would get Fibre-to-the-Building whilst Homes would get Fibre-to-the-Node then
twisted pair to the Home .... unless the Home-owner paid the extra bucks
to get Fibre-to-the-Home.
Now, various Domestic-type ISP's are offering to upgrade anybody to Fibre-to-the-Home for not much cost. My sister is undergoing this
upgrade at the moment, so this has prompted my question.
Which got me thinking ..... How do "they" Speed-test Internet Links?? .. particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest, are ....
https://www.bing.com/search?q=Internet%20speed%20test&form=B00032&ocid=SettingsHAQ-BingIA&pageId=SettingsPageNetworkManageAdapterOptions&mkt=en-US
Ping 23ms
Download 12.66 Mb/s
Upload 0.93 Mb/s
O.K., so these speeds, now-a-days, might not be anything to Write home
about but they are what they are .... but how do 'they' seperate how
much time is spent Downloading from my Computer and how much time is
spent Uploading to my Computer.
I mean .... My Computer starts a check, the signal goes somewhere,
starts a clock and a signal comes back to my Computer and, maybe, my
computer sends another signal to stop the Clock .... so the signal does
at least one full circuit .... but how do "they" seperate the two halves times and, therefore, the speeds each way??
[...]
Which got me thinking ..... How do "they" Speed-test Internet Links?? .. particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest [...]
On 9/8/25 7:42 AM, Daniel70 wrote:
(Posted to both Win-11 and Linux groups)
Some years ago, The Australian Government set up a "company" to connect
everyone up to the Internet. Commercial Buildings would get
Fibre-to-the-Building whilst Homes would get Fibre-to-the-Node then
twisted pair to the Home .... unless the Home-owner paid the extra bucks
to get Fibre-to-the-Home.
Now, various Domestic-type ISP's are offering to upgrade anybody to
Fibre-to-the-Home for not much cost. My sister is undergoing this
upgrade at the moment, so this has prompted my question.
Which got me thinking ..... How do "they" Speed-test Internet Links?? ..
particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest, are ....
https://www.bing.com/search?q=Internet%20speed%20test&form=B00032&ocid=SettingsHAQ-BingIA&pageId=SettingsPageNetworkManageAdapterOptions&mkt=en-US
Ping 23ms
Download 12.66 Mb/s
Upload 0.93 Mb/s
O.K., so these speeds, now-a-days, might not be anything to Write home
about but they are what they are .... but how do 'they' seperate how
much time is spent Downloading from my Computer and how much time is
spent Uploading to my Computer.
I mean .... My Computer starts a check, the signal goes somewhere,
starts a clock and a signal comes back to my Computer and, maybe, my
computer sends another signal to stop the Clock .... so the signal does
at least one full circuit .... but how do "they" seperate the two halves
times and, therefore, the speeds each way??
You send a ton of data one way and time it, then the other way. Seems simple to me.
How do you test read and write speed on a thumb drive or hard drive?
On 2025-09-08, Daniel70 wrote:
[...]
Which got me thinking ..... How do "they" Speed-test Internet Links?? ..
particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a file of known
size (say 100 MiB), and then sending it back. Exact file size will vary
by testing provider, but essentially it's just this:
Download start = 0.00
Download end = [TIME]
File size / TIME = X Mbit / sec
Upload Start = 0.00
Upload end = [TIME]
File size / TIME = Y Mbit / Sec
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...]
Which got me thinking ..... How do "they" Speed-test Internet Links?? .. >>> particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a file of known
size (say 100 MiB), and then sending it back. Exact file size will vary
by testing provider, but essentially it's just this:
Download start = 0.00
Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the entire file
(i.e. Download end time)??
Similarly, how does the distant end know when my computer started the
Upload Start = 0.00
Upload end = [TIME]
File size / TIME = Y Mbit / Sec
Upload (Upload start time)??
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...]
Which got me thinking ..... How do "they" Speed-test Internet Links?? .. >>> particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a file of known
size (say 100 MiB), and then sending it back. Exact file size will vary
by testing provider, but essentially it's just this:
Download start = 0.00
Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the entire file
(i.e. Download end time)??
If I START NOW how does the clock at the other end know when to START that clock. Sure, they'll know when to STOP that clock....
Conversely, when the distant end STARTs to send infomation, the know when
to start that clock .... but how do they know when they should STOP that clock??
Daniel,
If I START NOW how does the clock at the other end know when to START that >> clock. Sure, they'll know when to STOP that clock....
Conversely, when the distant end STARTs to send infomation, the know when
to start that clock .... but how do they know when they should STOP that
clock??
Thats the nice thing about TCP (as in: TCP/IP) communications : When the receiver finishes receiving a block of data it will send a signal back that the block is received correctly, and the next block may be send - or that,
as the sending-side indicated, the last block was received.
iow, *both* sides can start timers and get an accurate duration of the transmission.
Regards,
Rudy Wieser
On 8/09/2025 11:50 pm, R.Wieser wrote:
Daniel,But both sides only know when a FULL CYCLE has been completed .... not
If I START NOW how does the clock at the other end know when to START that >>> clock. Sure, they'll know when to STOP that clock....
Conversely, when the distant end STARTs to send infomation, the know when >>> to start that clock .... but how do they know when they should STOP that >>> clock??
Thats the nice thing about TCP (as in: TCP/IP) communications : When the
receiver finishes receiving a block of data it will send a signal back that >> the block is received correctly, and the next block may be send - or that, >> as the sending-side indicated, the last block was received.
iow, *both* sides can start timers and get an accurate duration of the
transmission.
Regards,
Rudy Wieser
two half cycles.
But both sides only know when a FULL CYCLE has been completed .... not
two half cycles.
On 8/09/2025 10:10 pm, Alan K. wrote:
On 9/8/25 7:42 AM, Daniel70 wrote:
You send a ton of data one way and time it, then the other way. SeemsIf I START NOW how does the clock at the other end know when to START
simple to me.
How do you test read and write speed on a thumb drive or hard drive?
that clock. Sure, they'll know when to STOP that clock.
Conversely, when the distant end STARTs to send infomation, the know
when to start that clock .... but how do they know when they should STOP that clock??
On Mon, 08 Sep 2025 23:24:12 +1000, Daniel70 wrote:
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...]
Which got me thinking ..... How do "they" Speed-test Internet Links?? .. >>>> particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a file of known
size (say 100 MiB), and then sending it back. Exact file size will vary >>> by testing provider, but essentially it's just this:
Download start = 0.00
Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the entire file
(i.e. Download end time)??
Similarly, how does the distant end know when my computer started the
Upload Start = 0.00
Upload end = [TIME]
File size / TIME = Y Mbit / Sec
Upload (Upload start time)??
The transfers typically use TCP, and that protocol includes feedback
from the receiving end as to whether or not it has received the data
sent. Typically, this feedback is in small enough packets that transmission latency doesn't affect the overall throughput measurement enough to
matter.
In theory, only one end has to make the timing measurements; It can
be the sending end, or the receiving end.
For sending-end measurement, the sender
- starts the clock
- sends a known amount of data to the receiver, obeying the receiver's
TCP flow-control requests
- stops the clock at the TCP FIN/FIN-ACK end-of-data acknowledged
- computes elapsed time
- computes upload transfer rate (known amount of data / computed elapsed time)
For receiving-end measurement, the receiver
- waits for the TCP connection
- starts the clock
- receives the data, counting the volume as it goes
- stops the clock at the TCP FIN/FIN-ACK end-of-data received signal
- computes elapsed time
- computes download transfer rate (counted amount of data / computed elapsed time)
With those web-page throughput estimators (https://www.speedtest.net, for example),
the throughput computation usually occurs at the web server, with the webpage providing
javascript (or other code that will execute on the client system) to either sink the TCP connection and data being sent (from the web server to the client system
for the upload test, or source the TCP connection and data (from the client system to
the web server) being sent for the download test.
HTH
On 8/09/2025 11:43 pm, Lew Pitcher wrote:
On Mon, 08 Sep 2025 23:24:12 +1000, Daniel70 wrote:
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...]
Which got me thinking ..... How do "they" Speed-test Internet Links?? .. >>>>> particularly How do 'they' distinguish the Up-link TIME from the
Down-link TIME?? e.g. my current speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a file of known >>>> size (say 100 MiB), and then sending it back. Exact file size will vary >>>> by testing provider, but essentially it's just this:
Download start = 0.00
Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the entire file
(i.e. Download end time)??
Similarly, how does the distant end know when my computer started the
Upload Start = 0.00
Upload end = [TIME]
File size / TIME = Y Mbit / Sec
Upload (Upload start time)??
The transfers typically use TCP, and that protocol includes feedback
from the receiving end as to whether or not it has received the data
sent. Typically, this feedback is in small enough packets that transmission >> latency doesn't affect the overall throughput measurement enough to
matter.
In theory, only one end has to make the timing measurements; It can
be the sending end, or the receiving end.
For sending-end measurement, the sender
- starts the clock
- sends a known amount of data to the receiver, obeying the receiver's
TCP flow-control requests
- stops the clock at the TCP FIN/FIN-ACK end-of-data acknowledged
- computes elapsed time
- computes upload transfer rate (known amount of data / computed elapsed time)
O.K., so my computer sends my Start time, then a certain amount of Data (1kB, maybe), and then sends my computers End Time. So including the
clock times, totaling, maybe, 1.1kB.
The Distant computer determines how long it took for my computer to send those three Datas (1.1kB) ..... but is it really able to determine how
long it took to get that 1.1kB across the Wire/Cable/Satellite/Whatever connecting medium or just how long it took my Computer to send the data??
For receiving-end measurement, the receiver
- waits for the TCP connection
- starts the clock
- receives the data, counting the volume as it goes
- stops the clock at the TCP FIN/FIN-ACK end-of-data received signal
- computes elapsed time
So the elapsed time (i.e. the time for my computer to actually send the 1.1kB), as measured by the receiving-end device should be the same time
as measured by my Sending Device .... but still doesn't know how long
the data transfer from Me to YOU to happen.
- computes download transfer rate (counted amount of data / computed elapsed time)I don't know if I've done a good enough job of explaining my situation
With those web-page throughput estimators (https://www.speedtest.net, for example),
the throughput computation usually occurs at the web server, with the webpage providing
javascript (or other code that will execute on the client system) to either >> sink the TCP connection and data being sent (from the web server to the client system
for the upload test, or source the TCP connection and data (from the client system to
the web server) being sent for the download test.
HTH
.... just goes to show how confused I am.
But both sides only know when a FULL CYCLE has been completed .... not two half cycles.
(Posted to both Win-11 and Linux groups)
Some years ago, The Australian Government set up a "company" to connect everyone up to the Internet. Commercial Buildings would get Fibre-to-the-Building whilst Homes would get Fibre-to-the-Node then twisted pair to the Home .... unless the Home-owner paid the extra bucks to get Fibre-to-the-Home.
Now, various Domestic-type ISP's are offering to upgrade anybody to Fibre-to-the-Home for not much cost. My sister is undergoing this upgrade at the moment, so this has prompted my question.
Which got me thinking ..... How do "they" Speed-test Internet Links?? .. particularly How do 'they' distinguish the Up-link TIME from the Down-link TIME?? e.g. my current speeds, using Speedtest, are ....
https://www.bing.com/search?q=Internet%20speed%20test&form=B00032&ocid=SettingsHAQ-BingIA&pageId=SettingsPageNetworkManageAdapterOptions&mkt=en-US
Ping 23ms
Download 12.66 Mb/s
Upload 0.93 Mb/s
O.K., so these speeds, now-a-days, might not be anything to Write home about but they are what they are .... but how do 'they' seperate how much time is spent Downloading from my Computer and how much time is spent Uploading to my Computer.
I mean .... My Computer starts a check, the signal goes somewhere, starts a clock and a signal comes back to my Computer and, maybe, my computer sends another signal to stop the Clock .... so the signal does at least one full circuit .... but how do "they" seperate the two halves times and, therefore, the speeds each way??
But how does the distant end know when I have received the entire file
(i.e. Download end time)??
Similarly, how does the distant end know when my computer started the
Upload (Upload start time)??
I don't know if I've done a good enough job of explaining my
situation .... just goes to show how confused I am.
(Posted to both Win-11 and Linux groups)
Some years ago, The Australian Government set up a "company" to connect everyone up to the Internet. Commercial Buildings would get Fibre-to-the-Building whilst Homes would get Fibre-to-the-Node then
twisted pair to the Home .... unless the Home-owner paid the extra bucks
to get Fibre-to-the-Home.
On 2025-09-08, Daniel70 wrote:
On 8/09/2025 11:50 pm, R.Wieser wrote:
Daniel,But both sides only know when a FULL CYCLE has been completed .... not
If I START NOW how does the clock at the other end know when to START that >>>> clock. Sure, they'll know when to STOP that clock....
Conversely, when the distant end STARTs to send infomation, the know when >>>> to start that clock .... but how do they know when they should STOP that >>>> clock??
Thats the nice thing about TCP (as in: TCP/IP) communications : When the >>> receiver finishes receiving a block of data it will send a signal back that >>> the block is received correctly, and the next block may be send - or that, >>> as the sending-side indicated, the last block was received.
iow, *both* sides can start timers and get an accurate duration of the
transmission.
Regards,
Rudy Wieser
two half cycles.
What is a "full" or "half" cycle?
so my computer sends my Start time, then a certain amount of Data (1kB, maybe), and then sends my computers End Time. So including the clock
times, totaling, maybe, 1.1kB.
On 08/09/2025 15.58, Daniel70 wrote:
But both sides only know when a FULL CYCLE has been completed .... not
two half cycles.
If a response not got for a package, you resend that package.
Daniel,
But both sides only know when a FULL CYCLE has been completed .... not two >> half cycles.
Why ?
I can see when I start upload and when it finishes, and in the same way when I get the first block of data of a download and when I get the last one.
And that goes for both sides of the communication.
Regards,
Rudy Wieser
If a response not got for a package, you resend that package.In an Error Detection and Correction situation, yes ....
but what if Distant end is not expecting me to send anything??
Do I just keep sending, ad infinitum??
On Tue, 09 Sep 2025 00:24:30 +1000, Daniel70 wrote:
On 8/09/2025 11:43 pm, Lew Pitcher wrote:
On Mon, 08 Sep 2025 23:24:12 +1000, Daniel70 wrote:
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...] Which got me thinking ..... How do "they" Speed-test
Internet Links?? .. particularly How do 'they' distinguish
the Up-link TIME from the Down-link TIME?? e.g. my current
speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a
file of known size (say 100 MiB), and then sending it back.
Exact file size will vary by testing provider, but
essentially it's just this:
Download start = 0.00 Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the
entire file (i.e. Download end time)??
Similarly, how does the distant end know when my computer
Upload Start = 0.00 Upload end = [TIME]
File size / TIME = Y Mbit / Sec
started the Upload (Upload start time)??
The transfers typically use TCP, and that protocol includes
feedback from the receiving end as to whether or not it has
received the data sent. Typically, this feedback is in small
enough packets that transmission latency doesn't affect the
overall throughput measurement enough to matter.
In theory, only one end has to make the timing measurements; It
can be the sending end, or the receiving end.
For sending-end measurement, the sender - starts the clock -
sends a known amount of data to the receiver, obeying the
receiver's TCP flow-control requests - stops the clock at the TCP
FIN/FIN-ACK end-of-data acknowledged - computes elapsed time -
computes upload transfer rate (known amount of data / computed
elapsed time)
O.K., so my computer sends my Start time, then a certain amount of
Data (1kB, maybe), and then sends my computers End Time. So
including the clock times, totaling, maybe, 1.1kB.
Nope. Your computer neither sends "Start time" nor "End time". It
simply sends data via TCP to the other system.
Your system opens a TCP connection to the OTHER SYSTEM, and when the
OTHER SYSTEM receives that TCP connection request from your system,
the OTHER SYSTEM notes the start time.
As your system sends data, the OTHER SYSTEM receives it, and
measures how much data it received.
When your system finishes sending data, it closes the TCP
connection, which sends a TCP "all done" control message to the OTHER
SYSTEM. When the OTHER SYSTEM receives that "all done" control
message, it records the "End time", computes the elapsed time and
volume of data, and then computes the throughput.
The Distant computer determines how long it took for my computer to
send those three Datas (1.1kB) ..... but is it really able to
determine how long it took to get that 1.1kB across the
Wire/Cable/Satellite/Whatever connecting medium or just how long it
took my Computer to send the data??
Rarely (if ever) have I seen a "speed test" that limits itself to
just 1.1Kb of data. Usually, both sides send megabytes of data. This
is important, as the smaller the data transfer, the larger the gross
error in measurements.
For receiving-end measurement, the receiver - waits for the TCP
connection - starts the clock - receives the data, counting the
volume as it goes - stops the clock at the TCP FIN/FIN-ACK
end-of-data received signal - computes elapsed time
So the elapsed time (i.e. the time for my computer to actually send
the 1.1kB), as measured by the receiving-end device should be the
same time as measured by my Sending Device .... but still doesn't
know how long the data transfer from Me to YOU to happen.
Elapsed time /IS/ "how long the data transfer from Me to YOU" took.
At least for the gross measurements that these "how fast is my
internet" websites offer. If you want some other measurement, you
need to measure in a different way.
- computes download transfer rate (counted amount of data /I don't know if I've done a good enough job of explaining my
computed elapsed time)
With those web-page throughput estimators
(https://www.speedtest.net, for example), the throughput
computation usually occurs at the web server, with the webpage
providing javascript (or other code that will execute on the
client system) to either sink the TCP connection and data being
sent (from the web server to the client system for the upload
test, or source the TCP connection and data (from the client
system to the web server) being sent for the download test.
HTH
situation .... just goes to show how confused I am.
From the sounds of it, you don't want to know "how fast is my
internet". You want to know something like "What is the potential
upper limit of packet transfer in a) my network, b) in the various
networks between me and some other defined system, and c) in the
various networks between me and some other undefined system.
a) Can be answered by looking at the specs for your NIC Neither b)
nor c) can be /reliably/ answered, as they depend on the states of
the other networks in the route from you to that other system.
Internet routing is variable, and there are many networks between you
and the other system, and many routes to get there. How fast can you
get from your home to, say, your local airport? If you travel the
highway, you get one answer, but if you travel the back roads, you
get another. If you go by car, you get a different answer then you
would if you go by bicycle. That's internet routing.
Daniel,
But how does the distant end know when I have received the entire file >>>> (i.e. Download end time)??
As said, the sending-side marks the last to-be-send data-block as being ... well, the last block. :-)
Similarly, how does the distant end know when my computer started the
Upload (Upload start time)??
By receiving the first block of data ?
Mind you, files do *not* get send as a single block, but as a number of smaller blocks.
Regards,
Rudy Wieser
On 9/09/2025 12:05 am, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:I know when I send something out .... and I know when I receive
On 8/09/2025 11:50 pm, R.Wieser wrote:
Daniel,But both sides only know when a FULL CYCLE has been completed .... not
If I START NOW how does the clock at the other end know when to START that...
clock. Sure, they'll know when to STOP that clock.
Conversely, when the distant end STARTs to send infomation, the know when >>>>> to start that clock .... but how do they know when they should STOP that >>>>> clock??
Thats the nice thing about TCP (as in: TCP/IP) communications : When the >>>> receiver finishes receiving a block of data it will send a signal back that
the block is received correctly, and the next block may be send - or that, >>>> as the sending-side indicated, the last block was received.
iow, *both* sides can start timers and get an accurate duration of the >>>> transmission.
Regards,
Rudy Wieser
two half cycles.
What is a "full" or "half" cycle?
something back .... e.g. I made my post at 23:58, yesterday, 08/09/25
and, if I had still been online, I might have received your reply at
0005, 09/09/25 .... so this full cycle took "7 minutes". But I did
receive it now, 20:15, 09/09/25
I know that not a good example for this situation but, hopefully, you
get what I mean by "full" or "half" cycle?
On 9/09/2025 1:08 am, R.Wieser wrote:
Daniel,If I send you Data ...... and I hear nothing back. Do I assume you
But both sides only know when a FULL CYCLE has been completed .... not two >>> half cycles.
Why ?
I can see when I start upload and when it finishes, and in the same way when >> I get the first block of data of a download and when I get the last one.
And that goes for both sides of the communication.
Regards,
Rudy Wieser
received my Data or do I just resend?? After a Minute?? An Hour?? A Day??
On 2025-09-08 16:24, Daniel70 wrote:
I don't know if I've done a good enough job of explaining my situation
.... just goes to show how confused I am.
The speed test measures how long it takes to send a large bunch of data. This is different from the time it takes to send a single packet,
because as you say, the time for the answer to get back to you means you measure double the time. Two trips.
However, the speed test may also show the "ping time". Perhaps "round
ping time". This can be estimated using time stamps, I believe. The ping command does print that info.
On 9/09/2025 1:20 am, R.Wieser wrote:
Daniel,Yes, understood, Rudy, don't start sending second Block until reception
But how does the distant end know when I have received the entire file >>>>> (i.e. Download end time)??
As said, the sending-side marks the last to-be-send data-block as
being ...
well, the last block. :-)
Similarly, how does the distant end know when my computer started the >>>>> Upload (Upload start time)??
By receiving the first block of data ?
Mind you, files do *not* get send as a single block, but as a number of
smaller blocks.
Regards,
Rudy Wieser
of first block acknowledged.
If I send you Data ...... and I hear nothing back. Do I assume you
received my Data or do I just resend?? After a Minute?? An Hour?? A Day??
On 2025-09-09 12:54, Daniel70 wrote:
On 9/09/2025 1:20 am, R.Wieser wrote:
Daniel,Yes, understood, Rudy, don't start sending second Block until
But how does the distant end know when I have received the
entire file (i.e. Download end time)??
As said, the sending-side marks the last to-be-send data-block as
being ... well, the last block. :-)
Similarly, how does the distant end know when my computer
started the Upload (Upload start time)??
By receiving the first block of data ?
Mind you, files do *not* get send as a single block, but as a
number of smaller blocks.
Regards, Rudy Wieser
reception of first block acknowledged.
Hum. Maybe not. I did not study TCP in that detail, but older
protocols would send a number of blocks, say 1, 2, 3, 4 & 5 and start receiving the ACKs after number 3. The receiver says OK to number 1,
fail number 2, Ok number 3... so after a while, out of sequence, the
sender repeats number 2, just after sending number 6.
Daniel70 wrote:
(Posted to both Win-11 and Linux groups)
Some years ago, The Australian Government set up a "company" to
connect everyone up to the Internet. Commercial Buildings would get
Fibre-to-the-Building whilst Homes would get Fibre-to-the-Node then
twisted pair to the Home .... unless the Home-owner paid the extra
bucks to get Fibre-to-the-Home.
Actually, the first suburbs rolled out got FTTH, I was lucky to be in
one. But then under pressure from Murdoch, the government went for the
mixed madness system (FTTN, coax, fixed wireless, whatever shit was in
the spare parts bin....)
Daniel,
If a response not got for a package, you resend that package.In an Error Detection and Correction situation, yes ....
That is what TCP is for.
but what if Distant end is not expecting me to send anything??
Than they would not be listening for something to come in, and you get a status back that your packet could not find an open port to deliver the data at.
Do I just keep sending, ad infinitum??
When you go visit someone unexpectedly, do you just keep knocking on their door until they open(even if they are currently on vacation), or do you
think after a few times knocking that they just might not be home ?
Regards,
Rudy Wieser
On 9/09/2025 12:43 am, Lew Pitcher wrote:
On Tue, 09 Sep 2025 00:24:30 +1000, Daniel70 wrote:
On 8/09/2025 11:43 pm, Lew Pitcher wrote:
On Mon, 08 Sep 2025 23:24:12 +1000, Daniel70 wrote:
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...] Which got me thinking ..... How do "they" Speed-test
Internet Links?? .. particularly How do 'they' distinguish
the Up-link TIME from the Down-link TIME?? e.g. my current
speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a
file of known size (say 100 MiB), and then sending it back.
Exact file size will vary by testing provider, but
essentially it's just this:
Download start = 0.00 Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the
entire file (i.e. Download end time)??
Similarly, how does the distant end know when my computer
Upload Start = 0.00 Upload end = [TIME]
File size / TIME = Y Mbit / Sec
started the Upload (Upload start time)??
The transfers typically use TCP, and that protocol includes
feedback from the receiving end as to whether or not it has
received the data sent. Typically, this feedback is in small
enough packets that transmission latency doesn't affect the
overall throughput measurement enough to matter.
In theory, only one end has to make the timing measurements; It
can be the sending end, or the receiving end.
For sending-end measurement, the sender - starts the clock -
sends a known amount of data to the receiver, obeying the
receiver's TCP flow-control requests - stops the clock at the TCP
FIN/FIN-ACK end-of-data acknowledged - computes elapsed time -
computes upload transfer rate (known amount of data / computed
elapsed time)
O.K., so my computer sends my Start time, then a certain amount of
Data (1kB, maybe), and then sends my computers End Time. So
including the clock times, totaling, maybe, 1.1kB.
Nope. Your computer neither sends "Start time" nor "End time". It
simply sends data via TCP to the other system.
Your system opens a TCP connection to the OTHER SYSTEM, and when the
OTHER SYSTEM receives that TCP connection request from your system,
the OTHER SYSTEM notes the start time.
As your system sends data, the OTHER SYSTEM receives it, and
measures how much data it received.
When your system finishes sending data, it closes the TCP
connection, which sends a TCP "all done" control message to the OTHER
SYSTEM. When the OTHER SYSTEM receives that "all done" control
message, it records the "End time", computes the elapsed time and
volume of data, and then computes the throughput.
YEAP!! Undergerstumble!! But did my data travel via Undersea Co-ax or
via Low Earth orbit Satellite or via High Earth orbit Satellite ..... or
via one of those reflector Panels (supposedly) left on The Moon by the Apollo Astronauts??
[...]
Data transfer time. How loan AFTER I started sending did YOU start receiving??
Most likely .... How do "they" determine my 'Upload Speed' and then how
do "they" determine my "Download Speed"??
[...]
How fast can I get from my Home to the Airport and then back Home?? ;-P
On 2025-09-09, Daniel70 wrote:
On 9/09/2025 12:43 am, Lew Pitcher wrote:
On Tue, 09 Sep 2025 00:24:30 +1000, Daniel70 wrote:
On 8/09/2025 11:43 pm, Lew Pitcher wrote:
On Mon, 08 Sep 2025 23:24:12 +1000, Daniel70 wrote:
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...] Which got me thinking ..... How do "they" Speed-test
Internet Links?? .. particularly How do 'they' distinguish
the Up-link TIME from the Down-link TIME?? e.g. my current
speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a
file of known size (say 100 MiB), and then sending it back.
Exact file size will vary by testing provider, but
essentially it's just this:
Download start = 0.00 Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the
entire file (i.e. Download end time)??
Similarly, how does the distant end know when my computer
Upload Start = 0.00 Upload end = [TIME]
File size / TIME = Y Mbit / Sec
started the Upload (Upload start time)??
The transfers typically use TCP, and that protocol includes
feedback from the receiving end as to whether or not it has
received the data sent. Typically, this feedback is in small
enough packets that transmission latency doesn't affect the
overall throughput measurement enough to matter.
In theory, only one end has to make the timing measurements; It
can be the sending end, or the receiving end.
For sending-end measurement, the sender - starts the clock -
sends a known amount of data to the receiver, obeying the
receiver's TCP flow-control requests - stops the clock at the TCP
FIN/FIN-ACK end-of-data acknowledged - computes elapsed time -
computes upload transfer rate (known amount of data / computed
elapsed time)
O.K., so my computer sends my Start time, then a certain amount of
Data (1kB, maybe), and then sends my computers End Time. So
including the clock times, totaling, maybe, 1.1kB.
Nope. Your computer neither sends "Start time" nor "End time". It
simply sends data via TCP to the other system.
Your system opens a TCP connection to the OTHER SYSTEM, and when the
OTHER SYSTEM receives that TCP connection request from your system,
the OTHER SYSTEM notes the start time.
As your system sends data, the OTHER SYSTEM receives it, and
measures how much data it received.
When your system finishes sending data, it closes the TCP
connection, which sends a TCP "all done" control message to the OTHER
SYSTEM. When the OTHER SYSTEM receives that "all done" control
message, it records the "End time", computes the elapsed time and
volume of data, and then computes the throughput.
YEAP!! Undergerstumble!! But did my data travel via Undersea Co-ax or
via Low Earth orbit Satellite or via High Earth orbit Satellite ..... or
via one of those reflector Panels (supposedly) left on The Moon by the
Apollo Astronauts??
It doesn't matter - throughput is not latency.
If I'm receiving from you:
1. I know I got the first packet at (UNIX TIME) 1757418187
2. I know I got the last packet at (UNIX TIME) 1757418287
3. I know the file size was 100 MB
4. Therefore I calculate the rate as
100MB / (1757418287 - 1757418187)
800Mbit / 100 sec = 8 mbit/sec
Or if I'm sending to you
1. I know I sent the first packet at (UNIX TIME) 1757418187
2. I know I sent the last packet at (UNIX TIME) 1757418287
2.1 I got the last ACK 20 milliseconds later, and throw it away because
it doesn't matter.
3. I know the file size was 100MB
5. Therefore I calculate the rate as
100 MB / (1757418287 - 1757418187)
800 Mbit / 100 sec = 8 mbit / sec
[...]
Data transfer time. How loan AFTER I started sending did YOU start
receiving??
For the most part, latency doesn't matter -- we're talking some tens of milliseconds for a full round trip against some tens or hundreds of
seconds to transfer the test file.
Most likely .... How do "they" determine my 'Upload Speed' and then how
do "they" determine my "Download Speed"??
We've told you a dozen times, you're just not listening.
[...]
How fast can I get from my Home to the Airport and then back Home?? ;-P
That would be the RTT / Latency, and doesn't matter when you're asking "what's the best way to get me, my 10 closest friends, all our luggage,
and two dogs to the airport?"
On 2025-09-09, Daniel70 wrote:
On 9/09/2025 12:43 am, Lew Pitcher wrote:
On Tue, 09 Sep 2025 00:24:30 +1000, Daniel70 wrote:
On 8/09/2025 11:43 pm, Lew Pitcher wrote:
On Mon, 08 Sep 2025 23:24:12 +1000, Daniel70 wrote:
On 8/09/2025 10:21 pm, Dan Purgert wrote:
On 2025-09-08, Daniel70 wrote:
[...] Which got me thinking ..... How do "they" Speed-test
Internet Links?? .. particularly How do 'they' distinguish
the Up-link TIME from the Down-link TIME?? e.g. my current
speeds, using Speedtest [...]
For the most part, a speedtest works by you downloading a
file of known size (say 100 MiB), and then sending it back.
Exact file size will vary by testing provider, but
essentially it's just this:
Download start = 0.00 Download end = [TIME]
File size / TIME = X Mbit / sec
But how does the distant end know when I have received the
entire file (i.e. Download end time)??
Similarly, how does the distant end know when my computer
Upload Start = 0.00 Upload end = [TIME]
File size / TIME = Y Mbit / Sec
started the Upload (Upload start time)??
The transfers typically use TCP, and that protocol includes
feedback from the receiving end as to whether or not it has
received the data sent. Typically, this feedback is in small
enough packets that transmission latency doesn't affect the
overall throughput measurement enough to matter.
In theory, only one end has to make the timing measurements; It
can be the sending end, or the receiving end.
For sending-end measurement, the sender - starts the clock -
sends a known amount of data to the receiver, obeying the
receiver's TCP flow-control requests - stops the clock at the TCP
FIN/FIN-ACK end-of-data acknowledged - computes elapsed time -
computes upload transfer rate (known amount of data / computed
elapsed time)
O.K., so my computer sends my Start time, then a certain amount of
Data (1kB, maybe), and then sends my computers End Time. So
including the clock times, totaling, maybe, 1.1kB.
Nope. Your computer neither sends "Start time" nor "End time". It
simply sends data via TCP to the other system.
Your system opens a TCP connection to the OTHER SYSTEM, and when the
OTHER SYSTEM receives that TCP connection request from your system,
the OTHER SYSTEM notes the start time.
As your system sends data, the OTHER SYSTEM receives it, and
measures how much data it received.
When your system finishes sending data, it closes the TCP
connection, which sends a TCP "all done" control message to the OTHER
SYSTEM. When the OTHER SYSTEM receives that "all done" control
message, it records the "End time", computes the elapsed time and
volume of data, and then computes the throughput.
YEAP!! Undergerstumble!! But did my data travel via Undersea Co-ax or
via Low Earth orbit Satellite or via High Earth orbit Satellite ..... or
via one of those reflector Panels (supposedly) left on The Moon by the
Apollo Astronauts??
It doesn't matter - throughput is not latency.
If I'm receiving from you:
1. I know I got the first packet at (UNIX TIME) 1757418187
2. I know I got the last packet at (UNIX TIME) 1757418287
3. I know the file size was 100 MB
4. Therefore I calculate the rate as
100MB / (1757418287 - 1757418187)
800Mbit / 100 sec = 8 mbit/sec
Or if I'm sending to you
1. I know I sent the first packet at (UNIX TIME) 1757418187
2. I know I sent the last packet at (UNIX TIME) 1757418287
2.1 I got the last ACK 20 milliseconds later, and throw it away because
it doesn't matter.
3. I know the file size was 100MB
5. Therefore I calculate the rate as
100 MB / (1757418287 - 1757418187)
800 Mbit / 100 sec = 8 mbit / sec
[...]
Data transfer time. How loan AFTER I started sending did YOU start
receiving??
For the most part, latency doesn't matter -- we're talking some tens of milliseconds for a full round trip against some tens or hundreds of
seconds to transfer the test file.
Most likely .... How do "they" determine my 'Upload Speed' and then how
do "they" determine my "Download Speed"??
We've told you a dozen times, you're just not listening.
[...]
How fast can I get from my Home to the Airport and then back Home?? ;-P
That would be the RTT / Latency, and doesn't matter when you're asking "what's the best way to get me, my 10 closest friends, all our luggage,
and two dogs to the airport?"
On 9/09/2025 10:13 pm, Dan Purgert wrote:
On 2025-09-09, Daniel70 wrote:
YEAP!! Undergerstumble!! But did my data travel via Undersea Co-ax or
via Low Earth orbit Satellite or via High Earth orbit Satellite ..... or >>> via one of those reflector Panels (supposedly) left on The Moon by the
Apollo Astronauts??
It doesn't matter - throughput is not latency.
But I'm not really interested in throughput OR latency but how long it
takes to get from A (my place) to B (test site) .... and then how long
it takes to get from B (test site) to A (my place).
Yes, understood, Rudy, don't start sending second Block until reception of first block acknowledged.
Yes, understood, Rudy, don't start sending second Block until reception
of first block acknowledged.
Hum. Maybe not. I did not study TCP in that detail, but older protocols would send a number of blocks, say 1, 2, 3, 4 & 5 and start receiving the ACKs after number 3. The receiver says OK to number 1, fail number 2, Ok number 3... so after a while, out of sequence, the sender repeats number
2, just after sending number 6.
On 2025-09-09 14:34, Daniel70 wrote:
On 9/09/2025 10:13 pm, Dan Purgert wrote:
On 2025-09-09, Daniel70 wrote:
YEAP!! Undergerstumble!! But did my data travel via Undersea
Co-ax or via Low Earth orbit Satellite or via High Earth orbit
Satellite ..... or via one of those reflector Panels
(supposedly) left on The Moon by the Apollo Astronauts??
It doesn't matter - throughput is not latency.
But I'm not really interested in throughput OR latency but how long
it takes to get from A (my place) to B (test site) .... and then
how long it takes to get from B (test site) to A (my place).
That's latency.
On 9/09/2025 10:41 pm, Carlos E.R. wrote:
On 2025-09-09 14:34, Daniel70 wrote:Ah!! O.K., my mistake.
On 9/09/2025 10:13 pm, Dan Purgert wrote:
On 2025-09-09, Daniel70 wrote:
YEAP!! Undergerstumble!! But did my data travel via Undersea
Co-ax or via Low Earth orbit Satellite or via High Earth orbit
Satellite ..... or via one of those reflector Panels
(supposedly) left on The Moon by the Apollo Astronauts??
It doesn't matter - throughput is not latency.
But I'm not really interested in throughput OR latency but how long
it takes to get from A (my place) to B (test site) .... and then
how long it takes to get from B (test site) to A (my place).
That's latency.
I thought 'Latency' was how long it took something to get up'n'going!!
i.e. overcoming "inertia".
On 9/09/2025 9:14 pm, Carlos E.R. wrote:
During my Military Service, I worked at The Australian Army's Primary
Hum. Maybe not. I did not study TCP in that detail, but older
protocols would send a number of blocks, say 1, 2, 3, 4 & 5 and start
receiving the ACKs after number 3. The receiver says OK to number 1,
fail number 2, Ok number 3... so after a while, out of sequence, the
sender repeats number 2, just after sending number 6.
H.F. Transmitter site. Most of our signals were multi-channel TTY over
an A.F. channel. Just kept sending. If there was a corruption, that'd
get resent later, if needed.
Actually, the first suburbs rolled out got FTTH, I was lucky to be in
one. But then under pressure from Murdoch, the government went for the
mixed madness system (FTTN, coax, fixed wireless, whatever shit was in
the spare parts bin....)
The Speed Test does show a Ping time .... 14 mS .... whilst its doing
the 'Download' speed test .... 12.59Mb/s .... THEN it tests the Upload
speed .... 0.98Mb/s
Carlos,
Yes, understood, Rudy, don't start sending second Block until
reception of first block acknowledged.
Hum. Maybe not. I did not study TCP in that detail, but older protocols
would send a number of blocks, say 1, 2, 3, 4 & 5 and start receiving
the ACKs after number 3. The receiver says OK to number 1, fail number
2, Ok number 3... so after a while, out of sequence, the sender repeats
number 2, just after sending number 6.
You are correct, it still does that. But its not a good idea to try to explain higher math to someone who doesn't (yet) know how additions
work.
Regards,
Rudy Wieser
I thought 'Latency' was how long it took something to get up'n'going!!
i.e. overcoming "inertia".
... what if Distant end is not expecting me to send anything?? Do I just
keep sending, ad infinitum??
On Wed, 10 Sep 2025 00:04:20 +1000, Daniel70 wrote:
I thought 'Latency' was how long it took something to get up'n'going!!
i.e. overcoming "inertia".
How would “inertia” apply to something like electrons, which weigh
hardly anything?
On 2025-09-09 16:04, Daniel70 wrote:
On 9/09/2025 10:41 pm, Carlos E.R. wrote:
On 2025-09-09 14:34, Daniel70 wrote:Ah!! O.K., my mistake.
On 9/09/2025 10:13 pm, Dan Purgert wrote:
On 2025-09-09, Daniel70 wrote:
YEAP!! Undergerstumble!! But did my data travel via Undersea
Co-ax or via Low Earth orbit Satellite or via High Earth orbit
Satellite ..... or via one of those reflector Panels
(supposedly) left on The Moon by the Apollo Astronauts??
It doesn't matter - throughput is not latency.
But I'm not really interested in throughput OR latency but how long
it takes to get from A (my place) to B (test site) .... and then
how long it takes to get from B (test site) to A (my place).
That's latency.
I thought 'Latency' was how long it took something to get up'n'going!!
i.e. overcoming "inertia".
I asked chatgpt to make sure. :-)
Q: In the scenario of measuring internet connection speed, what would be
the latency?
A: In the context of measuring **internet connection speed**,
**latency** refers to the **time it takes for a data packet to travel
from your device to a remote server and back**. It's usually measured in **milliseconds (ms)** and is also known as **ping**.
### Breakdown:
* **Latency = Round-trip time (RTT)**
* It measures **delay**, not speed (throughput).
* Lower latency = faster response.
---
### Example:
When you run a speed test:
* **Ping/Latency:** 20 ms
* **Download speed:** 100 Mbps
* **Upload speed:** 20 Mbps
Here:
* **100 Mbps** is how much data can be received per second.
* **20 ms** latency means it takes 20 milliseconds to send a small
request to the server and get a reply.
---
### Why Latency Matters:
* High latency can cause **lag** in:
* Online gaming
* Video calls
* Real-time applications
Even with fast download speeds, high latency can make the connection
feel sluggish.
---
Would you like help measuring or interpreting your own latency?
On Tue, 9 Sep 2025 21:36:19 +1000, Daniel70 wrote:
On 9/09/2025 9:14 pm, Carlos E.R. wrote:
During my Military Service, I worked at The Australian Army's Primary
Hum. Maybe not. I did not study TCP in that detail, but older
protocols would send a number of blocks, say 1, 2, 3, 4 & 5 and start
receiving the ACKs after number 3. The receiver says OK to number 1,
fail number 2, Ok number 3... so after a while, out of sequence, the
sender repeats number 2, just after sending number 6.
H.F. Transmitter site. Most of our signals were multi-channel TTY over
an A.F. channel. Just kept sending. If there was a corruption, that'd
get resent later, if needed.
You’re talking fairly low-bandwidth communication, where the end-to-end latency is only a few symbols at most.
With typical Internet connection speeds, end-to-end latencies can add up
to dozens, hundreds of data packets. So if you don’t use a windowing protocol, you end up with very low channel bandwidth usage efficiency.
On Tue, 9 Sep 2025 21:18:41 +1000, Daniel70 wrote:
The Speed Test does show a Ping time .... 14 mS .... whilst its doing
the 'Download' speed test .... 12.59Mb/s .... THEN it tests the Upload
speed .... 0.98Mb/s
VDSL?
On Tue, 9 Sep 2025 12:30:43 +0800, Woozy Song wrote:
Actually, the first suburbs rolled out got FTTH, I was lucky to be in
one. But then under pressure from Murdoch, the government went for the
mixed madness system (FTTN, coax, fixed wireless, whatever shit was in
the spare parts bin....)
NZ did FTTH all the way, at least in all the reasonably-sized urban
centres, including mine.
Though it turned out the company that originally laid the fibre trunks
took a few ... short-cuts ...
On 10/09/2025 2:30 am, Carlos E.R. wrote:
On 2025-09-09 16:04, Daniel70 wrote:
On 9/09/2025 10:41 pm, Carlos E.R. wrote:
On 2025-09-09 14:34, Daniel70 wrote:Ah!! O.K., my mistake.
On 9/09/2025 10:13 pm, Dan Purgert wrote:
On 2025-09-09, Daniel70 wrote:
YEAP!! Undergerstumble!! But did my data travel via Undersea
Co-ax or via Low Earth orbit Satellite or via High Earth orbit
Satellite ..... or via one of those reflector Panels
(supposedly) left on The Moon by the Apollo Astronauts??
It doesn't matter - throughput is not latency.
But I'm not really interested in throughput OR latency but how long
it takes to get from A (my place) to B (test site) .... and then
how long it takes to get from B (test site) to A (my place).
That's latency.
I thought 'Latency' was how long it took something to get up'n'going!!
i.e. overcoming "inertia".
I asked chatgpt to make sure. :-)
Q: In the scenario of measuring internet connection speed, what would be
the latency?
A: In the context of measuring **internet connection speed**,
**latency** refers to the **time it takes for a data packet to travel
from your device to a remote server and back**. It's usually measured in
**milliseconds (ms)** and is also known as **ping**.
So a "one-way" journey.
### Breakdown:
* **Latency = Round-trip time (RTT)**
But wait, "Latency" is now Return Trip Time!!
* **100 Mbps** is how much data can be received per second.
... but one-way, only!!
* **20 ms** latency means it takes 20 milliseconds to send a small
request to the server and get a reply.
So is that "Round Trip" time??
On 10/09/2025 2:30 am, Carlos E.R. wrote:
On 2025-09-09 16:04, Daniel70 wrote:
On 9/09/2025 10:41 pm, Carlos E.R. wrote:
On 2025-09-09 14:34, Daniel70 wrote:Ah!! O.K., my mistake.
On 9/09/2025 10:13 pm, Dan Purgert wrote:
On 2025-09-09, Daniel70 wrote:
YEAP!! Undergerstumble!! But did my data travel via Undersea
Co-ax or via Low Earth orbit Satellite or via High Earth orbit
Satellite ..... or via one of those reflector Panels
(supposedly) left on The Moon by the Apollo Astronauts??
It doesn't matter - throughput is not latency.
But I'm not really interested in throughput OR latency but how long
it takes to get from A (my place) to B (test site) .... and then
how long it takes to get from B (test site) to A (my place).
That's latency.
I thought 'Latency' was how long it took something to get
up'n'going!! i.e. overcoming "inertia".
I asked chatgpt to make sure. :-)
Q: In the scenario of measuring internet connection speed, what would
be the latency?
A: In the context of measuring **internet connection speed**,
**latency** refers to the **time it takes for a data packet to travel
from your device to a remote server and back**. It's usually measured
in **milliseconds (ms)** and is also known as **ping**.
So a "one-way" journey.
### Breakdown:
* **Latency = Round-trip time (RTT)**
But wait, "Latency" is now Return Trip Time!!
* It measures **delay**, not speed (throughput).
* Lower latency = faster response.
---
### Example:
When you run a speed test:
* **Ping/Latency:** 20 ms
* **Download speed:** 100 Mbps
* **Upload speed:** 20 Mbps
Here:
* **100 Mbps** is how much data can be received per second.
... but one-way, only!!
* **20 ms** latency means it takes 20 milliseconds to send a small
request to the server and get a reply.
So is that "Round Trip" time??
---
### Why Latency Matters:
* High latency can cause **lag** in:
* Online gaming
* Video calls
* Real-time applications
Even with fast download speeds, high latency can make the connection
feel sluggish.
---
Would you like help measuring or interpreting your own latency?
Thanks for the offer, Carlos, but I don't really think I'm achieving anything .... except annoying you guys. ;-)
On 10/09/2025 10:59 am, Lawrence D’Oliveiro wrote:
On Tue, 9 Sep 2025 21:18:41 +1000, Daniel70 wrote:Ummm!! Never heard that term before, Lawrence, so I don't know.
The Speed Test does show a Ping time .... 14 mS .... whilst its doing
the 'Download' speed test .... 12.59Mb/s .... THEN it tests the Upload
speed .... 0.98Mb/s
VDSL?
I've stated my speeds above, .... but my sisters newly upgraded system
can, apparently, achieve 100Mb/s but is being throttled to just 50Mb/s Download speed (cheaper account).
On 10/09/2025 11:39, Daniel70 wrote:
On 10/09/2025 10:59 am, Lawrence D’Oliveiro wrote:
On Tue, 9 Sep 2025 21:18:41 +1000, Daniel70 wrote:Ummm!! Never heard that term before, Lawrence, so I don't know.
The Speed Test does show a Ping time .... 14 mS .... whilst its doing
the 'Download' speed test .... 12.59Mb/s .... THEN it tests the Upload >>>> speed .... 0.98Mb/s
VDSL?
I've stated my speeds above, .... but my sisters newly upgraded system
can, apparently, achieve 100Mb/s but is being throttled to just 50Mb/s
Download speed (cheaper account).
Am I the only reader thinking that the OP is either incredibly dim or is winding up those kind enough to keep responding, probably the latter?
On 10/09/2025 11:39, Daniel70 wrote:
On 10/09/2025 10:59 am, Lawrence D’Oliveiro wrote:
On Tue, 9 Sep 2025 21:18:41 +1000, Daniel70 wrote:Ummm!! Never heard that term before, Lawrence, so I don't know.
The Speed Test does show a Ping time .... 14 mS .... whilst its doing
the 'Download' speed test .... 12.59Mb/s .... THEN it tests the Upload >>>> speed .... 0.98Mb/s
VDSL?
I've stated my speeds above, .... but my sisters newly upgraded system
can, apparently, achieve 100Mb/s but is being throttled to just 50Mb/s
Download speed (cheaper account).
Am I the only reader thinking that the OP is either incredibly dim or is winding up those kind enough to keep responding, probably the latter?
On 10/09/2025 10:59 am, Lawrence D’Oliveiro wrote:
Who would'a'thunk??
On Tue, 9 Sep 2025 12:30:43 +0800, Woozy Song wrote:
Actually, the first suburbs rolled out got FTTH, I was lucky to be in
one. But then under pressure from Murdoch, the government went for the
mixed madness system (FTTN, coax, fixed wireless, whatever shit was in
the spare parts bin....)
NZ did FTTH all the way, at least in all the reasonably-sized urban
centres, including mine.
Though it turned out the company that originally laid the fibre trunks
took a few ... short-cuts ...
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,070 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 151:46:59 |
| Calls: | 13,733 |
| Calls today: | 1 |
| Files: | 186,966 |
| D/L today: |
727 files (253M bytes) |
| Messages: | 2,418,445 |