A 2Wire 2700 HGV BT Business Hub Router Wireless

[David]

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\David> ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 39ms, Average = 38ms

C:\Users\David>

  Not to worry as I dont game but slightly high ?

[Rik]

We all have our cross to bear and you drew the short straw  

It's OK, I use a wide glass.

[Rik]

    Minimum = 37ms, Maximum = 39ms, Average = 38ms

  Not to worry as I dont game but slightly high ?

ISTR your pings were in that region normally, David? It could be you have a congested VP.

[David]

ttp://books.google.co.uk/books?id=ggTv2kLpQFEC&pg=PA283&lpg=PA283&dq=congested+path&source=bl&ots=E8kOrweC36&sig

Im trying to gigest this.....

I have had pings as low as 22 in the past,this possibly due to the hub ?its just a talking point really.I learn from them you see

[Rik]

The route between you and IDNet is called a virtual path because it's not a physical, hard-wired, connection, but can follow a number of routes depending on what is happening at the time you connect. If you hit a congested path, your pings increase. I saw it last week when, following a re-boot, pings went out to 30ms. A reset of the PPP session (always worth trying when running a 2700, as it doesn't affect sync), saw a shift to a different VP and pings returned to 21ms.

[David]

  Givee it a go later 

[LesD]

Well I can't remember where but made mention of it somewhere on the forum before and now it look like it's right. 

My 2Wire 2700HGV single SSID router with the BT firmware 5.29.107.19 took another reboot in the wee small hours of yesterday morning at just about or maybe slightly over the 300 hours mark. I shall give it another 12 days and if it does it again I will get the spare out of the cupboard and see how that one fairs (or is it fares?) I never know.

I have had much longer than this on previous occasions and the only thing I have any recollection of changing was unticking
Excessive Session Detection under the Advanced Firewall Settings after reading that this was a good thing to do somewhere. Maybe it wasn't so I have put the tick back to see whether I can pass the dreaded 12 day mark like this. Straws and clutching I guess! 

[Rik]

Generally, it's been understood to be the SBC firmware that caused this. Perhaps it was a hardware issue after all?

[LesD]

Last evening just about or just before I booted up my PC my 2700 took a reboot all of its own accord and this was in-line with the "12 day (300 hours)" reboot phenomenon and remember my router is using the BT firmware version 5.29.107.19! 

I took the following copies from the System Summary, Configuration section on Sunday evening just before the 12 days was up and then again last evening just over half an hour after the unscheduled reboot took place.

System Time: Sunday, March 29, 2009
09:40:06 PM
GMT Daylight Time
Time Since Last Boot: 11  days  10: 35: 19


System Time: Monday, March 30, 2009
10:18:45 PM
GMT Daylight Time
Time Since Last Boot: 0  days  00: 35: 31

Needless to say at that time of the evening my connection rate (sync speed) took a hit. 

Sadly this has become a noticeably repeatable occurrence over 12 day periods for some time now.

So maybe you are right Rik and it is a hardware issue and in my case possibly due to some change/deterioration because I used to stay up for a month or more at a time when I first got this router. When I get a chance I will see if using my spare makes any difference. Of my two eBay acquisition the spare was described as the used one. The one currently in use was supposedly new and unused when I got it.  Since the spare has been used already it may be subject to the 12 reboot issue, who knows! 

[Steve]

Possibly time for a newer twin ssid version?

[LesD]

Possibly time for a newer twin ssid version?

Yes Steve, the thought had crossed my mind but the V6 issue is a bit daunting.

[Rik]

What I took to doing, with my single SSID, SBC, version, Les, was to shut the router down every 12 days in the evening, re-booting the following morning. That meant the speed didn't take a hit.

[LesD]

What I took to doing, with my single SSID, SBC, version, Les, was to shut the router down every 12 days in the evening, re-booting the following morning. That meant the speed didn't take a hit.

Yes I remember you saying that this is what you did and in the short term I shall most probably start doing the same thing.
Till now I have been letting it happen to make sure that is was the "12 day" reboot that had crept up on me and not something else being as how I am using BT firmware. I am now convinced that this is what it is.

[Rik]

Which implies it was hardware all along and not, as we believed, firmware.