BT 2700 HGV Router problems

10forcash — Fri, 28 Nov 2014 19:18:05 GMT

For some time (months, not weeks or days) we have been experiencing high latency, loss of connection, dropped packets and router resets - even on two occasions, reset to factory condition...

We have:-

Replaced the router (same type)

Replaced the PSU

Replaced all cables

Replaced the filter

Had an engineer call, line tested and new faceplate with filter fitted in the absence of any other cause found (REIN test was OK)

When the problems occur, the phone line (no extensions!) is clear, and we have done random 'quiet line tests' with no noise found

I have recently talked to someone in BB Faults, whou was very helpful - well, as much as he could be, it was mentioned that they could see ten reconnects in one day!

For some time, we have been using the 'content screening' function, this 'dials home' to check the web page address before allowing or denying access, there have been a few instances logged where the router has lost contact with the server - it's not known if that is the cause or effect though.

We have also experienced the router completely 'freezing' the LAN activity LED is active, no BB activity and no access to the router web pages from the LAN.

One big concern I have from the router logs is the apparent attempt to contact IP addresses without any requests from the LAN (we're running Wireshark on a switch configured to reflect all traffic on the LAN to that machine and the wireless / BT Openzone is disabled).

Here's the latest sample from the system log

To save anyone the effort, the IP's are:-

Mondrian Holdings, LLC - Los Angeles - a hotel chain

KDDI CORPORATION - Japan ISP as far as I can see

SETITAGILA-NET - Russian ISP

I'm hoping this isn't due to a *NIX vulnerability in the router (have these been patched for the bash script problem?) current reported versions are:-

Hardware Version: 2701-100589-005
Firmware Version:
6.3.9.63-plus.tm

iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 46.165.4.194[500]
sntpc: Server ntp3.2wire.com did not respond
ip: bad window size in constructed ack: -2885, session 43616
csd: packet (4022860823) reached maximum retries - aborting packet
csd: packet (4022860824) reached maximum retries - aborting packet
csd: packet (4022860825) reached maximum retries - aborting packet
csd: packet (4022860826) reached maximum retries - aborting packet
csd: packet (4022860827) reached maximum retries - aborting packet
csd: packet (4022860828) reached maximum retries - aborting packet
csd: packet (4022860829) reached maximum retries - aborting packet
csd: packet (4022860830) reached maximum retries - aborting packet
csd: packet (4022860831) reached maximum retries - aborting packet
csd: packet (4022860832) reached maximum retries - aborting packet
csd: packet (4022860833) reached maximum retries - aborting packet
csd: packet (4022860834) reached maximum retries - aborting packet
krtlock: thread gen (tid 5) slow rd held 'thread'@0x41a1f2c0 for 16.13s
krtlock: slck: gen (tid 5):
krtlock: [5/KERN] - 0: 0x407df2d4
krtlock: [5/KERN] - 1: 0x4002740c
krtlock: [5/KERN] - 2: 0x400294c1
krtlock: [5/KERN] - 3: 0x4012599e
krtlock: [5/KERN] - 4: 0x400296d8
krtlock: [5/KERN] - 5: 0x4025d2a2
krtlock: [5/KERN] - 6: 0x40156a98
ip: bad window size in constructed ack: -39342, session 80910
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 119.106.86.48[500].
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500]
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])
iked: [PROTO_ERR]: ikev1.c:545:<unknown>(): Invalid exchange type 243 from 38.106.49.206[500].
iked: [PROTO_ERR]: ikev1.c:1031:<unknown>(): couldn't find configuration for remote 38.106.49.206[500] (local 217.43.97.56[500])

Any clues, pointers or ideas are most welcome!

Re: BT 2700 HGV Router problems

10forcash — Tue, 16 Dec 2014 12:34:58 GMT

Well after further investigation by both BT and myself, we decided the best course of action was to replace with a non-BT router, so after spending £15 on fleabay, I now have a Cisco 857 in place of the 2700HGV - problem solved, lower latency too!

topic Re: BT 2700 HGV Router problems in Archive

BT 2700 HGV Router problems

Re: BT 2700 HGV Router problems