50M : Installed Finally But...

[Ignitionnet]

Sadly that won't show anything Tazz, the problem is between me and the CMTS, that report only shows between his server and the CMTS.

[Tazz]

Originally Posted by Ignitionnet

Sadly that won't show anything Tazz, the problem is between me and the CMTS, that report only shows between his server and the CMTS.

Oh so not much cop then... TBB graphs to stick to it is then...

[pip08456]

As I posted when that link appeared on here.

Originally Posted by pip08456

Most ppl use the TBB Quality monitor which goes further than your CMTS as it pings your router.

[Skie]

Get onto your contacts and get a VMNG300. Its the only way to be sure.

The inability for the Superhub to handle LAN traffic and its poor wireless is unforgivable. VM have not acknowledged any of these issues so I doubt any sort of fix is due. They seem to be relying on modem mode to make the complaints about them stop, but not everyone will want to pony up for a router just to avoid the pile of pants that is the 'Super'hub. If they are offering a combined product, it should actually work. Mine was a regular reboot needer and wireless dropout, but luckily I had a VMNG300 lying around.

[Chrysalis]

Originally Posted by Ignitionnet

Oh while I'm at it the Superhub is a disaster. After falling over yesterday and requiring a reboot it has locked up twice so far today, disconnecting me from VPN / VoIP. The first time it required a power cycle, the second it sorted itself out after a couple of minutes of being unresponsive.

So, yes, an install delayed by a month and when it finally does happen the VoD doesn't work properly, the broadband is congested and is being delivered by unstable CPE that is on current rates becoming unresponsive once every 3 hours.

It's going to be quite funny when the people at VM who were helping me call to see how everything is going.

Still think its good enough because you not in the dumbed down mass user customer base?

[Ignitionnet]

Originally Posted by Chrysalis

Still think its good enough because you not in the dumbed down mass user customer base?

I'm beginning to understand more and more why even your own MP ignores you.

My experience is clearly exceptionally bad due to the reloads. Other people are obviously having better experiences. I never actually said that that thing was fine, merely its concept, I have always criticised the execution.

I fully expect that I am exacerbating the issues due to the amount of devices I have connected. I'm going to try a little workaround on this shortly.

[Chrysalis]

ignition it was a serious question I wasnt been sarcastic. Obviously for yourself the superhub is a shambles but my question was do you still think its a fair product for the customer base as a whole like you said before you had tried it.

I can assure you if I write to my MP its very different to how I am on internet forums.

Prior to going live you had posted at least a few times to unhappy customers they should accept the service for what it is due to its low cost (or leave) and that VM are right to concentrate on just keeping the lowest denominator happy, this is why I made that comment and an earlier one before it.

I agree with the point you made here that at the very least it should run faster than the lower speed tier below it. But you already know that so I apologise if my question offended you.

[Ignitionnet]

No worries but I stand by all the rest. Doesn't change that 13Mbit out of 50Mbit isn't acceptable to any denominator.

[Chrysalis]

you posted on VM forums? to see if raised as high utilisation.

[Ignitionnet]

Yes I have.

Pubs are closing up, post-rugby boozing session is done.

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=8ms TTL=251
Reply from 194.168.4.100: bytes=32 time=52ms TTL=251
Reply from 194.168.4.100: bytes=32 time=223ms TTL=251
Reply from 194.168.4.100: bytes=32 time=55ms TTL=251
Reply from 194.168.4.100: bytes=32 time=122ms TTL=251
Reply from 194.168.4.100: bytes=32 time=30ms TTL=251
Reply from 194.168.4.100: bytes=32 time=10ms TTL=251
Reply from 194.168.4.100: bytes=32 time=114ms TTL=251

http://www.speedtest.bbmax.co.uk/res...942&v=12765306

Download Speed: 10265 kbps (1283.1 KB/sec ) Upload Speed: 1168 kbps (146 KB/sec )

[Chrysalis]

downloading alpha windows 8 of a torrent and here is mine whilst doing that.

Reply from 194.168.4.100: bytes=32 time=5ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=8ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252

[Ignitionnet]

Rebooted Superhub twice so far this morning. Looks like it could be an hourly event!

---------- Post added at 10:03 ---------- Previous post was at 08:58 ----------

Indeed it is!

[horseman]

Originally Posted by Ignitionnet

Rebooted Superhub twice so far this morning. Looks like it could be an hourly event!

---------- Post added at 10:03 ---------- Previous post was at 08:58 ----------

Indeed it is!

Doesn't correlate with your SK kit's monitor by any chance? or did you leave that disco'd?

[Ignitionnet]

Originally Posted by horseman

Doesn't correlate with your SK kit's monitor by any chance? or did you leave that disco'd?

It is connected to the device though I can't receive the reports at this time.

Sadly no, not correlated, it's not precisely hourly and it was fine overnight, while unused, even though the SK kit would have been doing its thing throughout.

I am placing it under rather limited load, as I can't max out the full 50Mbps, which it seems to take exception to.

Anyway I'm going to stop reporting the reloads as I think it can be taken as read that the network is dodgy and the CPE is banal.

[horseman]

Originally Posted by Ignitionnet

It is connected to the device though I can't receive the reports at this time.

Then give it a year to settle in - then disconnect the SK kit and see if it makes any difference?