LQR problems on 256/128k links?

[Neil Gardner]

Hi guys - has anyone seen any evidence that the 256/128k ADSL links
cause any problems for LQR? I have an individual instance of a router
giving errors like this...

01 23:25:29 5 PPP DLINK ERROR ppp0: An LQR failure has occurred on primary
link over atm0.1
01 23:25:29 5 PPP DLINK DOWN ppp0: Primary link over atm0.1 has closed
01 23:25:29 5 PPP VINT DOWN ppp0: Interface has gone down and is unable to
send or receive data
01 23:25:29 3 IPG CIRC CONF Local request to reset ppp0 IP accepted
01 23:25:29 3 CH MSG WARN Dynamically configured name servers deleted
01 23:25:36 5 PPP DLINK DOWN ppp0: Primary link over atm0.1 has closed
01 23:25:36 3 PPP VINT UP ppp0: Interface has come up and is able to send
and receive data
01 23:25:36 3 PPP AUTH OK ppp0: PAP authentication over atm0.1 succeeded
01 23:25:36 5 IPG CIRC CONF Interface 00000800 is not renumbered, cannot
reset IP address
01 23:25:36 3 IPG CIRC CONF Remote request to set ppp0 IP to
1.2.3.4 (edited- NeilG)
accepted
01 23:27:35 5 PPP DLINK ERROR ppp0: An LQR failure has occurred on primary
link over atm0.1
01 23:27:35 5 PPP DLINK DOWN ppp0: Primary link over atm0.1 has closed
01 23:27:35 5 PPP VINT DOWN ppp0: Interface has gone down and is unable to
send or receive data

It's a product in development so it's not necessarily a problem, and I
am going through the process of trying another router on the line in
question and getting the router in question to a known good location
but I'm remote controlling everything so I thought I'd see if anyone
has noticed anything like this in recent times...

Cheers - Neil Gardner

[Ian Batterbee]

Post by Neil Gardner
Hi guys - has anyone seen any evidence that the 256/128k ADSL links
cause any problems for LQR? I have an individual instance of a router
giving errors like this...

LQR... meaning Link Quality Report, I think.. Which would indicate a line noise issue, presumably ?

[Garry Konings]

No LQR reports, but the last two nights I have had PPPoA LCP (repeated
re-)negotiation failed problems on my 256/128K line, to the extent it is
unusable.

Only happens after hours when I can't ring a Help desk to complain about
it of course!

-----Original Message-----
From: owner-***@unixathome.org [mailto:owner-***@unixathome.org] On
Behalf Of Ian Batterbee
Sent: Wednesday, 2 February 2005 5:14 p.m.
To: ***@lists.unixathome.org
Subject: Re: LQR problems on 256/128k links?

Post by Neil Gardner
Hi guys - has anyone seen any evidence that the 256/128k ADSL links
cause any problems for LQR? I have an individual instance of a router
giving errors like this...

LQR... meaning Link Quality Report, I think.. Which would indicate a
line noise issue, presumably ?
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.4 - Release Date: 1/02/2005

[LEE Tet Yoon]

Post by Garry Konings
No LQR reports, but the last two nights I have had PPPoA LCP (repeated
re-)negotiation failed problems on my 256/128K line, to the extent it is
unusable.
Only happens after hours when I can't ring a Help desk to complain about
it of course!

I have had similar problems. I'm using a M1122 and I haven't found anywhere where it specifically says what the problem is (haven't logged on with admin mode for a while tho, maybe that's why). However, I have had authentication problems every so often, usually at night (although maybe it happens during the afternoon of weekdays as well, never really looked into it). It fixed itself eventually but very frustrating.

BTW, I'm using bitstream (with Orcon)

[Garry Konings]

I'm with Orcon too. Got an email from them today explaining that they
have basically hit the wall on the capacity of their 155Mbps ATM circuit
from Telecom. They are working with Telecom to add another circuit but
claim that Telecom are facing some challenges spreading Orcon Bitstream
customer traffic over the two circuits. Hope they fix it soon!

Not sure yet if this really explains my problem completely, as I am
getting link disconnects, not just high latency/slowness. i.e yes, the
service is reeeeeally reeeeeally slow when I am connected, but most of
the time I'm actually just in a (re-) "Connecting..." State) with NO
throughput at all!

If the links they talk about are the ones that collect all the Orcon
Bitstream users' traffic and feed it to Orcon's servers, then I guess an
existing PPPoA session could end up being crashed due to packet
loss/timeouts on the oversubscribed 155M link??? (anyone who knows want
to comment?).

However, I also suspect I may be suffering congestion due to
oversubscription of my local DSLAM link (2MBps supporting 28 customers!
If each customer is on a 256/128kbps plan , and we all surf at the same
time in the evening, you work out how many times oversubscribed that
is!).

Here's a question I have. How does an ISP influence Telecom to increase
capacity on oversubscribed Jetstream DSLAM collection links (that are
shared by users subscribing to multiple different ISP's, not just their
own customers)? (In my case, I believe all I can do is complain to
Orcon, not to Telecom directly). Can any ISP pinpoint issues caused by
over-utilisation of common resources that they don't themselves manage?



-----Original Message-----
From: owner-***@unixathome.org [mailto:owner-***@unixathome.org] On
Behalf Of LEE Tet Yoon
Sent: Wednesday, 2 February 2005 11:38 p.m.
To: ***@lists.unixathome.org
Subject: RE: LQR problems on 256/128k links?

Post by Garry Konings
No LQR reports, but the last two nights I have had PPPoA LCP (repeated
re-)negotiation failed problems on my 256/128K line, to the extent it
is unusable.
Only happens after hours when I can't ring a Help desk to complain
about it of course!

I have had similar problems. I'm using a M1122 and I haven't found
anywhere where it specifically says what the problem is (haven't logged
on with admin mode for a while tho, maybe that's why). However, I have
had authentication problems every so often, usually at night (although
maybe it happens during the afternoon of weekdays as well, never really
looked into it). It fixed itself eventually but very frustrating.

BTW, I'm using bitstream (with Orcon)
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.4 - Release Date: 1/02/2005