Re: R36 Firmware Beta Test (was R35)
 

I'm quite prepare to give it a go - all I absolutely need is port forwarding and that is there albeit with a very klunky set up procedure.

I never use ISP DNS and it's annoying that the firmware doesn't allow an override but I just manually hard code that.

No Dynamic DNS services but I have a 24x7 desktop so running a software client covers that. Come to that I could do it with an IP webcam I have too.

I don't use torrents so the problems I've seen reported with hangs doing so unless the SPI firewall is turned off really don't matter to me.

WiFi range is poor on R30 and I don't see how firmware could improve it anyway but I only need it for my phone and an iPad. I run a FON router with an external aerial so if I need WiFi in the garden and the SH doesn't provide it that will.

So long as I don't need regular reboots and it doesn't adversely impact web performance it will be OK - my internal network is just a couple of gigabit switches which is why my venerable Buffalo was OK when I was on 10Mbps. I bought the D-Link when I was on 50Mbps and had the Superhub then swapped out for a VMNG300.

Overall I'm pleased with the upgrade 10Mbps to 60Mbps for an extra £2.50 a month is a very good deal even if I didn't hit the 60Mbps but it looks like I am right now. Mind you on 50Mbps it was fine and went down the tubes alarmingly quickly which was why I downgraded to 10Mbps.

Re: R36 Firmware Beta Test (was R35)
 

What's 'clunky' about the port forwarding set-up?

Think of a name, select the start and end ports, the protocol, the last octet of the IP address and click add. Job done.

Re: R36 Firmware Beta Test (was R35)
 

Ours hasn't rebooted at all since we have had R36 kwik. Oddly the wireless is improved but only in terms of reliability (range is still not what you would deem acceptable).

Re: R36 Firmware Beta Test (was R35)
 

Well you forward to an IP address and it's the fixing of that IP to a given MAC that is klunky as you have to manually enter the MAC rather than just select it from a list of attached devices like most other routers I've used. True there is every chance that a well behaved router will always assign the same IP to a MAC it has handled before but sfaik there is no guarantee that it will and I wouldn't trust the SH to do so for sure. Once you've done that the SH reboots. It does that for every one. OK I can understand it may need to do so but it should give you the option to defer that until you've finished making reservations. When I had a SH before on one occasion it managed to corrupt the entire fixed IP table somehow and I had to start over. Not showstopping certainly but tedious, annoying, and totally unnecessary.

Re: R36 Firmware Beta Test (was R35)
 

What firmware version are you using? On my R30 it's just the steps I outlined - no MAC address; no clunkiness; no reset?

Re: R36 Firmware Beta Test (was R35)
 

R30. Are you reserving the IP address as that is what I find clunky not the actual port forward to an IP address.

Re: R36 Firmware Beta Test (was R35)
 

Re: R36 Firmware Beta Test (was R35)
 

ahh; got you.

No, I don't use the feature to force the DHCP to assign a particular IP addresses. However, the way it's done makes sense. I can't see any other way of getting the DHCP server to make particular fixed MAC / IP assignments.

All I do is set an appropriate mask and limit the range of DHCP adresses. Then use statics on the devices that are outside that range but within the subnet set by the mask.

Re: R36 Firmware Beta Test (was R35)
 

Only way they could boost range is by upping transmit to maximum allowed legally and eventhen it doesnt guarantee it will receive the clients signal unless its transmitting high enough for the SH to receive it

Re: R36 Firmware Beta Test (was R35)
 

Sound Great

Re: R36 Firmware Beta Test (was R35)
 

Are they going to take our R36 firmware off us until general release? I hope that isnt the case.

Re: R36 Firmware Beta Test (was R35)
 

I wouldn't have thought so. If the pilot for 8000 users is the same iteration as we Guinea Pigs currently have, then it wouldn't make sense to change our current firmware. Might be worth emailing Mark Wilkin to verify though.

Re: R36 Firmware Beta Test (was R35)
 

i have request if possible to be in the 1st 8000 SH for try the r36
recently had few T3 errors due to congestion with upstream channel and the engineer have fitted a distribution unit
Maybe is a good test for the r36
If not in few weeks should be rolled out hopefully and i will know if is good that time

Re: R36 Firmware Beta Test (was R35)
 

Whats a distribution unit when it's at home?

Re: R36 Firmware Beta Test (was R35)
 

Well yes you have to specify both the MAC and the desired IP but manually entering the MAC - especially when you can't just use copy/paste is tedious and error prone - as I said originally most if not all routers I've used just allow you to select the device you want to reserve an IP for from the list of connected devices. With Tomato at least you build your table of reservations then hit apply just the once and it then restarts some services rather than doing a full reboot.

I find setting static IPs on a number of devices more of a PITA than just setting them to use DHCP which is virtually always the default anyway then reserving whatever the router allocated useng the router GUI.

That said unless the router resets to defaults (which was a common problem with the Superhub) it doesn't need doing very often and I imagine there is zero chance of VM changing it.