Anybody understand these Line Stats etc

Forums › Spark New Zealand (including Skinny and BigPipe) › Anybody understand these Line Stats etc

1 | 2 | 3

32 posts

Geek

#327179 5-May-2010 23:28

Ok, well if drop-outs are logged at the Telecom end (still), it really is up to them to resolve rather than you do all the trouble-shooting and testing.

I would ask them to check your profile since you are on Bigtime intead of a standard plan and also whether being "too close" would cause problems (I am sure they would have checked anyway, but...) and also get them to check your interleaving.

If you ask these questions, you may get transferred to an more advance section of the helpdesk.

If at first you don't succeed; call it version 1.0

teletek

45 posts

Geek

#327183 5-May-2010 23:40

gi99a: Ok, well if drop-outs are logged at the Telecom end (still), it really is up to them to resolve rather than you do all the trouble-shooting and testing.

I would ask them to check your profile since you are on Bigtime intead of a standard plan and also whether being "too close" would cause problems (I am sure they would have checked anyway, but...) and also get them to check your interleaving.

If you ask these questions, you may get transferred to an more advance section of the helpdesk.

Just because they log a drop out doesn't mean it's a Telecom problem. It can still be on his end especially after the faultmen have tested the line, checked his internal wiring and changed the jack points and changed the port. Apart from changing his cable pairs and they may have done that already it is either something higher up the chain or possibly a dodgy phone, fax that is causing the drops.

He's still best to log and do some basic testing to ensure it isn't at his end.

I've seen faulty hubs, phones, computers causing apparent stalling of internet connections and the cust blaming telecom only to have it finally proved to what's plugged in at the customer end.

gi99a

32 posts

Geek

#327185 6-May-2010 00:04

Totally agree Teletek but that's all well and good for tech-savvy customers but average users cannot be expected to perform technical analysis. I'm not saying crazed isn't savvy as I am sure he is. :-)

Isolation testing is required (removing possible causes) e.g. removing everything from the line such as phones, sky decoders and even the filters... plug directly into the jack point with only the router in place and check performance.

For disconnections (where they see the loss of the connection) it is really up to Telecom to prove the line is not faulty.

I would still recommend asking Telecom to check the profile and also whether being "too close" would cause problems and check interleaving.

If at first you don't succeed; call it version 1.0

Detruire

1788 posts

Uber Geek
+1 received by user: 84

#327190 6-May-2010 00:37

Those stats aren't just good, they're spectacular.

rm *

teletek

45 posts

Geek

#327196 6-May-2010 05:35

gi99a: Totally agree Teletek but that's all well and good for tech-savvy customers but average users cannot be expected to perform technical analysis. I'm not saying crazed isn't savvy as I am sure he is. :-)

Isolation testing is required (removing possible causes) e.g. removing everything from the line such as phones, sky decoders and even the filters... plug directly into the jack point with only the router in place and check performance.

For disconnections (where they see the loss of the connection) it is really up to Telecom to prove the line is not faulty.

I would still recommend asking Telecom to check the profile and also whether being "too close" would cause problems and check interleaving.

Ok well you deal with it then. Hope you come up with better than telling him he has wrong firmware in his router, cos telling him not to bother with logging is going to leave him in the dark as to times and events on his connection.

crazed

484 posts

Ultimate Geek
+1 received by user: 26

Trusted

#327202 6-May-2010 07:17

gi99a: Totally agree Teletek but that's all well and good for tech-savvy customers but average users cannot be expected to perform technical analysis. I'm not saying crazed isn't savvy as I am sure he is. :-)

Isolation testing is required (removing possible causes) e.g. removing everything from the line such as phones, sky decoders and even the filters... plug directly into the jack point with only the router in place and check performance.

For disconnections (where they see the loss of the connection) it is really up to Telecom to prove the line is not faulty.

I would still recommend asking Telecom to check the profile and also whether being "too close" would cause problems and check interleaving.

Sorry mate I have already done isolation testing in the house, as I said further back. I have 14 years experience with I.T so isolation testing is the first thing I do even before contacting the help desk. I contacted Telecom about this becuase I had expended my own knowledge and experience trying to fix the problem.

These issues are noticable irrespective of which computer/phone/modem etc is plugged in. The only unusal item we have is the St Johns Medical alarm, which has also been isolated and verified as not the source of the problem.

