Re: R36 Firmware Beta Test (was R35)
 

Hi Bungle

That's what I've done for R36. I've changed from modem mode to router mode, wireless off and, in my case, only one wire out to my usual router (which I've set into Bridge Mode).

What you want to do should work, though provided that there are no firmware issues when using more than one router port.

So that's a go and there's no advice you need provided you can use the ASUS Wizard (which is very good).

Re: R36 Firmware Beta Test (was R35)
 

Thanks Seph, hopefully one day I can have my damn network somewhere close to how I like lol.

I am using the Custom firmware on this router which seems to be better than the asus one, fingers crossed :)

regards

Re: R36 Firmware Beta Test (was R35)
 

Still no R36 on XL.

Edit

An update has been provided today on the community forums from Mark Wilkin :

'Sorry for any confusion here I suspect the information I had on this had a typo in it. To clarify some of you on 30Mb will be able to get R36 by re-booting your Super Hub right now, everyone else who hasn't been able to get it yet will be able to before the end of the week (either Thursday evening or Friday morning) I'll post an announcement once it's confirmed'

Re: R36 Firmware Beta Test (was R35)
 

I've still yet to get R36 on my 100MB package up here in TS19 area, no amount of rebooting or factory pinhole resetting seems to be picking it up. So hopefully by the end of the week, if not a 150 call -.-

Re: R36 Firmware Beta Test (was R35)
 

Don't wait till the weekend. Call them now.

Re: R36 Firmware Beta Test (was R35)
 

Well gave them a ring and their sending a engineer out since one of the downstream channels is sitting at 38-40 power level on QAM256, plus the firmware wouldn't pick up on the superhub after the techie on the phone tried to force it onto the superhub, so probably a replacement in order, see on thursday.

Re: R36 Firmware Beta Test (was R35)
 

Got R36 and several reboots today......hmmmmm

Re: R36 Firmware Beta Test (was R35)
 

Since getting the R36 firmware today, I've had to reset my superhub every hour or so because the connection keeps cutting out.

Re: R36 Firmware Beta Test (was R35)
 

I have found that the wifi signal is not acceptable, just as everyone else seems to have. Many parts of the house are on now signal free unlike when I was in modem mode. The latest issue is that I could not log into the superhub at all and had to pull the power cord. What a pile of pants!!

Re: R36 Firmware Beta Test (was R35)
 

Rebooted hub, nothing, then about 3 mins later hub rebooted itself and I now have R36.

Re: R36 Firmware Beta Test (was R35)
 

Back in modem mode!!:mad:

Re: R36 Firmware Beta Test (was R35)
 

Re: R36 Firmware Beta Test (was R35)
 

Welcome to idiot India, I get sent to those and I have to pretend I have fixed something as the call centre have convinced the customer there is a fault

Re: R36 Firmware Beta Test (was R35)
 

When calling customer service, always take option 5 then option 2, this will take you to retentions. Just ask to be transferred to a British call center, as you cannot get any satisfaction in India.

Re: R36 Firmware Beta Test (was R35)
 

Tried that, and it certainly hasn't affected my constant disconnections since the firmware update. Whats worse, is I need to turn my devices off and on again to reconnect to the router seeing as just clicking on "connect" doesn't do the job anymore.

Re: R36 Firmware Beta Test (was R35)
 

this is great, I could write a book on this:

The Trials and Tribulations of the Shub

Re: R36 Firmware Beta Test (was R35)
 

or simply.. FAIL!

Re: R36 Firmware Beta Test (was R35)
 

There's an IP Flood control settings in "Firewall", I've unchecked mine as disconnects always happened when multiple devices were communicating at once (ie when you forced an update on a social media app on a smart phone). It's not disconnected again yet....

here's hoping.

Re: R36 Firmware Beta Test (was R35)
 

Hmm I'm now back in modem mode with my R36 firmware. Dreadful speeds earlier this evening and still not good at all, averaging about 3.5 MB/s rather the the usual 7MB/s. After turning the thing off for two hours I noticed that my IP address has changed from [Mod Edit - IP Address removed] to [Mod Edit - IP Address removed] which seems to be a very different range?

Re: R36 Firmware Beta Test (was R35)
 

82.whatever sounds right because that is what mine has always been. Speeds will be poor in the evening because of congestion, traffic shaping (depending on what you are doing) and stm if you have been naughty

