Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 
eldite

13 posts

Geek
+1 received by user: 5


  #2382525 29-Dec-2019 16:22
Send private message

Appreciate all your detailed responses.  Sync is at 122Mbps, with 'elapsed time' 25 days ago (2,232,000+ seconds).   

 

 

 

I do not have a lot of experience with ddDLM, but will check the console for sync speeds next time I encounter this. 

 

 

 

 

 

 

 

 

 

 




RunningMan
9186 posts

Uber Geek
+1 received by user: 4840


  #2382640 29-Dec-2019 20:09
Send private message

If the XDSL link times (46) is the number of times it's reset in 25 days, then that could be the problem. As it stands, it's looking pretty good, but if there's something intermittent causing bursts of noise or interference on the line, then ddDLM could be pulling it back.

 

The mode (17a) and the DS sync rate are the things to keep an eye on. When you do a speedtest, check what those are at the same time.


yitz
2239 posts

Uber Geek
+1 received by user: 594


  #2382641 29-Dec-2019 20:11
Send private message

Dat 1 dB SNR margin 😎




hio77
'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified
Trusted
Lizard Networks
Subscriber

  #2382655 29-Dec-2019 20:48
Send private message

yitz:

Dat 1 dB SNR margin 😎


That's probably got something to do with it. Although I'm surprised if it's erroring that bad it isn't dropping...




#include <std_disclaimer>

 

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have. 


hio77
'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified
Trusted
Lizard Networks
Subscriber

  #2382657 29-Dec-2019 20:53
Send private message

yitz:

Do Spark/Skinny/Bigpipe still use xDSL port line rate data passed on from Chorus to do some sort of traffic policing at their BNGs?


The prioritisation bigpipe had was removed when it was moved to sparks core.
Yes traffic policy's are set from the data we get from chorus. But that's dynamic to what the connection connects at. It wouldn't be the cause of this at all. Looks like the low us snr is dropping the connection, its getting a bad sync then renegotiating.




#include <std_disclaimer>

 

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have. 


1 | 2 
View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.