Okay, so here is my follow up on live chat + technician coming over and informing them about dsl noise profile that can only be changed on TM side stuff few days ago.
Oh ya, I create the report on monday 20/3/2017 and it was changed just now 22/3/2017.

Before (Interleaving mode)




Today (Fastpath mode)




for Miri City TM technicians.

Edit: Note that I don't get charged...okay....
Edit2: Replacing pictures with PNG version because lowyat JPEG compressor quality is disappointing....

This post has been edited by JohnLai: Mar 22 2017, 06:13 PM


Attached thumbnail(s)

Login into the modem/router and check the adsl stats.
Dlink, asus and tplink display "Interleave Depth" value for both upstream and downstream.
In my case, it was 64 depth downstream and 8 depth upstream
If you use TM supplied innacomm, then you out of luck.
Notice how much delay/latency interleaving by taking a look at "Delay (msec)"
When my adsl line was in Interleave mode, the "Delay (msec)" were 7.85ms for downstream and 7.91ms for upstream.

Once it is changed to fastpath, Interleave Depth is 1 for both upstream and downstream (depth of 1 means fastpath). The Delay (msec) for both downstream and upstream become 0.25ms and 0.24ms respectively.

Some people is unlucky, for example, the forummer HolySatan here:

Source: https://forum.lowyat.net/index.php?showtopi...post&p=84153387
His "Delay (msec)" is....... 15ms for both downstream and upstream. Total up 30ms latency. His adsl noise profile probably is configured at maximum stability mode.


25.3 with 6.4?
22.8 with 6.5?
Yes, stable enough.


EDIT: Anyone with SNR (upstream and downstream) lower than 25, don't bother changing to fastpath. Otherwise, the dsl line will be forced to retrain randomly due to error/noise/low signal (layman term, dsl light will be unstable) or there will be a lot of packet loss.

This post has been edited by JohnLai: Mar 22 2017, 11:30 PM

Only 1.4db attenuation for upstream?
Sure, no problem. Upstream SNR 23.4 should be fine since the attenuation is quite low. If your attenuation is more than 10, then better don't change. Luckily it is only 1.4db. Must be new copper wire........

But seriously......you better hope the technician at your local DSLAM exchange know how to change it.

Changing "interleave" to "fastpath" can only be done on TM side, not user side.
No need to ask TM technician to come over. (TM charges RM50+ for each visit, in my case though, TM technicians came over and I explained to them about dsl interleaving,fastpath, and depth value plus how those things have impact on latency, when fastpath or interleave should be used and how it can be only changed by TM since TM doesn't expose such setting to user unlike Australia Telstra ISP. I showed them Australia Telstra website too. I don't get charged for the visit. They said they will refer to their senior and voila, mine got changed to fastpath the next day )

This post has been edited by JohnLai: Mar 22 2017, 11:56 PM

So far, so good,even my parent also said their internet browsing (through wifi) is quite responsive than usual today.
Except the part where my area IPv6 connectivity still borked since October 2016.........
Not really a problem as I can use HE tunnel to access IPv6 only websites.
The bad news, I might not be using dsl for long. Currently awaiting call from unifi installer. Installer may call me for installation between April to June.

True, copper cable quality is important. But with your current upstream SNR......don't take the risk of changing to fastpath.

EDIT: wah, even with interleaving, your 22ms ping is quite good. I guess 38ms is quite reasonable for my location in Sarawak.

This post has been edited by JohnLai: Mar 23 2017, 01:25 AM

I got mine changed back to public IP.

Oh ya, livechat agent also requested ping plotter result from me.
I simply provided her/him with the result and clarify that the ping can be lowered further if adsl noise profile is set to fastpath. I also wrote the interleave depth is adding 25ms plus 5ms extra ping time. So, from the pingplotter result, there is total 30ms extra latency which is caused by dsl interleaving which is simply unacceptable for online gaming. I provided them the source for the info http://www.kitz.co.uk/adsl/interleaving.htm and http://www.juniper.net/techpubs/software/c...e-config31.html , at the bottom graph, had* the livechat agent took a look at 'burst protection' latency values because TM dsl line has it activated. In worst case scenario, interleaving can increase latency up to 47ms for depth value of 64 with INP value of 2.