Re: R36 Firmware Beta Test (was R35)
 

They are both VM IP addresses for the warw12 CMTS

http://whatismyipaddress.com/

It's generally not recommended to post your IP address on a public forum in case some nutcase decides to try to hack into you or launch a script kiddy type assault. In truth I'd rate that as pretty low risk myself.

Re: R36 Firmware Beta Test (was R35)
 

Well a update on my situation, the engineer has replaced my superhub, the old one was faulty by quite a considerable margin, so now got a brand new superhub with R36 on, its in router mode and maxing out over 100mbps on the speedtests and wireless is much better to, so overall a good experience for me with the superhub, touch wood it stays like that.

Re: R36 Firmware Beta Test (was R35)
 

Old firmware + modem mode +pre-speed double = 30meg
R36 + modem modem mode + speed double = 10meg
R36 in full router mode = 60meg.

Wired tests.

Re: R36 Firmware Beta Test (was R35)
 

I also unchecked mine and disconnections have stopped...............so far!

Re: R36 Firmware Beta Test (was R35)
 

So basically vm are now punishing users that want to use their own router and rewarding loyal shub users?

Re: R36 Firmware Beta Test (was R35)
 

This is total rubbish. Where did you get this from? Following my glitch the other night I turned the superhub off for half an hour then back on again. Running in modem mode with R36 I have been getting a consistent download of 60 and upload of just under 3 as should be the case.

Re: R36 Firmware Beta Test (was R35)
 

That's a very "unusual" interpretation of the information.....;)

Re: R36 Firmware Beta Test (was R35)
 

Well ... something must going on because some one at VM forums has made this post, filling a form after r36 firmware & lower speeds
http://community.virginmedia.com/t5/...s/td-p/1336300


Any one knows what is the purpose of this form?which one will help?
Thanks

Re: R36 Firmware Beta Test (was R35)
 

My apologies...just notice it & can not edit above post

The main thread is here for users experience slower / corrupt downloads speeds since the R36 firmware
http://community.virginmedia.com/t5/...d/td-p/1337570

Re: R36 Firmware Beta Test (was R35)
 

not sure if this has been posted already but I've found fellow VM customers having problems with their SHs shortly after R36 got pushed. I saw wifi glitched. A simple power down and up did sort the problem out once or twice but connectivity via wifi was real hit and miss, a few of which in areas with next to no other wifi networks to get in the way. Anyway a pinhole reset sorted it.

Re: R36 Firmware Beta Test (was R35)
 

4 Days on and no disconnections ;)

Re: R36 Firmware Beta Test (was R35)
 

I should be on 60Mbps, but since upgrading and moving to R36, the speed has dropped to an average of 29Mbps

Re: R36 Firmware Beta Test (was R35)
 

well, the Flood detection theory hasn't worked for me.

Xbox multiplayer has been rendered completely useless because I fear the connection dropping out constantly.

The virgin media forums are littered with people compaining about the same thing with no solution forthcoming.

What on earth was wrong with the R30 firmware, that worked perfectly fine?

Re: R36 Firmware Beta Test (was R35)
 

can't help but quote Stephen as you are obviously needlessly moaning

Re: R36 Firmware Beta Test (was R35)
 

I'm deeply suspitions that although you can check or uncheck the option the underlying code is disabled. When folks moaned about its effect on pingtest.net results VM came up with a "fix" which worked with amazing speed considering the amount of time and retries other bugs took and are still taking to resolve. I'm pretty much convinced all they did was ignore the setting if it was turned on. Of course I may be over cynical...

In fact I don't think it ever was a real bug - it was just the software doing what it had been coded to do - block a flood of pings.

Re: R36 Firmware Beta Test (was R35)
 

Where on earth do you find your connection speeds on the new R36 firmware?

Thankyouplease.

Re: R36 Firmware Beta Test (was R35)
 

192.168.100.1

dont login and look to your top right for router status

---------- Post added at 17:01 ---------- Previous post was at 16:57 ----------

or login > advanced > under device management click on network status

Re: R36 Firmware Beta Test (was R35)
 

Sat staring at that now and it appears to list everything but speed.

---------- Post added at 17:11 ---------- Previous post was at 17:09 ----------

Ah it only seems to show when you're not logged in... Weird

