Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » O Canada! » Canadian » TekSavvy » Bell finally fixed the IKNS remotes (somewhat)
Uniqs:
1319
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
email not working »
« Teksavvy screws current MLPPP users  
sMURF

join:2007-02-27
Toronto, ON

Bell finally fixed the IKNS remotes (somewhat)

And it only took them 19 months! Way to fail!

The upstream SNR/power are still stuck on 6dB/12.5dBm respectively, but the attenuation is no longer stuck on 20.5dB (it shows as 5.5dB for me).

It's also still on interleave, but the ping times are better. Before being put on the IKNS remote, my second hop ping times were usually 10ms or so, then around 45ms while on the IKNS remote, and now it's around 15-20ms.

Angelo_
The Network Guy
Premium
join:2002-06-18

Re: Bell finally fixed the IKNS remotes (somewhat)

i'd check your profiel a change in profiles can do this
sMURF

join:2007-02-27
Toronto, ON

Re: Bell finally fixed the IKNS remotes (somewhat)

Profile is still the same:

Down Up
Current Rate: 5056 kbs 800 kbs
Max Rate: 10584 kbs 800 kbs
Current Connection:
Current Noise Margin: 25.0 dB 6.0 dB
Current Attenuation: 5.4 dB 5.5 dB
Current Output Power: 1.0 dBm 12.5 dBm
bbiab

join:2004-05-26

Re: Bell finally fixed the IKNS remotes (somewhat)

Not sure why you think your problems are due to IKNS. In fact, I don't think there ever was a problem with down, only the reporting of stats. Up, on the other hand, still no change @ 736 here. Some will say there is no reason for this or does not exist anymore, but then they never say how to fix. This is real of course, documented from the beginning. Ping is fine, no idea what the stats say, don't care.

Gokuu

join:2001-08-27

Re: Bell finally fixed the IKNS remotes (somewhat)

If you had bothered to read the OP, you would have realized that he was talking about UPSTREAM.

If you have no idea about the stats and "don't care", then please don't bother posting and wasting our time if you have nothing of value to add to the conversation.

I have been on an IKNS remote since March 2009, and I have always had correct upstream attenuation with my ST516. Upstream is at a perfect 800kbit, however this wasn't the case when on 2+. I was never able to get anything close to the 1088 which is in Bell's official profile.

said by bbiab See Profile :

Not sure why you think your problems are due to IKNS. In fact, I don't think there ever was a problem with down, only the reporting of stats. Up, on the other hand, still no change @ 736 here. Some will say there is no reason for this or does not exist anymore, but then they never say how to fix. This is real of course, documented from the beginning. Ping is fine, no idea what the stats say, don't care.
bbiab

join:2004-05-26

1 edit

Re: Bell finally fixed the IKNS remotes (somewhat)

OP be talking about interleave and ping time. Not using ST516.
planiwa

join:2009-02-19
Toronto M5S


2 edits
This appears to have happened 22 hours ago:

SysUpTime: 18:14:43 xDSL linestate down
SysUpTime: 18:16:28 xDSL linestate up (downstream: 5056 kbit/s, upstream: 800 kbit/s; output Power Down: 17.0 dBm, Up: 12.5 dBm; line Attenuation Down: 17.0 dB, Up: 20.5 dB; snr Margin Down: 27.0 dB, Up: 6.0 dB)
SysUpTime: 01 day 16:39:00 LOGIN User logged in on TELNET (192.168.1.2)
Jun 25 07:48:07 LOGOUT User logged out on TELNET (192.168.1.2)
Jun 25 07:48:21 LOGIN User logged in on TELNET (192.168.1.2)
Jun 25 07:58:54 LOGOUT User logged out on TELNET (192.168.1.2)
Jun 25 08:05:23 LOGIN User logged in on TELNET (192.168.1.2)
Jun 24 08:07:23 LOGOUT User logged out on TELNET (192.168.1.2)
Jun 24 08:07:34 LOGIN User logged in on TELNET (192.168.1.2)
Jun 24 08:08:14 LOGOUT User logged out on TELNET (192.168.1.2)
Jun 24 08:10:41 LOGIN User logged in on TELNET (192.168.1.2)
Jun 24 08:18:23 LOGOUT User logged out on TELNET (192.168.1.2)
Jun 29 01:57:27 xDSL linestate down
Jun 29 02:08:35 xDSL linestate down
Jun 29 02:08:56 xDSL linestate up (downstream: 5056 kbit/s, upstream: 800 kbit/s; output Power Down: 5.0 dBm, Up: 12.5 dBm; line Attenuation Down: 5.0 dB, Up: 5.5 dB; snr Margin Down: 27.5 dB, Up: 6.0 dB)

Access Concentrator is bas3-toronto02 DSLAM is 501-4

Channel mode still reports Interleaved, and latency has not improved.
Mind you ST 516 is not vulnerable to IKNS latency as 2Wire is.

Any earlier log reports?
--
»[RFC] Connection / Speed Problems Checklist

Gokuu

join:2001-08-27

Re: Bell finally fixed the IKNS remotes (somewhat)

Interesting. Looks like they're pushing out new firmware.
sMURF

join:2007-02-27
Toronto, ON

said by planiwa See Profile :

This appears to have happened 22 hours ago:
Yeah that's when I lost my connection, June 30th around 1:57am, and it came back up at 2:25am. I only noticed the change while playing a game today, my ping was half of what it used to be.

I believe it was only the 2Wire modems that had significant ping time increases on IKNS remotes, other modems only had a 5-10ms increase.