You can check my interleaved dsl stats screenshot where my INP were 2.64 and 2.63 for downstream and upstream. In fastpath, INP is disabled.

EDIT: Some stuff for reading....how INP and interleave depth affect each other......fair use.....two pages only. Sourced from google book?





This post has been edited by JohnLai: Mar 23 2017, 04:24 PM

Yes...the app ping plotter......use LAN cable, make sure no one uses the line while pingplotting......ping TM DNS server IP 202.188.1.5 (decommissioned) or 1.9.1.9 (use this one better)

You could calculate it....if you know INP value, depth value, B M T R S L....
In theory, mine supposed to shave 30ms latency off ping time after changing from interleaving to fastpath. In reality, only average 21ms latency is shaved off. Probably because trellis line coding still activated for downstream Well, I guess 70% out of 100% is fine. I believe the shaved latency should be 25ms out of 30ms if my downstream trellis modulation is turned off . Nothing is perfect. Only formula is perfect.

Poor soul.....private ipv4 address.

10.112.0.0-10.112.255.255 Reserved for Private-Use Networks [RFC 1918]

3. Private Address Space

The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

EDIT: Check if your IPV6 is working on device. Cause your lowyat post didn't show IPv6 logo on top right of the post.

This post has been edited by JohnLai: Mar 31 2017, 08:50 PM

Well, it is either youtube 50kb/s with Ipv6 or live with private ipv4 address........
Either way, since you never notice it.....continue using ipv4......

Yes.
IPv4/IPV6
SLAAC
Enable PD
DHCP V6 Enabled.
Request DHCPV6

No idea why you don't get the ipv6 logo on your post.
I guess your IPv6 connectivity is borked at TM side similar to mine.

Congratulation!

Telnet/SSH into the router and find out.
But the sad news is ....different model has different command to show adsl stats.
So, once you login into the router, type 'help' to list out every available commands.

Nope, TM ancient DLINK 2640B doesn't show it.

Well, telnet and find out. If you don't know....better give it up.


I got 2640T and 2640B. Lazy to plug it and take screenshot.
Anyway, these two models don't show detailed adsl stats.

Only 2750U does.

Yes. You are behind Private IP range.

Yes.

IF you can gg them in first place......

Well, just tell them that you streamyx account needs to be assigned with public IPV4 address because you can't access your home CCTV.

But.....recently.....TM is requesting customer to use IPV6 instead. However.....MOST EXISTING CCTV is not IPV6 compatible.

Please report back if you ever get it changed back to public IP. (Which is very unlikely now)
I got few colleagues whose streamyx got assigned with private IPV4 address and they were told to use IPV6 by TM.

Probably TM changed the port too while reconfiguring it to FastPath?

Unfortunately, yes, it is still there.
Went to my colleagues houses to enable IPv6 for them (only to discover their CCTV doesn't support IPV6) and tried youtube. 50kb/s on IPV6.
They rather have IPV6 disabled because the throttling is too much. Seriously, with 4Mbps/8Mbps, nobody wanna stuck with 50kb/s throttling on IPV6 at youtube.

Huh......a successful gg.
Don't be happy so soon. TM will revert you back to private IPv4 later.

Last year, my streamyx was assigned with private IPV4 address 6 TIMES!
Every time it happened, I complained kaw-kaw at TMPoint.
If call 100 or use live chat, sure will get a lot of excuses and other 'solution'.

Good luck on finding knowledgable TM personnels.
95% of time, call operator doesn't know what are you talking about (noise profile, interleaving,fast path, depth, symbol rate). Since the operator doesn't know, he/she can't even know how to file a report.
After call operator level, even your local TM technicians don't know.

I am not TM management, can't do anything.
However, I can guarantee you, it WILL HAPPEN for sure.
At least your area IPv6 still work....my area had it disabled since october 2016.