Re: R36 Firmware Beta Test (was R35)
 

Today I got a 100meg super hub, I was at work and I told the engineer (over the phone) to get them to put the SH into modem mode as there have been issues with it, we was supprised I knew about it, but did so.

When I came home I can only get 25meg, and my routers (ASUS RT-N66U) internet status says "detecting connection again..." and I noticed I was lossing connections to XBL parties.

The engineer phoned back to see if there where any problems with the 1TB Tivo box he installed, and when my dad told him it could take a while for it to get the conections for 100meg a while to settle.

Is there any thing I can do to to help.

Re: R36 Firmware Beta Test (was R35)
 

it makes me cringe when they say that. It doesn't need to settle, it either works or it doesnt. If he has put it in modem mode go to 192.168.100.1 and log in to the shub. I dont know which tab it is under now but look at connection status or something and make sure you have been provisioned for the right speed. You are looking for something like:

[b]Primary Downstream Service Flow[b]
SFID : 900
Max Traffic Rate : 110000000 bps
Max Traffic Burst : 10000 bytes
Min Traffic Rate : 0 bps

Primary Upstream Service Flow
SFID : 899
Max Traffic Rate : 10250000 bps
Max Traffic Burst : 16320 bytes
Min Traffic Rate : 0 bps
Max Concatenated Burst : 16320 bytes
Scheduling Type : Best Effort

Re: R36 Firmware Beta Test (was R35)
 

Taking these two clues in reverse order:

Connection dropping:

Do you lose your internet access when the Asus router is "detecting connection"?

Could be signal levels on your connection or may be a VM network issue. To check levels:

Look at the tabs under http://192.168.100.1/RouterStatus.html

Post the levels from the Downstream tab
Post the levels from the Upstream tab

The levels should have been checked by the installation engineer but this doesn't seem to always be the case...

Speedtest:

How are you testing?
Are you connected by ethernet cable or by wireless?
If wireless:

a) Try an ethernet cable
b) Does your PC support 802.11n or is it 802.11g only? If 'g' then you won't get anything faster around 25Mbps

Re: R36 Firmware Beta Test (was R35)
 

Well, I'm Finally fixed thanks to update on the Virgin Media support forums.

I was lazy when my Superhub was delivered, and just plugged in the old mains lead from my old Virgin Modem "because it fit", not giving a thought to power input/outputs.

The 0.8 A output must have been sufficient for the previous firmware but it definitely isnt for R36. Found the plug that came with the superhub that obviously has the right power output and voila..... no problems.

That'll teach me to be lazy.....

Re: R36 Firmware Beta Test (was R35)
 

when theres a glitch, error, fault whatever and bonding is no more is there a system to find and resync connections? recently ive found ive had to manually reboot. others times in the past it sorted itself out.

Re: R36 Firmware Beta Test (was R35)
 

The attached image shows the process. The CM has to find an US channel in order to send it's initial ranging request. If the CM (SH) is not in a state of grace for whatecver reason, then a reboot is the only way of getting a proper request process. If it is in a state of grace when the glitch occurred, it won't need a reboot.

As broad as it's long.

HTH.

Re: R36 Firmware Beta Test (was R35)
 

sorry I wasn't clear enough. when theres a glitch of some sort and a connection goes down to 1 down channel locked and 1 up channel locked is there a system in place to resync bonding rather than leaving the connection with only 1 channel locked on for each up and downstream

Re: R36 Firmware Beta Test (was R35)
 

I did understand your first note, TH. The operative word here is "glitch". As long as you have the primary DS channel, your circuit can operate maybe even without speed degradation if yu're on 50 meg or below. But it's fairly serious at VM's end if you can't get a bonding group. You keep the Primary Channel because otherwise it couldn't carry on trying.

So then to your question. So it's unhappily chugging along on one DS channel. Presumably you have the blue top light on the SH to indicate DOCSIS 3? I could look up the DOCSIS 3 spec to see if there's auto-recover from this situation but I don't have the time, unfortunately. My instinct is to say that subsequent glitches will occur that would reset the SH and eventually your multiple channels will come back.

If you are suffering this situation, it'a a fault to be reported.

Re: R36 Firmware Beta Test (was R35)
 

