Destroyed by Packet Loss and Dropped Connections

Desaan · May 28, 2012, 03:02:06

The last few days my connection has been stone age, insane lag and packet loss. My connection also drops frequently, like 15 times and hour frequently. I've changed cables, routers, checked faceplates and filters done quite line tests and checked all known sources for service statuses and outages. Nada, nothing, zero. Still exactly the same.

Some logs:

05/28/2012 02:42:02   If(ATM1) PPP connection ok !
05/28/2012 02:42:01   ATM1 get IP:212.69.62.90
05/28/2012 02:42:00   ATM1 start PPP
05/28/2012 02:41:59   If(3) PPP Dial timeout :< 102000
05/28/2012 02:40:17   ATM1 start PPP
05/28/2012 02:40:17   If(3) PPP Dial timeout :< 100001
05/28/2012 02:38:37   ATM1 start PPP
05/28/2012 02:38:36   If(3) PPP Dial timeout :< 100002
05/28/2012 02:38:35   ATM1 get IP:212.69.62.90
05/28/2012 02:36:56   ATM1 start PPP
05/28/2012 02:36:56   Dial On Demand(ATM1)
05/28/2012 02:36:56   If(3) PPP Dial timeout :< 100001
05/28/2012 02:35:16   ATM1 start PPP
05/28/2012 02:35:16   If(ATM1) PPP fail : Peer terminate
05/28/2012 02:35:04   ATM1 start PPP
05/28/2012 02:35:04   Dial On Demand(ATM1)
05/28/2012 02:35:04   If(3) PPP Dial timeout :< 102000
05/28/2012 02:33:22   ATM1 start PPP
05/28/2012 02:29:47   If(ATM1) PPP connection ok !
05/28/2012 02:29:46   ATM1 get IP:212.69.62.90
05/28/2012 02:29:20   ATM1 start PPP
05/28/2012 02:29:20   If(3) PPP Dial timeout :< 102000
05/28/2012 02:27:38   ATM1 start PPP
05/28/2012 02:10:45   If(ATM1) PPP connection ok !
05/28/2012 02:10:44   ATM1 get IP:212.69.62.90
05/28/2012 02:10:24   ATM1 start PPP
05/28/2012 02:10:24   If(ATM1) PPP fail : Peer terminate
05/28/2012 02:10:22   ATM1 start PPP
05/28/2012 02:10:21   ADSL Media Up !
05/28/2012 02:10:18   If(ATM1) PPP fail : Timeout in LCP negotiation
05/28/2012 02:09:27   ADSL Media Down !
05/28/2012 02:09:26   ATM1 start PPP
05/28/2012 02:09:26   If(ATM1) PPP fail : Timeout in LCP negotiation
05/28/2012 02:08:34   ATM1 start PPP
05/28/2012 02:08:34   If(ATM1) PPP fail : Peer terminate
05/28/2012 02:08:22   ATM1 start PPP
05/28/2012 02:08:18   ATM1 stop PPP
05/28/2012 02:08:00   If(ATM1) PPP connection ok !
05/28/2012 02:07:59   ATM1 get IP:212.69.62.90
05/28/2012 02:07:44   ATM1 start PPP
05/28/2012 02:07:43   If(ATM1) PPP fail : Timeout in CHAP negotiation
05/28/2012 02:07:21   ATM1 start PPP
05/28/2012 02:07:21   If(ATM1) PPP fail : CHAP authentication failure
05/28/2012 02:07:19   ATM1 start PPP
05/28/2012 02:07:19   If(ATM1) PPP fail : CHAP authentication failure
05/28/2012 02:07:17   ATM1 start PPP
05/28/2012 02:07:17   If(ATM1) PPP fail : CHAP authentication failure
05/28/2012 02:07:15   ATM1 start PPP
05/28/2012 02:07:15   If(ATM1) PPP fail : CHAP authentication failure
05/28/2012 02:07:13   ATM1 start PPP
05/28/2012 02:07:13   If(ATM1) PPP fail : CHAP authentication failure
05/28/2012 02:07:11   ATM1 start PPP
05/28/2012 02:07:11   If(ATM1) PPP fail : CHAP authentication failure

