on 01-10-2010 18h41
Hello BTCare forum
This is my first post, so please forgive me if I'm asking a question that's been answered. I've Googled and searched the forums but not found anything so far...
Here's the situation ... I've had BT BB for three years and ADSL2+ for about six months. It's all been fine and really solid as long as I can remember.
A few days ago the PPP started going up and down, even though the ADSL link is really steady and stays up. I've phoned BT and they did some line tests, but I don't think the problem is with the line or with my DSL profile.
Here's an example of my Connection logs for today:
The funny thing is the ADSL itself is up all the time, as indicated by the ADSL line status page.
So here's my question -- why would the PPP keep going up and down even when there's no problem with the ADSL? Any ideas?
Solved! Go to Solution.
on 01-10-2010 20h41
Ive been having pretty much the exact same issue. The PPP is just dropping like no bodies business but my ADSL is rock solid.
Heres my thread about it, but not getting anywhere.
Are you getting any other problems? Im having insane amounts of packet loss and a real mix up with download speeds and my IP profile going up and down.
That said, Ive spoken to BT and they are acknowledging that there is a problem. At first the guy did some tests and it said there wasnt any problem - I figure this is because its an intermittent drop. If they say theres nothing wrong, ask them to do more tests maybe.
Hopefully itll get fixed so this problem will have definitely been on BTs end.
on 03-10-2010 11h33
I read through your posts and the various links and it looks like we may have the same issue.
Here's this morning's logs...
At no time did the ADSL go down. It's been up for over 3 days since I last powercycled the HH2.
I think I have packet loss too. When we use any streaming service like the BBC radio or iPlayer it drops out between every 3 minutes and every 15 minutes. Annoying enough that you can't use the service.
I've just tried speedtest.net and get this:
And this is my line state:
ADSL line status
|Connection time||3 days, 16:14:58|
|Noise margin (Down/Up)||4.1 dB / 5.6 dB|
|Line attenuation (Down/Up)||32.0 dB / 16.6 dB|
|Output power (Down/Up)||0.0 dBm / 13.0 dBm|
|Loss of Framing (Local)||41|
|Loss of Signal (Local)||4|
|Loss of Power (Local)||0|
|FEC Errors (Down/Up)||7704283 / 0|
|CRC Errors (Down/Up)||397 / 2147480000|
|HEC Errors (Down/Up)||nil / 0|
|Error Seconds (Local)||287|
I'm on the Falmouth telephone exchange, WWFALM.
Does anyone know why the ADSL itself stays up even though the PPP goes up and down? Could this still be a line noise problem? Are the FEC/CRC/HEC errors particularly bad?
I've not heard back from BT's call centre, they were going to call me but didn't. Should I call them back? The adviser I originally spoke to said I shouldn't call back about the problem and I should wait for them...
Many thanks again for any help, its much appreciated.
on 03-10-2010 11h42
I think FEC is pretty poor but the crc is a hub bug and meaningless
on 03-10-2010 11h53
This is my result from the BT Speedtester:
I've no idea what to do next. From my little understanding of what's going on, from what I've read in other posts, it looks like the problem as at the BT exchange. But how can I be sure of that and what can BT do to fix it?
Welcome to the world of BT broadband mysteries, I suppose...
on 03-10-2010 12h08
Oh dear, things don't looks so good on the ping test:
OK, so here's my new question:
Has anyone who's had similar problems to mine got the problem solved and if so what was done to solve the problem?
As always, any help gratefully received.
on 03-10-2010 12h28
Martin - you could try the following:-
ping your router 192.168.1.254
then ping the default gateway found in hub manager under advanced/broadband
Do these pings from a command prompt and post the results.
This is to prove you have packet loss on the link. You would want to do this while you are having the ppp down/up events.
on 03-10-2010 12h55
This is what I get from the router:
PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=1.010 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.820 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.587 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.716 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=0.696 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=0.984 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=0.667 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=0.724 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=0.808 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=0.779 ms
And this is what I get from the gateway:
PING 184.108.40.206 (220.127.116.11): 56 data bytes
64 bytes from 18.104.22.168: icmp_seq=0 ttl=254 time=53.449 ms
64 bytes from 22.214.171.124: icmp_seq=1 ttl=254 time=53.187 ms
64 bytes from 126.96.36.199: icmp_seq=2 ttl=254 time=50.627 ms
64 bytes from 188.8.131.52: icmp_seq=3 ttl=254 time=47.132 ms
64 bytes from 184.108.40.206: icmp_seq=4 ttl=254 time=54.509 ms
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
64 bytes from 220.127.116.11: icmp_seq=7 ttl=254 time=54.153 ms
64 bytes from 18.104.22.168: icmp_seq=8 ttl=254 time=51.960 ms
64 bytes from 22.214.171.124: icmp_seq=9 ttl=254 time=50.467 ms
64 bytes from 126.96.36.199: icmp_seq=10 ttl=254 time=50.751 ms
64 bytes from 188.8.131.52: icmp_seq=11 ttl=254 time=53.207 ms
64 bytes from 184.108.40.206: icmp_seq=12 ttl=254 time=49.017 ms
64 bytes from 220.127.116.11: icmp_seq=13 ttl=254 time=55.890 ms
64 bytes from 18.104.22.168: icmp_seq=14 ttl=254 time=56.365 ms
64 bytes from 22.214.171.124: icmp_seq=15 ttl=254 time=54.669 ms
64 bytes from 126.96.36.199: icmp_seq=16 ttl=254 time=48.231 ms
64 bytes from 188.8.131.52: icmp_seq=17 ttl=254 time=53.596 ms
64 bytes from 184.108.40.206: icmp_seq=18 ttl=254 time=52.848 ms
64 bytes from 220.127.116.11: icmp_seq=19 ttl=254 time=53.898 ms
64 bytes from 18.104.22.168: icmp_seq=20 ttl=254 time=53.602 ms
64 bytes from 22.214.171.124: icmp_seq=21 ttl=254 time=52.241 ms
64 bytes from 126.96.36.199: icmp_seq=22 ttl=254 time=49.170 ms
Request timeout for icmp_seq 23
64 bytes from 188.8.131.52: icmp_seq=24 ttl=254 time=52.029 ms
64 bytes from 184.108.40.206: icmp_seq=25 ttl=254 time=50.838 ms
Does the Request timeout mean I'm having packet loss?
The results I'm getting from pingtest are crazy, 835ms latency sometimes more, 1566ms jitter:
From these results, what do you think?
on 03-10-2010 13h12
Well well well.
This is definitely something up with BT.
Because guess where I live. In Falmouth too.
Where abouts are you? I live down on Bar Lane/Road right down near the Docks entrance.
I rung up BT, they admitted a fault and said that they were going to fix it. They didnt ring me yesterday then rung me this morning. They left me a voice message which didnt really allude to whether they had fixed it or not. They just said to ring again if I had any problems. Which sounds like they must have tried to fix something.
Im gonna get into contact with BT shortly so Ill mention this.
03-10-2010 13h34 - edited 03-10-2010 13h39
I was getting to the point where I was sure this was a problem in or beyond the exchange, not on the line or in the house.
We're at the bottom of Arwenack Avenue, near Grovehill Crescent, not far from you.