'Modem mode' VM firmware imminent ? Looks like it.....

Been running R30 for a week or so... only in modem mode mind you. Only thing I could measure is that it hasn't dropped out, which it didn't before anyway.

Hooked up with a DIR655 with no issues.
 
I got on the R30 trial becuase I was sick of the Superdud falling over (Multiple T3 and T4 errors and wireless refusing to connect). I am pleased to report my router has not skipped a beat since I got the new firmware pushed. My hub used to crash and die every day, but its been up and running solidly for a record 10 days now !. I can even use my wireless internet radio again and unbelievably it even worked all the way out in the garden this weekend!. Whilst this is all very good news, it does make me fume that VM have been fobbing people off for the last 8 or so months pretending there was nothing wrong. Still, I would even go as far as saying I might not bother plugging in a seperate router at all... until I come across something in the quite basic feature set in the SH I need and it doesn't have.
 
Last edited:
Could one of you lot with the R30 firmware in modem-only mode run some traceroutes to see if there is any latency between your router and the SuperHub? For some reason my traceroutes were showing ~15ms latency between my old modem (non-SuperHub) and Linksys router. Very strange.

Using a SuperHub on its own with the R26 firmware until the new firmware is pushed out :)

No problems here <1ms latency between the hub and my router.
 
Code:
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Tomato.Workgroup [192.168.10.1]
  2     9 ms     7 ms     8 ms  10.188.240.1
  3     8 ms     7 ms     8 ms  newt-geam-1a-ge240.network.virginmedia.net [80.6
.129.13]
  4    14 ms    11 ms   13 ms  exe2-core-1a-pc111.network.virginmedia.net [80.6
.128.193]
  5    11 ms    15 ms    12 ms  glfd-bb-1a-ge-210-0.network.virginmedia.net [195
.182.178.129]
  6    14 ms    11 ms    11 ms  glfd-bb-1b-ae0-0.network.virginmedia.net [213.10
5.172.6]
  7    13 ms    11 ms    13 ms  glfd-tmr-1-ae5-0.network.virginmedia.net [213.10
5.159.46]
  8    16 ms    12 ms    11 ms  tcl5-ic-1-as0-0.network.virginmedia.net [62.253.
185.78]
  9    13 ms    15 ms    12 ms  212.58.239.249
 10    14 ms    15 ms    13 ms  212.58.238.149
 11    15 ms    13 ms    15 ms  virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]


Trace complete.

All looks good here :)
 
SH1.png


SH2.png
 
Because you are still using the built in router, which some people don't want. This makes it just like the old Cable Modems again.
 
Because you are still using the built in router, which some people don't want. This makes it just like the old Cable Modems again.

Which is what disabling wireless and using a Wireless access point does, which has been available in all firmwares? :confused: Why is R30 a sudden ephiphany? it's been well documented with loads of people that disabling the wireless works fine. I have been running like that for ages now, no dropouts, I have loads of devices connected on WLAN and Ethernet with no issues...
 
Which is what disabling wireless and using a Wireless access point does, which has been available in all firmwares? :confused: Why is R30 a sudden ephiphany? it's been well documented with loads of people that disabling the wireless works fine. I have been running like that for ages now, no dropouts, I have loads of devices connected on WLAN and Ethernet with no issues...

Yes, you're right mate, but like I said, theres a lot of people, who don't have a clue how to disable wireless, or anything else in the routers setup, so for them, it's a much simpler solution, to simply put the router into "modem mode"
It's nothing new, I've been doing the same for weeks now, it's really just aimed at the "technically dumb" people
 
Back
Top Bottom