Tracerts:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 24 ms * 23 ms bt1.idnet.net [212.69.63.42]
3 27 ms 29 ms * redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
4 * 26 ms 28 ms www.idnet.net [212.69.36.10]

Trace complete.

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * 23 ms bt1.idnet.net [212.69.63.42]
3 * * * Request timed out.
4 * * * Request timed out.
5 * 25 ms 25 ms www.idnet.net [212.69.36.10]

1 <1 ms <1 ms <1 ms 192.168.2.1
2 25 ms 27 ms * bt1.idnet.net [212.69.63.42]
3 * 26 ms * redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
4 23 ms * * www.idnet.net [212.69.36.10]
5 * * * Request timed out.
6 24 ms * * www.idnet.net [212.69.36.10]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * 192.168.2.1 reports: Destination net unreachable.

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * 23 ms bt1.idnet.net [212.69.63.42]
3 25 ms * 22 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
4 * * * Request timed out.
5 23 ms * 28 ms www.idnet.net [212.69.36.10]

1 <1 ms <1 ms <1 ms 192.168.2.1
2 27 ms * * bt1.idnet.net [212.69.63.42]
3 * * 26 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 24 ms * * www.idnet.net [212.69.36.10]
8 * 24 ms 28 ms www.idnet.net [212.69.36.10]

1 <1 ms <1 ms <1 ms 192.168.2.1
2 27 ms * 25 ms bt1.idnet.net [212.69.63.42]
3 23 ms * 28 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
4 * 23 ms 25 ms www.idnet.net [212.69.36.10]

It's been a while since I did a tracert and I've never seen bt1.idnet.net before. Obviously I've emailed support but what gives? What could possibly cause such a massive failure in service considering nothing at my end has changed?

sparkler · May 28, 2012, 05:35:57

my connection has been messed up for the last few days as well