From my last post in this thread I ran the Kiwisyslog and recorded overnight from the Dynalink Modem.

This is what I get:

05-06-2010    07:08:15    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=82.154.1.220 DST=125.238.84.6 LEN=60 TOS=0x00 PREC=0x40 TTL=44 ID=48133 DF PROTO=TCP SPT=38412 DPT=50873 WINDOW=5840 RES=0x00 SYN URGP=0
05-06-2010    06:55:26    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=80.198.147.230 DST=125.238.84.6 LEN=60 TOS=0x00 PREC=0x40 TTL=53 ID=20017 DF PROTO=TCP SPT=39833 DPT=51492 WINDOW=5840 RES=0x00 SYN URGP=0
05-06-2010    06:44:39    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=124.178.178.1 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=38375 DF PROTO=TCP SPT=2427 DPT=51492 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    06:34:06    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=91.153.152.8 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=101 ID=10498 DF PROTO=TCP SPT=51695 DPT=59196 WINDOW=8192 RES=0x00 SYN URGP=0
05-06-2010    06:31:26    Syslog.Info    192.168.1.1    -- MARK --
05-06-2010    06:24:06    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=65.95.98.158 DST=125.238.84.6 LEN=60 TOS=0x00 PREC=0x40 TTL=52 ID=41262 DF PROTO=TCP SPT=42313 DPT=59196 WINDOW=5840 RES=0x00 SYN URGP=0
05-06-2010    06:14:07    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=217.165.23.113 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x00 TTL=111 ID=50736 DF PROTO=TCP SPT=1420 DPT=59196 WINDOW=16384 RES=0x00 SYN URGP=0
05-06-2010    06:04:14    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=65.97.60.243 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=109 ID=45917 DF PROTO=TCP SPT=27539 DPT=59196 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    05:54:12    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=80.195.179.151 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=106 ID=1769 DF PROTO=TCP SPT=50246 DPT=59196 WINDOW=8192 RES=0x00 SYN URGP=0
05-06-2010    05:54:11    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=196.20.153.55 DST=125.238.84.6 LEN=60 TOS=0x00 PREC=0x00 TTL=111 ID=39796 DF PROTO=TCP SPT=3662 DPT=59196 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    05:54:09    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=80.195.179.151 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=106 ID=1607 DF PROTO=TCP SPT=50246 DPT=59196 WINDOW=8192 RES=0x00 SYN URGP=0
05-06-2010    05:54:07    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=120.28.197.71 DST=125.238.84.6 LEN=52 TOS=0x00 PREC=0x40 TTL=112 ID=53191 DF PROTO=TCP SPT=50248 DPT=59196 WINDOW=32767 RES=0x00 SYN URGP=0
05-06-2010    05:54:04    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=120.28.197.71 DST=125.238.84.6 LEN=52 TOS=0x00 PREC=0x40 TTL=112 ID=53107 DF PROTO=TCP SPT=50248 DPT=59196 WINDOW=32767 RES=0x00 SYN URGP=0
05-06-2010    05:48:02    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!
05-06-2010    05:35:49    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=93.182.188.121 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=107 ID=21933 DF PROTO=TCP SPT=54334 DPT=51492 WINDOW=8192 RES=0x00 SYN URGP=0
05-06-2010    05:31:26    Syslog.Info    192.168.1.1    -- MARK --
05-06-2010    05:29:45    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=221.209.17.174 DST=125.238.84.6 LEN=40 TOS=0x00 PREC=0x00 TTL=103 ID=256 PROTO=TCP SPT=6000 DPT=1433 WINDOW=16384 RES=0x00 SYN URGP=0
05-06-2010    05:18:33    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=58.215.75.62 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=109 ID=38744 PROTO=TCP SPT=21007 DPT=10000 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    05:08:17    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=82.154.1.220 DST=125.238.84.6 LEN=60 TOS=0x08 PREC=0x40 TTL=44 ID=54971 DF PROTO=TCP SPT=43058 DPT=50873 WINDOW=5840 RES=0x00 SYN URGP=0
05-06-2010    05:08:14    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=82.154.1.220 DST=125.238.84.6 LEN=60 TOS=0x00 PREC=0x40 TTL=44 ID=54970 DF PROTO=TCP SPT=43058 DPT=50873 WINDOW=5840 RES=0x00 SYN URGP=0
05-06-2010    04:52:56    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=125.238.236.245 DST=125.238.84.6 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=60545 DF PROTO=TCP SPT=4261 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
05-06-2010    04:37:36    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=70.45.16.155 DST=125.238.84.6 LEN=64 TOS=0x00 PREC=0x40 TTL=41 ID=51127 DF PROTO=TCP SPT=52473 DPT=18499 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    04:33:03    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=75.34.229.6 DST=125.238.84.6 LEN=64 TOS=0x00 PREC=0x40 TTL=51 ID=57394 DF PROTO=TCP SPT=49432 DPT=40892 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    04:31:26    Syslog.Info    192.168.1.1    -- MARK --
05-06-2010    04:21:13    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=82.234.136.216 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=107 ID=19775 DF PROTO=TCP SPT=63567 DPT=1223 WINDOW=8192 RES=0x00 SYN URGP=0
05-06-2010    04:21:07    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=82.234.136.216 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x40 TTL=107 ID=17722 DF PROTO=TCP SPT=63567 DPT=1223 WINDOW=8192 RES=0x00 SYN URGP=0
05-06-2010    04:19:33    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!
05-06-2010    03:56:43    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=115.64.173.180 DST=125.238.84.6 LEN=48 TOS=0x00 PREC=0x00 TTL=109 ID=30914 DF PROTO=TCP SPT=57555 DPT=4963 WINDOW=8192 RES=0x00 SYN URGP=0
05-06-2010    03:50:04    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!
05-06-2010    03:49:39    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=72.79.211.194 DST=125.238.84.6 LEN=52 TOS=0x00 PREC=0x40 TTL=45 ID=5344 DF PROTO=TCP SPT=1577 DPT=60802 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    03:49:36    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=72.79.211.194 DST=125.238.84.6 LEN=52 TOS=0x00 PREC=0x40 TTL=45 ID=4751 DF PROTO=TCP SPT=1577 DPT=60802 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    03:49:34    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=72.79.211.194 DST=125.238.84.6 LEN=52 TOS=0x00 PREC=0x40 TTL=45 ID=4417 DF PROTO=TCP SPT=1577 DPT=60802 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    03:31:26    Syslog.Info    192.168.1.1    -- MARK --
05-06-2010    03:20:46    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=78.46.109.82 DST=125.238.84.6 LEN=60 TOS=0x00 PREC=0x40 TTL=39 ID=5138 DF PROTO=TCP SPT=50020 DPT=1346 WINDOW=5840 RES=0x00 SYN URGP=0
05-06-2010    03:07:25    User.Alert    192.168.1.1    kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=75.34.229.6 DST=125.238.84.6 LEN=64 TOS=0x00 PREC=0x40 TTL=51 ID=19084 DF PROTO=TCP SPT=64005 DPT=40892 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010    03:04:32    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!
05-06-2010    03:00:14    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!
05-06-2010    02:59:29    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!
05-06-2010    02:57:53    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!
05-06-2010    02:57:22    User.Warning    192.168.1.1    kernel: MASQUERADE: No route: Rusty's brain broke!

