R38 ain't so good
 

Whilst on R37 we had zero issues with our connection everything worked 100%
Now after the router's firmware was upgraded to R38 we have had nothing but dropped packets, huge latency and wireless products having their connection dropped every half hour or so while the wired connection remains active.

Pretty miffed that this is happening.

Re: R38 ain't so good
 

Hey alferret,

Have you posted on our forums about this?

Thanks

Re: R38 ain't so good
 

Yes, posted about the same time.

http://community.virginmedia.com/t5/...e/td-p/1875664

See attached from 03/06/13 11/06/13 13/06/13

Re: R38 ain't so good
 

you should feed it back internally dude because VM made a big hoo ha over r37 saying what a massive improvement it made to wireless so if they have now released another version of firmware which screws it all up again then they need to know.

Tbh if they are going to be that careless and muck (f) everything up again then they should just knock shub1 on the head and give everyone a shub 2. It is a sad state of affairs when you are still working on fixing problems when the next gen router has come out more than 2 years later. Time to cut your losses me thinks.

Re: R38 ain't so good
 

Posted on vm's forums and no reply from staff. Ho hum!

Re: R38 ain't so good
 

We were sleeping. ;)

I've asked one of the forum team to look into it and see if there are any possible causes external to the Super Hub. Can you confirm if the issues occur in Modem Mode?

Re: R38 ain't so good
 

Thanks for popping back Kieran.
I'll drop it into modem mode later on, probably overnight.

Re: R38 ain't so good
 

Been trying to post info on VM's "help" forum & I cant get owt to work.

Here are my upstream/downstream values for those that may be interested and could help/offer advice.

Cheers

Here is today's TBB graph
http://www.thinkbroadband.com/ping/s...14-06-2013.png

Re: R38 ain't so good
 

power levels are pretty much perfect dude which makes your graph all the more a mystery.

Re: R38 ain't so good
 

I guessed levels were ok as they are pretty much the same as before R38 and as you say the graph is a mystery. I know VM will come back and say "oh we cant see an issue its all in your mind" type of thing, yet there clearly is an issue.

Re: R38 ain't so good
 

yeah definitely, I would have thought something like that has got to a network fault which will be affecting your area so if they nothing is wrong then they are lieing out of their collective asses. If nothing else they'll be able to run a battery of tests and see the packet loss.

Re: R38 ain't so good
 

I haven't seen dropped packets (at least not "lots of" in the TBBs.

Re: R38 ain't so good
 

I have seen something similar on SH1 in modem mode but it didn't affect throughput. When I rebooted the hub the graph went back to normal.

P.S This was on R37

Re: R38 ain't so good
 

I have rebooted a couple of times but left it switched off for less than a minute.
Rebooted a little while ago after seeing your post but left it off for 10 minutes while I got on with some stuff. The upshot of doing that, is this
http://www.thinkbroadband.com/ping/s...15-06-2013.png

As you can see its possible normal service has resumed, not counting chickens just yet but maybe leaving it off for longer did have a possible and positive effect.

Re: R38 ain't so good
 

What you are showing is a well documented behaviour of the SH1. You could keyword search on CRAWLEY and see the saga reported by thenry. Ravenstar has effectively documented a whole saga (monitored under controlled conditions) on the VM forum.

A reboot of the SH1 clears the SH's chest so to speak and it stops wheezing. The same people have not reported the same phenomenon on the SH2 and thenry has confirmed this.

I've always said that the SH1 is beyond redemption.