Can anyone tell me what this means?
Hi SteveArnold,
How is your kit set up? Are you using any extension cables/sockets at all? The drops seem to mainly be happening in the evening. I'm wondering if there's something that could be interfering at home, heating, Christmas lights etc?
Jojo
How is your kit set up? Are you using any extension cables/sockets at all? The drops seem to mainly be happening in the evening. I'm wondering if there's something that could be interfering at home, heating, Christmas lights etc?
Jojo
How about trying it in the test socket. This will rule out interference with the hard wired extension.
Hi Jojo,
I'll give it a go probably tomorrow as my nephew is here playing on the main pc over the internet. I've been relegated to the laptop I'll leave routerstats running and see what happens.
Just a thought there is one thing that has altered on my network, I've added a Synology DS212J NAS via a 0.5m cable to the gigabit switch upstairs but that shouldn't affect the WAN connection though as far as I know. By the way switch to router is via around 15m of cat6 cable.
I'll update again once I've tried the test socket.
Thanks again
Steve
I'll give it a go probably tomorrow as my nephew is here playing on the main pc over the internet. I've been relegated to the laptop
I'll leave routerstats running and see what happens.Just a thought there is one thing that has altered on my network, I've added a Synology DS212J NAS via a 0.5m cable to the gigabit switch upstairs but that shouldn't affect the WAN connection though as far as I know. By the way switch to router is via around 15m of cat6 cable.
I'll update again once I've tried the test socket.
Thanks again
Steve
If you're not that worried about having the small increase in speed that 21CN has given you then why not try forcing your router to connect at G.DMT (ITU G.992.1) i.e. establish an ADSL Max stylee connection instead ? This would mean, in principle, that your connection should perform exactly as it always used to do prior to the upgrade to 21CN However, are you 100% sure that you're not still in the 10/14 day (or whatever it is) 'training period' that started when you were moved over to 21CN ? If so then you probably need to wait for that to complete before trying anything much or in fact considering the current router behaviour to be a problem for that matter. Several disconnects as well as seeing occasional silly stats is pretty much the expected thing during the initial training period I think.
I'm interested in your problem because I have had a similar problem with random and intermittent but pretty regular PPP drops (although in my case with absolutely NO change whatsoever in line synch, SNR or IP profile etc) ever since I was forcibly upgraded without warning to 21CN. It started literally within minutes of the so-called upgrade but had very rarely (if ever) been seen in the previous ~10 years ! After arguing the toss and going round and round in ever decreasing circles with Support for almost 9 months I've just about given up because it seems quite clear to me that they do not understand how things work (in particular LCP control packets and the difference between a PPP connection and the fundamental connection with the exchange equipment etc.) and are unable or unwilling to provide sensible and valid answers to questions or provide any relevant comments. All I get is pretty much an insistence that the customer's equipment is the cause of the apparent problem without any evidence or rationale whatsoever to support drawing such a wild conclusion from the stack of evidence to the contrary being provided. There are a few other BT/PN network issues as well (such as some very obvious and logged data routing errors and totally dead gateways) to consider but my conclusion at the mo is that it's primarily a bug and/or a network loading issue. Needless to say, the problem generally becomes MUCH worse when there are lots of speed or response time complaints from other customers, reports of network balance problems, announced maintenance periods or perhaps rather more telling, immediately prior to a BW increase
I strongly suspect that under high network load conditions, routine LCP monitoring packets are simply being intentionally dropped/ignored for extended periods of time as and when required in addition to there being a significant increase in routing and other errors.
I would therefore be *VERY* interested to hear what happens if you do try connecting at G.DMT on 21CN although as you're apparently getting a very variable SNR then I would suspect that unlike me you do have a genuine interference problem or some other real issue somewhere. Connecting at good old G.DMT will however mean that the upper ADSL2 frequency bands will not be used so it might solve your problem PROVIDING that the problem is in fact solely down to some issue or other when using the extended ADSL2 frequencies of course. If it doesn't solve the problem then that would suggest that you may also have similar issues to me with random and intermittent PPP drops for no obvious or particularly good reason that were not in any way apparent prior to the upgrade to 21CN.
Just in case it helps, the sort of thing I'm seeing from looking at my router LCP packet logs is below:
The above quite clearly shows that the BT/PN network stopped sending or responding to routine LCP packets completely for no particularly good or obvious reason and therefore the router quite rightly concluded that there was a network fault and terminated the PPP connection. However, it is also quite clear that there was no fundamental transmission problem on the line because the PPP Termination Request was in fact received and responded to correctly even though various other routine LCP packets were being completely ignored and data flow in general had ceased
If you are able to log similar data from your router then it may perhaps help to identify what exactly is going on with your connection.
However, are you 100% sure that you're not still in the 10/14 day (or whatever it is) 'training period' that started when you were moved over to 21CN ? If so then you probably need to wait for that to complete before trying anything much or in fact considering the current router behaviour to be a problem for that matter. Several disconnects as well as seeing occasional silly stats is pretty much the expected thing during the initial training period I think.I'm interested in your problem because I have had a similar problem with random and intermittent but pretty regular PPP drops (although in my case with absolutely NO change whatsoever in line synch, SNR or IP profile etc) ever since I was forcibly upgraded without warning to 21CN. It started literally within minutes of the so-called upgrade but had very rarely (if ever) been seen in the previous ~10 years ! After arguing the toss and going round and round in ever decreasing circles with Support for almost 9 months I've just about given up because it seems quite clear to me that they do not understand how things work (in particular LCP control packets and the difference between a PPP connection and the fundamental connection with the exchange equipment etc.) and are unable or unwilling to provide sensible and valid answers to questions or provide any relevant comments. All I get is pretty much an insistence that the customer's equipment is the cause of the apparent problem without any evidence or rationale whatsoever to support drawing such a wild conclusion from the stack of evidence to the contrary being provided. There are a few other BT/PN network issues as well (such as some very obvious and logged data routing errors and totally dead gateways) to consider but my conclusion at the mo is that it's primarily a bug and/or a network loading issue. Needless to say, the problem generally becomes MUCH worse when there are lots of speed or response time complaints from other customers, reports of network balance problems, announced maintenance periods or perhaps rather more telling, immediately prior to a BW increase
I strongly suspect that under high network load conditions, routine LCP monitoring packets are simply being intentionally dropped/ignored for extended periods of time as and when required in addition to there being a significant increase in routing and other errors.I would therefore be *VERY* interested to hear what happens if you do try connecting at G.DMT on 21CN although as you're apparently getting a very variable SNR then I would suspect that unlike me you do have a genuine interference problem or some other real issue somewhere. Connecting at good old G.DMT will however mean that the upper ADSL2 frequency bands will not be used so it might solve your problem PROVIDING that the problem is in fact solely down to some issue or other when using the extended ADSL2 frequencies of course. If it doesn't solve the problem then that would suggest that you may also have similar issues to me with random and intermittent PPP drops for no obvious or particularly good reason that were not in any way apparent prior to the upgrade to 21CN.
Just in case it helps, the sort of thing I'm seeing from looking at my router LCP packet logs is below:
[everything working normally for some considerable period of time]
Dec 17 04:05:59 PoE <== Protocol:LCP(c021) EchoReq Identifier:0xB8Magic Number: 0x68d8 5d e6 ##
Dec 17 04:05:59 PoE ==> Protocol:LCP(c021) EchoRep Identifier:0xB8Magic Number: 0x0 00 00 ##
Dec 17 04:07:59 PoE <== Protocol:LCP(c021) EchoReq Identifier:0xB9Magic Number: 0x68d8 5d e6 ##
Dec 17 04:07:59 PoE ==> Protocol:LCP(c021) EchoRep Identifier:0xB9Magic Number: 0x0 00 00 ##
Dec 17 04:09:59 PoE <== Protocol:LCP(c021) EchoReq Identifier:0xBAMagic Number: 0x68d8 5d e6 ##
Dec 17 04:09:59 PoE ==> Protocol:LCP(c021) EchoRep Identifier:0xBAMagic Number: 0x0 00 00 ##
Dec 17 04:11:59 PoE <== Protocol:LCP(c021) EchoReq Identifier:0xBBMagic Number: 0x68d8 5d e6 ##
Dec 17 04:11:59 PoE ==> Protocol:LCP(c021) EchoRep Identifier:0xBBMagic Number: 0x0 00 00 ##
Dec 17 04:13:59 PoE <== Protocol:LCP(c021) EchoReq Identifier:0xBCMagic Number: 0x68d8 5d e6 ##
Dec 17 04:13:59 PoE ==> Protocol:LCP(c021) EchoRep Identifier:0xBCMagic Number: 0x0 00 00 ##
[fault occurs here - expected Echo Req IN is missing and subsequent Echo Req OUTs are ignored]
Dec 17 04:16:03 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x02Magic Number: 0x0 00 00 ##
Dec 17 04:16:06 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x03Magic Number: 0x0 00 00 ##
Dec 17 04:16:09 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x04Magic Number: 0x0 00 00 ##
Dec 17 04:16:12 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x05Magic Number: 0x0 00 00 ##
Dec 17 04:16:15 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x06Magic Number: 0x0 00 00 ##
Dec 17 04:16:18 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x07Magic Number: 0x0 00 00 ##
Dec 17 04:16:21 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x08Magic Number: 0x0 00 00 ##
Dec 17 04:16:24 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x09Magic Number: 0x0 00 00 ##
Dec 17 04:16:27 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0AMagic Number: 0x0 00 00 ##
Dec 17 04:16:30 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0BMagic Number: 0x0 00 00 ##
Dec 17 04:16:33 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0CMagic Number: 0x0 00 00 ##
Dec 17 04:16:36 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0DMagic Number: 0x0 00 00 ##
Dec 17 04:16:39 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0EMagic Number: 0x0 00 00 ##
Dec 17 04:16:42 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x0FMagic Number: 0x0 00 00 ##
Dec 17 04:16:45 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x10Magic Number: 0x0 00 00 ##
Dec 17 04:16:48 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x11Magic Number: 0x0 00 00 ##
Dec 17 04:16:51 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x12Magic Number: 0x0 00 00 ##
Dec 17 04:16:54 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x13Magic Number: 0x0 00 00 ##
Dec 17 04:16:57 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x14Magic Number: 0x0 00 00 ##
Dec 17 04:17:00 PoE ==> Protocol:LCP(c021) EchoReq Identifier:0x15Magic Number: 0x0 00 00 ##
Dec 17 04:17:03 PoE ==> Protocol:LCP(c021) TermReq Identifier:0x16 ##
Dec 17 04:17:03 PoE <== Protocol:LCP(c021) TermAck Identifier:0x16 ##
[new PPP connection established]
NOTES: The above is only a small edited sample of typical relevant data from the router logs
At no time was there any loss or change in line synch or SNR etc.
<== means INCOMING data packets from BT/PN
==> means OUTGOING data packets to BT/PN
The above quite clearly shows that the BT/PN network stopped sending or responding to routine LCP packets completely for no particularly good or obvious reason and therefore the router quite rightly concluded that there was a network fault and terminated the PPP connection. However, it is also quite clear that there was no fundamental transmission problem on the line because the PPP Termination Request was in fact received and responded to correctly even though various other routine LCP packets were being completely ignored and data flow in general had ceased
If you are able to log similar data from your router then it may perhaps help to identify what exactly is going on with your connection.
