![]() ![]() ![]() ![]() |
|
FireEngine:DensitY: 39.66Mbit/sec on speedtest downstream (synced at around 41 so pretty good all things considering)
Awesome! glad we could sort it out for you. Sorry it wasn't setup properly from the get-go.
Phewsion: Rather than starting a new thread thought I'd chime in here
I might be having the same problem, It was installed last monday so I gave it a week to see how it went before posting
Regards FireEngine
alexchung5111: I can only get around 30Mbps
Could you help me plz ?
Regards FireEngine
FireEngine:alexchung5111: I can only get around 30Mbps
Could you help me plz ?
You are on the right profile, can you reboot and if still an issue let me know the sync rate as well as throughput please.
alexchung5111:FireEngine:alexchung5111: I can only get around 30Mbps
Could you help me plz ?
You are on the right profile, can you reboot and if still an issue let me know the sync rate as well as throughput please.
I rebooted it, here is the info from the modem
Regards FireEngine
alexchung5111:FireEngine:alexchung5111: I can only get around 30Mbps
Could you help me plz ?
You are on the right profile, can you reboot and if still an issue let me know the sync rate as well as throughput please.
I rebooted it, here is the info from the modem
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Attainable Rate (Kbps):
51495
12912
Rate (Kbps):
46140
10354
alliao: that DLM-1 profile sure looks sweet, any idea how I can get on to it? I've read that epic thread over at snap, looks like waiting and hoping the only way?
I didn't know about the 10 days profiling period and I went ahead and removed the filter since I'm on naked connection anyway, so loads of reconnection in the first and second day.
So now even though it says
Attainable Rate (Kbps): 51495 12912
I connect at
Rate (Kbps): 46140 10354
any pointers?
#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:alliao: that DLM-1 profile sure looks sweet, any idea how I can get on to it? I've read that epic thread over at snap, looks like waiting and hoping the only way?
I didn't know about the 10 days profiling period and I went ahead and removed the filter since I'm on naked connection anyway, so loads of reconnection in the first and second day.
So now even though it says
Attainable Rate (Kbps): 51495 12912
I connect at
Rate (Kbps): 46140 10354
any pointers?
the reboots will have pushed your chances right back.
more than about 1 reboot a day (depending of if the DSLAM picks the reboot to be a crash or a disconnection), will loose DLM-1 instantly.
ild keep your modem offline for 5 or so mins, so the DSLAM marks it as a normal power down, and not the line being "unstable", this seems to stop DLM moves - but again doing it often will not be so healthy..
whats your line attenuation? your speed possibly indicates you might be on a pretty short line, inwhich case you have a high chance of getting a 17A profile.
#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: 9db, thats a bit far for 17a.. looks like the copper in your area is pretty decent though.
errors dont look on the pretty side mind you.
will be interesting to see what DLM does for your line considering your errors, your already on DLM-6.
are you sure you removed the splitter correctly? single run to from ETP to your DSL jackpoint? your error rates suggest DLM may pull back even more soon. (assuming i didnt make a mistake in my math. not used to reading your routers output)
the fact that you have large counts of SES and UAS, further pushes the point that your line isnt looking pretty, further more removing the splitter, makes for an easy blame for chorus should they need to come out and fix it up.
|
![]() ![]() ![]() ![]() |