In reply to a post by MrSaffron:

And while it is annoying I do not think people should expect leased line uptimes unless willing to pay for it.

I wouldn't call a few months of continual uptime leased line like standards, as i have in the past had such and would of been longer but i rebooted the router, if you don't have a line problem then there's no reason why you would loose sync under normal circumstances unless the router was unable to handle it
currently my uptime is at 23 days, would of been a lot longer if i hadn't been trying out different methods of improving my sync,

Edited by tommy45 (Mon 14-Mar-11 17:16:54)

In reply to a post by Anonymous:

In reply to a post by RobertoS:

This is not a disconnection, and will show as a red down-line on the graph. It is the router too busy doing real work to respond to the stats request.

Real disconnections maintain the normal colour and have a flat line at zero for the time taken to re-sync.

Ironically there was a 3 page argument with the OP on the Be forums, where he/she doesn't believe that... Hope it doesn't happen again.

Seems this Anon is not the OP . However, for both of you, I am not and have never been on Be, and have no knowledge of the OP's problem apart from this thread. But I do have a huge experience of RouterStats over several years.

Re the problem itself, my feeling is as expressed by a few others. The jumpering to the Be line card, or the line card itself. Strange that the symptoms are not worse though. To me that would indicate the card rather than the jumpering.

(Edit - typo.)

Edited by RobertoS (Mon 14-Mar-11 22:01:56)

In reply to a post by RobertoS:

In reply to a post by Anonymous:

In reply to a post by RobertoS:

This is not a disconnection, and will show as a red down-line on the graph. It is the router too busy doing real work to respond to the stats request.

Real disconnections maintain the normal colour and have a flat line at zero for the time taken to re-sync.

Ironically there was a 3 page argument with the OP on the Be forums, where he/she doesn't believe that... Hope it doesn't happen again.

Seems this Anon is not the OP . However, for both of you, I am not and have never been on Be, and have no lnowledge of the OP's problem apart from this thread. But I do have a huge experience of RouterStats over several years.

Re the problem itself, my feeling is as expressed by a few others. The jumpering to the Be line card, or the line card itself. Strange that the symptoms are not worse though. To me that would indicate the card rather than the jumpering.

who said the OP was Anon??????????????? who said you where on BE???

In reply to a post by Anonymous:

who said the OP was Anon???????????????

The nick of the opening post?

who said you where on BE???

No-one. I just wished to establish the fact so I couldn't be accused of bias or pre-formed opinions on the matter.

Who the heck are you, you pip-squeak scaredy-baby anonymous big-mouth!?

The relevance of your flame of me to the OP's problem is what, exactly?

Edited by RobertoS (Mon 14-Mar-11 22:03:48)

In reply to a post by RobertoS:

In reply to a post by Anonymous:

who said the OP was Anon???????????????

The nick of the opening post?

who said you where on BE???

No-one. I just wished to establish the fact so I couldn't be accused of bias or pre-formed opinions on the matter.

Who the heck are you, you pip-squeak scaredy-baby anonymous big-mouth!?

The relevance of your flame of me to the OP's problem is what, exactly?

what [censored] are you posting

what [censored] are you posting

[chuckle]

Edited by RobertoS (Mon 14-Mar-11 22:19:55)

In reply to a post by nredwood:

I recommend Pastebin
http://pastebin.com/

Thanks for that nredwood, that could be useful for alot of things actually

Having to start over had a power cut here this evening which lasted a few hours so all onboard router stats are gone.

Routerstats lite prior to the power cut looking at stats to that point it doesnt look like there were any disconnects though. (would had been something like 52 hours total uptime, ironic a power cut halted the uptime on this occasion).

Also although im using the Bebox i stand by what i said regarding other routers.

It does not make a difference on my connection, ive tried various models over the prior months and it all suffers the same. Have also reported to BE using more than one model of router (their Bebox included in prior months).

Also again i have to correct 'you know who' there are plenty of others using Netgears on BE and the TP-link which was recommended by some on BE forums which have no issues.

My netgear 834GT and the TP-Link perform just as well as the Bebox, infact better in many regards. My 834GT served me well on UKonline and the TP-Link is actually better (and worse) in some areas than that model.

Id also say there are more than a few that have stated that TP-Link performs better on BEs forums than the BEbox a couple which have stated it holds onto sync better and to a lower SNR level........

HOWEVER all that said that doesnt mean im not listening to sensible people such as yourself here.

To satisfy any doubt ill use the Bebox for the routerstats lite collecting here and await the disconnect.

Oh and incase there was any doubt....
Im the original anon poster and from the cheeky username it should be obvious from now on

In reply to a post by nonBEliever:

Having to start over had a power cut here this evening which lasted a few hours so all onboard router stats are gone.

Routerstats lite prior to the power cut looking at stats to that point it doesnt look like there were any disconnects though. (would had been something like 52 hours total uptime, ironic a power cut halted the uptime on this occasion).

Oh, that's a pity, I was looking forward to those

Qiite a good username in fact . Though I do hope you believe me about the occasional RS down-spikes, and I do really think you should set the sampling period to 5 seconds if you haven't already done so.

Better luck with the next lot of diagnostics.

In reply to a post by RobertoS:

Qiite a good username in fact .

Actually, PRODISC would have been a better choice to maintain continuity