Sat, 2000-01-01 00:01:31 - Initialize LCP.
Sat, 2000-01-01 00:01:31 - LCP is allowed to come up.
Sat, 2000-01-01 00:01:42 - CHAP authentication success
Sat, 2000-01-01 00:01:48 - Send out NTP request to time-g.netgear.com
Fri, 2012-05-25 02:25:10 - Receive NTP Reply from time-g.netgear.com
Fri, 2012-05-25 02:26:45 - LCP down.
Fri, 2012-05-25 02:27:01 - Initialize LCP.
Fri, 2012-05-25 02:27:01 - LCP is allowed to come up.
Fri, 2012-05-25 02:28:02 - Initialize LCP.
Fri, 2012-05-25 02:28:02 - LCP is allowed to come up.
Fri, 2012-05-25 02:29:02 - Initialize LCP.
Fri, 2012-05-25 02:29:02 - LCP is allowed to come up.
Fri, 2012-05-25 02:30:02 - Initialize LCP.
Fri, 2012-05-25 02:30:02 - LCP is allowed to come up.
Fri, 2012-05-25 02:30:10 - CHAP authentication success
Fri, 2012-05-25 02:31:55 - LCP down.
Fri, 2012-05-25 02:32:52 - Initialize LCP.
Fri, 2012-05-25 02:32:52 - LCP is allowed to come up.
Fri, 2012-05-25 02:33:08 - CHAP authentication success
Fri, 2012-05-25 03:23:21 - Router start up
Fri, 2012-05-25 02:34:42 - LCP down.
Fri, 2012-05-25 02:34:49 - Initialize LCP.
Fri, 2012-05-25 02:34:49 - LCP is allowed to come up.
Fri, 2012-05-25 02:35:49 - Initialize LCP.
Fri, 2012-05-25 02:35:49 - LCP is allowed to come up.
Fri, 2012-05-25 02:36:49 - Initialize LCP.
Fri, 2012-05-25 02:36:49 - LCP is allowed to come up.
Fri, 2012-05-25 02:37:50 - Initialize LCP.
Fri, 2012-05-25 02:37:50 - LCP is allowed to come up.
Fri, 2012-05-25 02:38:50 - Initialize LCP.
Fri, 2012-05-25 02:38:50 - LCP is allowed to come up.
Fri, 2012-05-25 02:39:50 - Initialize LCP.
Fri, 2012-05-25 02:39:50 - LCP is allowed to come up.
Fri, 2012-05-25 02:40:50 - Initialize LCP.
Fri, 2012-05-25 02:40:50 - LCP is allowed to come up.
Fri, 2012-05-25 02:41:10 - CHAP authentication success
Fri, 2012-05-25 04:32:45 - Initialize LCP.
Fri, 2012-05-25 04:32:45 - LCP is allowed to come up.
Fri, 2012-05-25 04:32:54 - CHAP authentication success
Fri, 2012-05-25 04:33:28 - Administrator login successful - IP:192.168.0.2
Fri, 2012-05-25 04:37:58 - LCP down.
Fri, 2012-05-25 04:38:01 - Administrator login successful - IP:192.168.0.2
Fri, 2012-05-25 04:38:05 - Initialize LCP.
Fri, 2012-05-25 04:38:05 - LCP is allowed to come up.
Fri, 2012-05-25 04:38:15 - CHAP authentication success
Fri, 2012-05-25 12:18:39 - LCP down.
Fri, 2012-05-25 12:19:21 - Initialize LCP.
Fri, 2012-05-25 12:19:21 - LCP is allowed to come up.
Fri, 2012-05-25 12:19:30 - CHAP authentication success
Fri, 2012-05-25 15:29:05 - LCP down.
Fri, 2012-05-25 15:30:12 - Initialize LCP.
Fri, 2012-05-25 15:30:12 - LCP is allowed to come up.
Fri, 2012-05-25 15:31:12 - Initialize LCP.
Fri, 2012-05-25 15:31:12 - LCP is allowed to come up.
Fri, 2012-05-25 15:32:12 - Initialize LCP.
Fri, 2012-05-25 15:32:12 - LCP is allowed to come up.
Fri, 2012-05-25 15:33:12 - Initialize LCP.
Fri, 2012-05-25 15:33:12 - LCP is allowed to come up.
Fri, 2012-05-25 15:34:12 - Initialize LCP.
Fri, 2012-05-25 15:34:12 - LCP is allowed to come up.
Fri, 2012-05-25 15:35:12 - Initialize LCP.
Fri, 2012-05-25 15:35:12 - LCP is allowed to come up.
Fri, 2012-05-25 15:36:12 - Initialize LCP.
Fri, 2012-05-25 15:36:12 - LCP is allowed to come up.
Fri, 2012-05-25 15:37:13 - Initialize LCP.
Fri, 2012-05-25 15:37:13 - LCP is allowed to come up.
Fri, 2012-05-25 15:38:13 - Initialize LCP.
Fri, 2012-05-25 15:38:13 - LCP is allowed to come up.
Fri, 2012-05-25 15:38:41 - CHAP authentication success
Fri, 2012-05-25 15:47:45 - LCP down.
Fri, 2012-05-25 15:47:52 - Initialize LCP.
Fri, 2012-05-25 15:47:52 - LCP is allowed to come up.
Fri, 2012-05-25 15:48:01 - CHAP authentication success
Fri, 2012-05-25 20:58:35 - LCP down.
Fri, 2012-05-25 20:58:42 - Initialize LCP.
Fri, 2012-05-25 20:58:42 - LCP is allowed to come up.
Fri, 2012-05-25 20:58:50 - CHAP authentication success
Fri, 2012-05-25 22:21:11 - Initialize LCP.
Fri, 2012-05-25 22:21:11 - LCP is allowed to come up.
Fri, 2012-05-25 22:21:20 - CHAP authentication success
Sat, 2012-05-26 10:58:15 - Initialize LCP.
Sat, 2012-05-26 10:58:15 - LCP is allowed to come up.
Sat, 2012-05-26 10:58:24 - CHAP authentication success
Sat, 2012-05-26 15:28:59 - LCP down.
Sat, 2012-05-26 15:29:05 - Initialize LCP.
Sat, 2012-05-26 15:29:05 - LCP is allowed to come up.
Sat, 2012-05-26 15:29:14 - CHAP authentication success
Sat, 2012-05-26 15:30:28 - LCP down.
Sat, 2012-05-26 15:32:56 - Initialize LCP.
Sat, 2012-05-26 15:32:56 - LCP is allowed to come up.
Sat, 2012-05-26 15:33:05 - CHAP authentication success
Sat, 2012-05-26 20:50:40 - Initialize LCP.
Sat, 2012-05-26 20:50:40 - LCP is allowed to come up.
Sat, 2012-05-26 20:50:48 - CHAP authentication success
Sat, 2012-05-26 20:53:03 - LCP down.
Sat, 2012-05-26 20:53:25 - Initialize LCP.
Sat, 2012-05-26 20:53:25 - LCP is allowed to come up.
Sat, 2012-05-26 20:53:40 - CHAP authentication success
Sun, 2012-05-27 08:53:53 - Initialize LCP.
Sun, 2012-05-27 08:53:53 - LCP is allowed to come up.
Sun, 2012-05-27 08:54:01 - CHAP authentication success
Sun, 2012-05-27 08:54:13 - Administrator login successful - IP:192.168.0.2
Sun, 2012-05-27 09:29:16 - LCP down.
Sun, 2012-05-27 09:29:43 - Initialize LCP.
Sun, 2012-05-27 09:29:43 - LCP is allowed to come up.
Sun, 2012-05-27 09:29:52 - CHAP authentication success
Sun, 2012-05-27 09:33:36 - LCP down.
Sun, 2012-05-27 09:34:53 - Initialize LCP.
Sun, 2012-05-27 09:34:53 - LCP is allowed to come up.
Sun, 2012-05-27 09:35:02 - CHAP authentication success
Sun, 2012-05-27 09:37:16 - LCP down.
Sun, 2012-05-27 09:37:23 - Initialize LCP.
Sun, 2012-05-27 09:37:23 - LCP is allowed to come up.
Sun, 2012-05-27 09:38:23 - Initialize LCP.
Sun, 2012-05-27 09:38:23 - LCP is allowed to come up.
Sun, 2012-05-27 09:39:23 - Initialize LCP.
Sun, 2012-05-27 09:39:23 - LCP is allowed to come up.
Sun, 2012-05-27 09:39:39 - CHAP authentication success
Sun, 2012-05-27 09:56:51 - Initialize LCP.
Sun, 2012-05-27 09:56:51 - LCP is allowed to come up.
Sun, 2012-05-27 09:56:59 - CHAP authentication success
Sun, 2012-05-27 10:11:04 - LCP down.
Sun, 2012-05-27 10:11:56 - Initialize LCP.
Sun, 2012-05-27 10:11:56 - LCP is allowed to come up.
Sun, 2012-05-27 10:12:04 - CHAP authentication success
Sun, 2012-05-27 17:38:11 - Initialize LCP.
Sun, 2012-05-27 17:38:11 - LCP is allowed to come up.
Sun, 2012-05-27 17:38:19 - CHAP authentication success
Mon, 2012-05-28 00:25:10 - Send out NTP request to time-g.netgear.com
Mon, 2012-05-28 00:25:12 - Receive NTP Reply from time-g.netgear.com
Mon, 2012-05-28 05:27:58 - Initialize LCP.
Mon, 2012-05-28 05:27:58 - LCP is allowed to come up.
Mon, 2012-05-28 05:28:26 - Administrator login successful - IP:192.168.0.2
Mon, 2012-05-28 05:28:58 - Initialize LCP.
Mon, 2012-05-28 05:28:58 - LCP is allowed to come up.
Mon, 2012-05-28 05:29:58 - Initialize LCP.
Mon, 2012-05-28 05:29:58 - LCP is allowed to come up.
Mon, 2012-05-28 05:30:59 - Initialize LCP.
Mon, 2012-05-28 05:30:59 - LCP is allowed to come up.
Mon, 2012-05-28 05:31:07 - CHAP authentication success