CraZeD,
Your friendly Southern Geeky Fellow :P

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

MikeB4

MikeB4
18775 posts

Uber Geek
+1 received by user: 12766

ID Verified

Trusted

Subscriber

#327211 6-May-2010 07:59

This may sound daft but please hear me out , you have said that it starts around 8pm and goes through to around mid day the next day. I don't know what your living environment is but have you looked around your neighborhood to see if anything could be causing this. DSL is notoriously fussy to interference.

Look for ...

Larger than normal Satellite dish
Radio ham mast
Home work shop ( a car restorer or some one like that who works at night )
Electric security fence
Dodgy street lights

Here is a crazy notion, lets give peace a chance.

crazed

484 posts

Ultimate Geek
+1 received by user: 26

Trusted

#327232 6-May-2010 09:21

Thanks for the suggestions.

I have already ruled out Ham Radio as my Elderly Father who lives with my Wife and I is a Ham Radio operator and the disconnects don't correspond with his use of it.

As for the Log file if I'm reading this correctly based on information from Google, it looks like the modem disconnected a total of 9 times lastnight, with the worst being around 230am to 4am

CraZeD,
Your friendly Southern Geeky Fellow :P

MikeB4

MikeB4
18775 posts

Uber Geek
+1 received by user: 12766

ID Verified

