Superhub Technical question! - Page 2

pip08456 · 16-05-2011, 14:32

Quote:

Originally Posted by zekeisaszekedoes

Most wireless problems are caused by the 300Mbps mode on the super hub (I'm going to stop title casing it from now on), which is unstable and can cause lockups requiring a reboot, especially when wirelessly transferring large files.

Put it on 145Mbps mode and it'll work more reliably, however if you have a 100Mb broadband service this now means any wireless devices won't be able to make the most of it, which is odd because of course part of the reason it exists is so all devices can make use of the flagship 100Mb tier whether they are wired or wireless.

You forgot to add it's future proof for higher tiers!

zekeisaszekedoes · 16-05-2011, 21:03

Yeah, well, the way things are going it'll be a 100Mbps only device before being replaced by some other equally inadequate combi modem/router that'll be ill-equipped to handle 200Mbps WAN side.

craigj2k12 · 16-05-2011, 21:07

Quote:

Originally Posted by zekeisaszekedoes

Yeah, well, the way things are going it'll be a 100Mbps only device before being replaced by some other equally inadequate combi modem/router that'll be ill-equipped to handle 200Mbps WAN side.

never mind lan side

zekeisaszekedoes · 16-05-2011, 21:29

Yep, very easy to kill it on the LAN side. A router that cannot route, it's amusing.

craigj2k12 · 16-05-2011, 21:30

Quote:

Originally Posted by zekeisaszekedoes

Yep, very easy to kill it on the LAN side. A router that cannot route, it's amusing.

thats netgear for you. im using a gigabit switch made by netgear, its unmanaged, so there is no interface for netgear to screw up, but it does do some dodgy stuff from time to time

Skie · 16-05-2011, 21:50

My superhubs wireless wouldnt allow connections when in 145 mode and required a restart daily while in 300 mode.

Superb bit of kit!

craigj2k12 · 16-05-2011, 21:52

Quote:

Originally Posted by Skie

My superhubs wireless wouldnt allow connections when in 145 mode and required a restart daily while in 300 mode.

Superb bit of kit!

its amazing, and im sure the fun will start again with the next firmware update

scott.deagan · 17-05-2011, 21:19

I'm not confident that adding a "Bridge Mode" to R27 is going to solve all the problems. I was on the 20Mb service (separate modem/router) since it was released in my area and not ONCE did I have to call Virgin Media.

The reason why I do no believe adding a Bridge Mode will be the magic pill is because I'm using my "Super" Hub as a modem only (I've turned off wireless functionality, placed a WNR2000v2 in the DMZ and connected it via a cable). I am still experiencing issues, such as video and audio streams freezing (and not starting again once they stop), SSH connections being disconnected, PPTP connections freezing and then dropping (etc, etc, etc).

The problems are intermittent, but they happen (too) frequently and on Linux, Windows, and OSX. I also experience the same reliability issues if using wired or wireless connections. Setting the WiFi mode to 54Mb, 145Mb, or 300Mb does not help.

I wish I had never been suckered in to the so called "free" 30Mb upgrade (I was seduced by the promise of a 3Mb upstream). I should have checked the forums first. I did ask to downgrade back to the 20Mb service within 14 days, but Virgin were not going to give me back the old DOCSIS 2 modem - I would still be stuck with the "super" hub.

I don't know if I can wait any longer for the R27 release, and I'm not confident that R27 is going to fix anything at all (judging by Virgin's responses in the forums, if they believe it's just a WiFi issue then they're not going to fix the real problem(s)). A very simple solution would be to allow customers to using their own DOCSIS 3 modems.

Anyway, for me, personally, every time the "glitch" manifests it feels like a hot knife being thrust into the heart of my digital persona. My contract is up, and now there's a new fibre provider in town

.

pip08456 · 17-05-2011, 21:22

The point is you can't use the hub as a modem only until bridge mode is implemented.

Chrysalis · 18-05-2011, 07:23

Quote:

Originally Posted by scott.deagan

I'm not confident that adding a "Bridge Mode" to R27 is going to solve all the problems. I was on the 20Mb service (separate modem/router) since it was released in my area and not ONCE did I have to call Virgin Media.

The reason why I do no believe adding a Bridge Mode will be the magic pill is because I'm using my "Super" Hub as a modem only (I've turned off wireless functionality, placed a WNR2000v2 in the DMZ and connected it via a cable). I am still experiencing issues, such as video and audio streams freezing (and not starting again once they stop), SSH connections being disconnected, PPTP connections freezing and then dropping (etc, etc, etc).

The problems are intermittent, but they happen (too) frequently and on Linux, Windows, and OSX. I also experience the same reliability issues if using wired or wireless connections. Setting the WiFi mode to 54Mb, 145Mb, or 300Mb does not help.

I wish I had never been suckered in to the so called "free" 30Mb upgrade (I was seduced by the promise of a 3Mb upstream). I should have checked the forums first. I did ask to downgrade back to the 20Mb service within 14 days, but Virgin were not going to give me back the old DOCSIS 2 modem - I would still be stuck with the "super" hub.

I don't know if I can wait any longer for the R27 release, and I'm not confident that R27 is going to fix anything at all (judging by Virgin's responses in the forums, if they believe it's just a WiFi issue then they're not going to fix the real problem(s)). A very simple solution would be to allow customers to using their own DOCSIS 3 modems.

Anyway, for me, personally, every time the "glitch" manifests it feels like a hot knife being thrust into the heart of my digital persona. My contract is up, and now there's a new fibre provider in town

.

with DMZ the superhub is still processing the packets and routing the traffic.

As a dumb modem it will simply pass thru traffic as is to another singular device.

eg. with DMZ it will still cause timeouts due to its very agressive internal timeout setting and still process everything through NAT tables, as well as still process everything through its firewall. In a dumb modem mode if integrated properly all that should be disabled completely 100%.

kwikbreaks · 18-05-2011, 07:55

The question in my mind is can they provide a proper bridge mode with the firmware? The modem outlet port is internal and the ethernet ports on the back are connected to circuitry which is controlled by the router firmware so there will still be at least some software involved which they seem to be expert at getting wrong.

Chrysalis · 18-05-2011, 08:11

thats what we will find out.

It may well just be some sort of hack where there is still some internal routing going on.

When the day comes I plan to do some basic tests to see if superhub routing issues remain in bridge mode such as ssh timeouts. IF they all dissapear it would suggest its a proper bridge modem.

I would expect in a proper bridge mode wireless to be non functional and only one ethernet port to work.

kwikbreaks · 18-05-2011, 08:44

... with the public IP on that single port.

I don't have a gigabit router and I have a NAS device sitting on one of the Superhub ports so I'll initially continue trying it as a hub to see if they've fixed the various bugs I've had and try out all the wonderful new features they must surely have added considering the time they've been working on it