I'm not sure if the new firmware on these remotes fixes the lower than normal upload profile some people seem to be stuck on, however.
planiwa

join:2009-02-19
Toronto M5S

Re: Bell finally fixed the IKNS remotes (somewhat)

Oh, now that you mention it -- mine happened 2 days ago!!!!
donkies

join:2008-04-08

1 edit
here in Montreal too, was 20.5 now is 7.5 ala upload ATTN, still states interleaved.

speedstream 4200 would never sync at 800 up, where a 2wire 2700 does without issue.
InvalidError

join:2008-02-03
·TekSavvy Solutions..
·Videotron

Re: Bell finally fixed the IKNS remotes (somewhat)

said by donkies See Profile :

here in Montreal too, was 20.5 now is 7.5 ala upload ATTN, still states interleaved.
My ADSL went down on Monday night too, Montreal, IKNS remote. My timeline was roughly like this:
01:30 - Loss of sync
01:45 - Sync is back but transport is down, unable connect to authentication servers
02:15 - Transport is back but login attempts always fail with "incorrect user name or password", even test@test
03:00 - Back online

I too noted the change in upstream attenuation but still bogus other stats.
bbiab

join:2004-05-26
The poster with the speedstream 4200 would never sync at 800 up. This seems to be a problem. Still. Perhaps this thread wasn't about that though, my mistake.

HiVolt
30
Premium
join:2000-12-28
Toronto, ON
clubs:

Re: Bell finally fixed the IKNS remotes (somewhat)

Neither SpeedStream 4200 or 6520 (i tried both) sync at higher than 736/766 on an IKNS remote (on ADSL2+ profile).
--
GOLF LEAFS GOLF!
bbiab

join:2004-05-26

Re: Bell finally fixed the IKNS remotes (somewhat)

ADSL sync 736
oxfordwhite

join:2008-01-28
Well somethign did happen. My attenuation went from the 20.5 to varing between 8-15 depending on the resync. (upstream that is)

TilhasBB
Formally Goden99
Premium
join:2000-08-05
canada

I had resycned on 30th as well. Not sure of changes.

But last night (july 4th) at 4am-7am I had lost sync. Attenuation is even lower at 6db and the snr is 0.5 HIGHER on upload! 6.5dB YUPIEEE...
To be fair everytime my modem resynced i'd get about 200-300
Transmitted FEC and Transmitted CRC. I have 0 now. So something has changed.

TilhasBB
Formally Goden99
Premium
join:2000-08-05
canada
Did you guys notice INKS ADSL2+ Resync time is down from 2-3minutes to 15-20seconds !!!

Whatever they did on the update, it seems to have made a nice difference.
Anyone else care to try?
dpkform

join:2003-04-13
Toronto, ON

I'm on TMMB/IKNS in High Park, Toronto, and while my upload SNR remains at 6, my attenuation is 6.5 from what I believe was in the low 20s. My output power is showing at 12.5 - can't remember if this was different before.

Has made a small but significant difference on upload for me - I used to score in the low to mid 600 range, now I am pulling high 600 on java test, and low 700 on flash test to speedtest.teksavvy.com

Server latency seems kinda crappy though at about 137ms.
planiwa

join:2009-02-19
Toronto M5S

Re: Bell finally fixed the IKNS remotes (somewhat)

said by dpkform See Profile :

now I am pulling high 600 on java test, and low 700 on flash test to speedtest.teksavvy.com

Server latency seems kinda crappy though at about 137ms.
"Low 700" is impossible. Presumably modem now syncs at 800, whereas before it synced at ???
RTT=173 means little without knowing modem make/model and server.
bbiab

join:2004-05-26
No change on ADSL upsync - still 736 on a perfect line.
planiwa

join:2009-02-19
Toronto M5S


2 edits

Re: Bell finally fixed the IKNS remotes (somewhat)

said by bbiab See Profile :

No change on ADSL upsync - still 736 on a perfect line.
Sync rate and latency with IKNS depends on modem. SpeedTouch is reputed to get 800. 2Wire , TP-Link, Aztech, SpeedStream sync lower and 2Wire has higher latency, reportedly.

At least now, with the crazy US Atn gone, people aren't getting wonky wire length guesstimates any more. For example, using Formula18:

Atn US Atn DS Wire-length Estimate

20.5 17 2.08km before
5.5 5 .58km after

Forums » O Canada! » Canadian » TekSavvyemail not working »
« Teksavvy screws current MLPPP users  


Monday, 30-Nov 16:44:03 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [34] Broadband Killed The Game Console
· [26] AT&T Top Lobbyist Cicconi Has His Feelings Hurt
· [22] Rural Carriers Quickly Embracing Fiber
· [19] Midcontinent Socked With Easement Lawsuit
· [12] Charter Exits Chapter 11
· [10] Baltimore To Ban Lazy Cable Installs
· [3] Monday Morning Links
Most people now reading
· Is Microsoft Technet ok to use for my family PC's? [Microsoft Help]
· [Internet] Gaming problem for "Heroes of Newerth" ( New bell Upd [Bell Canada]
· Are GPS's better today? [General Questions]
· Portable power for blackouts? [Home Repair & Improvement]
· filling an in-ground pool [Home Repair & Improvement]
· Considering Leaving Vonage, who should I Consider? [VOIP Tech Chat]
· Fun screwing with PuG raids. [World of Warcraft]
· [Snow Leopard] NFS Mounts - no more Directory Utility [All Things Macintosh]
· [Future9] Guaging interest. [VOIP Tech Chat]