Since the firmware update, our wi-fi connection has been abysmal - it would simply time out and I could not load anything. Luckily, I only use wi-fi for my tablet but it was still annoying and nothing would fix it. From all the posts here and on the VM's forum it is obviously to do with the update and - finally - it seems VM are working on a fix. I had restarted the SH this morning again and wi-fi is working properly again, as it used to. Not sure whether this is going to be a permanent state of things - maybe they pushed the fix out through the night? The TIVO got its update through the night so I wondered if there was any connection between the two, or if it is just a coincidence. For all I know it's just a glitch and things will be back to no wi-fi later on.

Just wanted to mention this in case others have had a similar experience.

Re: R36 Firmware Beta Test (was R35)
 

It wouldn't need a reset, as DOCSIS 3 supports dynamic channel and bonding changes, it can add, change or remove channels on-the-fly. In theory, that is, assuming the Shrub's firmware is intelligent enough to cope with it...

Re: R36 Firmware Beta Test (was R35)
 

no on 1 channel locked on the top light is green

do a pinhole reset. poke and hold down for around 20seconds until all lights turn blue then let it load up and try connecting again

---------- Post added at 13:35 ---------- Previous post was at 13:33 ----------

yeah in the past ive found it would sort itself out but recently its taken a manual reboot.

Re: R36 Firmware Beta Test (was R35)
 

Does that reset all the SH settings?

Re: R36 Firmware Beta Test (was R35)
 

I rarely advise people to do a pinhle reset. They just lose their settings and might not be any better of because it's the SH in router mode that is the variable factor here along with its firmware curve-ball.

Theres no relationship to Tivo in this (or any SH related) case. I'm from the convinced school that says you can't rely ever on SH wireless even if it performed OK before. Once it plays up, it'll always play up.

If toy want to stay in router mode, you could buy a wireless accesspoint that connects by ethernet back to the SH. But best of all is to use the modem mode with your own router. That always works well.

Hope that helps

Re: R36 Firmware Beta Test (was R35)
 

I've found after the firmware upgrade a fair few SuperHubs have gone onto glitch. a simple pinhole reset fixed this. and yes you'll have all your settings reset by doing a pinhole reset. its that or live with it.

Re: R36 Firmware Beta Test (was R35)
 

hmmm...

Re: R36 Firmware Beta Test (was R35)
 

Anybody else experience error when trying to change settings on SHUB?

Attachment 23743

Also Getting RS errors never had problems on R35..


Attachment 23744




D...

Re: R36 Firmware Beta Test (was R35)
 

Incorrect error counts are a known R36 bug.

Getting the right coders to fix this stuff can be tricky so it may not get fixed in the next release.

Re: R36 Firmware Beta Test (was R35)
 

:LOL:

Re: R36 Firmware Beta Test (was R35)
 

If only you knew how resourceful (and amusing) you are kwik :D

Re: R36 Firmware Beta Test (was R35)
 

Had a search but cant find anything relevant.

Ive put my SH into modem mode and noticed a couple of things.

IP address given to my router is in the 192.168.0.x range, and the wireless was on (virgin media SSID).

I did factory reset and same.

Shouldn't I have a public IP on the WAN side of my router?

Re: R36 Firmware Beta Test (was R35)
 

Nope - in modem mode, its not acting as a proper modem, its just disables routing functions

Also, are you saying the superhub is transmitting over wireless?

Re: R36 Firmware Beta Test (was R35)
 

Both that and the factory reset suggests it's not in modem mode at all.

Re: R36 Firmware Beta Test (was R35)
 

Sorry Guys, engage brain before typing (read router and understand modem!)

Going back to work after 2 weeks off, I need to use the brain again!

FYI, now actually in modem mode and have public IP on my router.

Re: R36 Firmware Beta Test (was R35)
 

your sure youve enabled modem mode?

Re: R36 Firmware Beta Test (was R35)
 

Yes definitely in modem mode. (It wasn't before!)

Re: R36 Firmware Beta Test (was R35)
 

so whats the problem?

Re: R36 Firmware Beta Test (was R35)
 

Nothing, Like I said I didnt have it in modem mode!

It may have reset into router mode itself, but I'm not sure!

Re: R36 Firmware Beta Test (was R35)
 

by the way if anyone is curious how my highly utilised UBR port looks on this firmware I will switch to the superhub before leaving VM so I have some data on it.