Steve · May 28, 2012, 06:30:18

No idea , my guess is BT faults or work possibly, if there was an IDNet issue I think we'd see more forum complaints over this period.

Anything showing here for your location feed://www.idnet.net/statusrss.php (rss feed) http://aaisp-btmso.blogspot.co.uk/ http://status.zen.co.uk/broadband/

jameshurrell · May 28, 2012, 13:06:27

Quote from: Steve on May 28, 2012, 06:30:18
No idea , my guess is BT faults or work possibly, if there was an IDNet issue I think we'd see more forum complaints over this period.

I agree, especially in the early hours of the morning like in OP's log.

Desaan · May 28, 2012, 15:48:04

It was like that from Friday till today, when everything now appears normal.

I guess what pisses me off the most is it was like that for 3 days with not even a hint as to what was happening. Nobody from Idnet knows of any work being done and there are no service announcements about any work being done in my area by BT, the right hand has no idea what the left is doing

It appears my line reconnected @5.08 am this morning and actually stayed connected, which is just as well considering I use the connection for work and everything else. So damn technology dependent! Just don't let Snake Plisskin push that button.

pctech · May 28, 2012, 18:38:42

Bear in mind IDNet are as much a customer of BT as you are of IDNet, BT does not have to tell them anything if it does not wish to, the same goes for any BT ADSL based ISP in the UK.