Trusted

Subscriber

#327254 6-May-2010 09:54

Look further than your own home. The interference can come from further afield. Three , four ,eight houses away.
Have you asked neighbours if they are experiencing similar?

Here is a crazy notion, lets give peace a chance.

crazed

484 posts

Ultimate Geek
+1 received by user: 26

Trusted

#327262 6-May-2010 10:03

KiwiNZ: Look further than your own home. The interference can come from further afield. Three , four ,eight houses away.
Have you asked neighbours if they are experiencing similar?

Have asked the neighbours and none of them report any issues. I have just finished on the phone with Telecom, they have checked interleaving and the profile, and changed some small settings, they are now monitoring the line for 24 hours to check for any issues, then will contact us back tomorrow with the results.

CraZeD,
Your friendly Southern Geeky Fellow :P

gi99a

32 posts

Geek

#327361 6-May-2010 13:02

Hi Crazed - sorry, didn't mean to imply you hadn't done isolation testing, just saying that is what telecom expect and certainly not questioning your technical ability.

Teletek, dude! chill out, I am not saying I am right and yes I did make a slight error, I was too keen to help and didn't read the info I found.

KiwiNZ does make some good points, sometimes over-looked.

in regards to "kernel: Intrusion "... isn't that just the firewall of the router indicating connection attempts from other IP addresses (scanning ports)? You running a torrent?

If at first you don't succeed; call it version 1.0

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

teletek

45 posts

Geek

#327366 6-May-2010 13:13

crazed:
gi99a: Totally agree Teletek but that's all well and good for tech-savvy customers but average users cannot be expected to perform technical analysis. I'm not saying crazed isn't savvy as I am sure he is. :-)

Isolation testing is required (removing possible causes) e.g. removing everything from the line such as phones, sky decoders and even the filters... plug directly into the jack point with only the router in place and check performance.

For disconnections (where they see the loss of the connection) it is really up to Telecom to prove the line is not faulty.

I would still recommend asking Telecom to check the profile and also whether being "too close" would cause problems and check interleaving.

Sorry mate I have already done isolation testing in the house, as I said further back. I have 14 years experience with I.T so isolation testing is the first thing I do even before contacting the help desk. I contacted Telecom about this becuase I had expended my own knowledge and experience trying to fix the problem.

These issues are noticable irrespective of which computer/phone/modem etc is plugged in. The only unusal item we have is the St Johns Medical alarm, which has also been isolated and verified as not the source of the problem.

From my last post in this thread I ran the Kiwisyslog and recorded overnight from the Dynalink Modem.

This is what I get:

0
05-06-2010 03:07:25 User.Alert 192.168.1.1 kernel: Intrusion -> IN=ppp_0_100_1 OUT= MAC= SRC=75.34.229.6 DST=125.238.84.6 LEN=64 TOS=0x00 PREC=0x40 TTL=51 ID=19084 DF PROTO=TCP SPT=64005 DPT=40892 WINDOW=65535 RES=0x00 SYN URGP=0
05-06-2010 03:04:32 User.Warning 192.168.1.1 kernel: MASQUERADE: No route: Rusty's brain

Ok well all those messages are firewall violations. No line drops in there.

Can you post your Adsl Line Status page again like you had in your first post.

That will show us what counters have gone up over the last 12+ hours.

Cheers

crazed

484 posts

Ultimate Geek
+1 received by user: 26

Trusted

#327381 6-May-2010 14:06

Line Mode     G.DMT       Line State     Show Time
Latency Type     Interleave     Line Up Time     00:04:11:15
Line Coding     Trellis On     Line Up Count     2

Statistics     Downstream     Upstream
Line Rate     7616 Kbps     896 Kbps
Attainable Line Rate     10176 Kbps     1200 Kbps
Noise Margin     18.9 dB     16.0 dB
Line Attenuation     4.0 dB     2.5 dB
Output Power     7.8 dBm     12.2 dBm
K (number of bytes in DMT frame)     239     29
R (number of check bytes in RS code word)     16     16
S (RS code word size in DMT frame)     1     8
D (interleave depth)     64     8
Super Frames     886709     886668
Super Frame Errors     0     0
RS Words     60296278     7536678
RS Correctable Errors     698     19
RS Uncorrectable Errors     0     0
HEC Errors     0     0
OCD Errors     0     0
LCD Errors     0     0
Total Cells     270765039     0
Data Cells     874602     0
Bit Errors     0     0
Total ES     5     0
Total SES     1     0
Total UAS     33     0

