Status
Not open for further replies.
Do you have more than one WIN 10 PC on a local LAN? have you checked ? Before you do that, I am not wrong ........

Post that trace route, and then PROVE, the update was coming over that link ------ with nothing else on the PC running ------

I'll run the traceroute again tonight (and a few others)...

Curious as to where you think latency would come in?
 
Last edited:
3ms latency is NOT possible over even the shortest of Internet connections.

Who told you that nonsense? Of course it's possible, and has been since forever*. 10 years ago I lived in one country and had sub-3 millisecond pings to machines in the neighbouring country.

* Not to be taken literally.
 
3ms latency is NOT possible over even the shortest of Internet connections. Have you got more than one WIN 10 PC connected to your local LAN? IF so, that update is happening from another device on your LAN ... have a look at the update setup on your machine. Go to [settings/advanced options/ choose how your updates are delivered/Updates from more than one place].. If ON, then the default option is PCs on my local network and PCs on the Internet.

I would advise to either switch this OFF or, at least to change it to PCs on my local network only ....

Lel. I love this guy.

2 of us had that ping on a gaming server once because it was like 5KM from my home - our homes. Not sure what makes you think it's impossible. Ping is mostly a factor of distance - if he's not too far from the server, and the ASSIA/Interleaved setting is disabled(adds 10-15ms automatically for me when on), 3ms is easily possible.
 
Well lets see. the claim is that this is to a point where a WIN 10 update is coming from. It is only possible with a perfect direct connection, NOT through a typical Internet connection ...... So my claim stands until those trace routes are posted, because THAT WILL reveal how it is/was routed. Not before that is revealed can the claim be made ----.
 
Lel. I love this guy.

2 of us had that ping on a gaming server once because it was like 5KM from my home - our homes. Not sure what makes you think it's impossible. Ping is mostly a factor of distance - if he's not too far from the server, and the ASSIA/Interleaved setting is disabled(adds 10-15ms automatically for me when on), 3ms is easily possible.

Working over a WUG I suppose ? So tell us what the network looked like . It could not have happened over a typical normal connection, between two points through a public network, it had to be via some or other "private network".
 
Well lets see. the claim is that this is to a point where a WIN 10 update is coming from. It is only possible with a perfect direct connection, NOT through a typical Internet connection ...... So my claim stands until those trace routes are posted, because THAT WILL reveal how it is/was routed. Not before that is revealed can the claim be made ----.

Where would the bottleneck be?
 
D:\Users\micro>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router [10.0.0.1]
2 <1 ms <1 ms <1 ms 196-212-61-1.dynamic.ftth.broadband.is [196.212.61.1]
3 <1 ms <1 ms <1 ms cdsl1-rba-vl151.ip.isnet.net [196.38.73.18]
4 <1 ms <1 ms <1 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 4 ms 1 ms 2 ms core1b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.62]
6 1 ms <1 ms <1 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
7 1 ms 1 ms 1 ms 72.14.205.16
8 1 ms 1 ms 1 ms 72.14.239.53
9 1 ms 1 ms 1 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

D:\Users\micro>
 
D:\Users\micro>tracert www.google.co.za

Tracing route to www.google.co.za [197.80.135.29]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router [10.0.0.1]
2 <1 ms <1 ms <1 ms 196-212-61-1.dynamic.ftth.broadband.is [196.212.61.1]
3 <1 ms <1 ms <1 ms cdsl1-rba-vl151.ip.isnet.net [196.38.73.18]
4 <1 ms <1 ms <1 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 3 ms 2 ms 2 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
6 1 ms <1 ms <1 ms 168.209.1.170
7 1 ms 1 ms 1 ms mweb-1.jinx.net.za [196.223.14.25]
8 1 ms 1 ms 3 ms 197-80-7-14.jhb.mweb.co.za [197.80.7.14]
9 1 ms 1 ms 1 ms 197-80-135-29.jhb.mweb.co.za [197.80.135.29]
 
Now that IS impressive! Just confirm this is over your normal home connection and not sitting at some very conveniently located business node.

I stand corrected, FTTH is making a huge difference. No question, and end to end fibre is at the moment changing things drastically.

Now what about where the WIN 10 update was coming from? If the source was somewhere close you may just be correct.

Compare this with a normal ADSL client in PTA to the same points as you posted :

13 ms when no other activity is taking place on my LAN.

Right now, I have a very large Dropbox download taking place ,and the best I can get over a public ADSL network is 34 ms.
 
Last edited:
Now that IS impressive! Just confirm this is over your normal home connection and not sitting at some very conveniently located business node.

I stand corrected, FTTH is making a huge difference. No question, and to end fibre is at the moment changing things drastically.

Now what about where the WIN 10 update was coming from? If the source was somewhere close you may just be correct.

Compare this with a normal ADSL client in PTA to the same points as you posted :

13 ms when no other activity is taking place on my LAN.

Right now, I have a very large Dropbox download taking place ,and the best I can get over a public ADSL network is 34 ms.

This is my home pc. This one is wired, not wifi though.
Fibre makes a huge difference. No Telkom IPC, and no ATM encapsulation over the last mile . Gigabit Ethernet all the way to the core.
 
This is my home pc. This one is wired, not wifi though.
Fibre makes a huge difference. No Telkom IPC, and no ATM encapsulation over the last mile . Gigabit Ethernet all the way to the core.

Yes GE also helps. Consider me green with envy. It is what I was used to as well before being relegated back mto just a normal sub on an ADSL network.

Adding a last inch Wi-Fi element is not going to cause much worse results. Effectively, at the moment you are on a backbone node .....


But you will agree with me that what you are getting is NOT what a normal client on a public network (ADSL) can expect .....
 
Last edited:
Who told you that nonsense? Of course it's possible, and has been since forever*. 10 years ago I lived in one country and had sub-3 millisecond pings to machines in the neighbouring country.

* Not to be taken literally.

Certainly not possible in our country.
 
Working over a WUG I suppose ? So tell us what the network looked like . It could not have happened over a typical normal connection, between two points through a public network, it had to be via some or other "private network".

Nope. ADSL. You saying it couldn't happen doesn't mean it didn't.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X