Niall · May 28, 2012, 23:23:18

My connection went really bad a while ago. To this day I don't know what happened, other than the cabinet had something replaced, something in the exchange was replaced and a part of my line was replaced. I still lost over 6mb in speed when they 'fixed' it. The trouble with BT is that they have nothing but complete contempt for it's customers and refuse point blank to update ISPs with a list of accurate work being done. Seriously, how hard can it be to input information into a computer to say what and where you're working, so the ISP can see it and update a page for their customers. Why a monitoring body hasn't flogged them for this I don't know. The stress it causes people and money spent trying to problem solve (I was forced to spend over £300 replacing stuff that didn't need replacing, and can I get that money back? Of course not, as no one gives a cr*p) is just ridiculous. Any other company that tried to pull this would go out of business, but does BT? Nope, they get money put in from the government

mervl · May 29, 2012, 09:23:54

I'm no BT lover (never ask about the over 2 years whilst BT "worked" on my part time phone line - in suburbia, not some remote island or hilltop, though that might have been better!). But I still think their achievement with the complexity of broadband over the old telephone system is not far short of miraculous, and not least at the prices we pay. Yes, of course, anyone could devise a better system, but I defy anyone to find someone wiling to pay for it.

The engineering staff I have come across have almost without exception been excellent, dedicated and within their resources willing to go as far as they can. I frankly, in the real world, don't know how much more you can ask. Of course it's hugely frustrating when it goes wrong and you can't find out why, and we're right to vent our anger (if it makes us feel better at least) and BT would die if they didn't improve, but things take time, cost money, and we're driving the system at and beyond its limit. Of course on any road you should never have to stop or slow down, be held up or find yourself in a queue, or heaven forbid even worse find yourself subject to a speed limit, so find that road! Sorry, if being with an inadequate or no connection for a few days is a life and death matter for you, than I'd have to suggest the main problem is not the BT public phone network.

pctech · May 29, 2012, 19:26:32

I agree about the engineers (apart from the herbert that put the second line in back in 2004 who was a bodge it and hop it merchant) but the other two guys have been superb.

I think the problem is those further up that you don't see.

Rik · May 30, 2012, 09:10:02

Who believe in the mantra, "Do nothing".

mervl · May 31, 2012, 14:39:30

The hated accountants, you mean? Trouble is, name one successful company that runs without 'em.

Rik · May 31, 2012, 17:17:13

The Post Office. When it was part of the Civil Service and there was barely an accountant to be seen, they managed two (three in some parts of London) deliveries a day, 99%+ of mail was delivered next day and staff and customers were happy.