Telecom have done some changes on the line this morning and for the time being it seems to be stable. They also have the line under "Live monitoring" and I have been asked not to disconnect the modem at all or manually reconnect so that they can see any activity on the line. Since they did the changes this morning I have noticed a speed increase.

CraZeD,
Your friendly Southern Geeky Fellow :P

gi99a

32 posts

Geek

#327401 6-May-2010 14:37

crazed: Line Mode     G.DMT       Line State     Show Time
Latency Type     Interleave     Line Up Time     00:04:11:15
Line Coding     Trellis On     Line Up Count     2

Statistics     Downstream     Upstream
Line Rate     7616 Kbps     896 Kbps
Attainable Line Rate     10176 Kbps     1200 Kbps
Noise Margin     18.9 dB     16.0 dB
Line Attenuation     4.0 dB     2.5 dB
Output Power     7.8 dBm     12.2 dBm
K (number of bytes in DMT frame)     239     29
R (number of check bytes in RS code word)     16     16
S (RS code word size in DMT frame)     1     8
D (interleave depth)     64     8
Super Frames     886709     886668
Super Frame Errors     0     0
RS Words     60296278     7536678
RS Correctable Errors     698     19
RS Uncorrectable Errors     0     0
HEC Errors     0     0
OCD Errors     0     0
LCD Errors     0     0
Total Cells     270765039     0
Data Cells     874602     0
Bit Errors     0     0
Total ES     5     0
Total SES     1     0
Total UAS     33     0

Telecom have done some changes on the line this morning and for the time being it seems to be stable. They also have the line under "Live monitoring" and I have been asked not to disconnect the modem at all or manually reconnect so that they can see any activity on the line. Since they did the changes this morning I have noticed a speed increase.

I note the connect rates are now the expected 7616 down.

It would be interesting to know what Telecom changed.

I had PM'd you earlier, crazed, incase you needed further assistance.

all the best.

If at first you don't succeed; call it version 1.0

crazed

484 posts

Ultimate Geek
+1 received by user: 26

Trusted

#327407 6-May-2010 15:19

gi99a:
crazed: Line Mode     G.DMT       Line State     Show Time
Latency Type     Interleave     Line Up Time     00:04:11:15
Line Coding     Trellis On     Line Up Count     2

Statistics     Downstream     Upstream
Line Rate     7616 Kbps     896 Kbps
Attainable Line Rate     10176 Kbps     1200 Kbps
Noise Margin     18.9 dB     16.0 dB
Line Attenuation     4.0 dB     2.5 dB
Output Power     7.8 dBm     12.2 dBm
K (number of bytes in DMT frame)     239     29
R (number of check bytes in RS code word)     16     16
S (RS code word size in DMT frame)     1     8
D (interleave depth)     64     8
Super Frames     886709     886668
Super Frame Errors     0     0
RS Words     60296278     7536678
RS Correctable Errors     698     19
RS Uncorrectable Errors     0     0
HEC Errors     0     0
OCD Errors     0     0
LCD Errors     0     0
Total Cells     270765039     0
Data Cells     874602     0
Bit Errors     0     0
Total ES     5     0
Total SES     1     0
Total UAS     33     0

Telecom have done some changes on the line this morning and for the time being it seems to be stable. They also have the line under "Live monitoring" and I have been asked not to disconnect the modem at all or manually reconnect so that they can see any activity on the line. Since they did the changes this morning I have noticed a speed increase.

I note the connect rates are now the expected 7616 down.

It would be interesting to know what Telecom changed.

I had PM'd you earlier, crazed, incase you needed further assistance.

all the best.

Yea they didn't go into detail with what they were doing, it was tier 2 support I was dealing with. I know they have turned Interleaving back on and a couple of other changes. Its pretty good at present so for the time being I'm happy. I'm using the Dynalink ADSL2+ RTA1320 which is humming along.

Yes I got your PM and thanks for the offer, Will keep it in mind.

CraZeD,
Your friendly Southern Geeky Fellow :P

1 | 2 | 3