Superhub Firmware R37 - Page 8

Sephiroth · 30-11-2012, 17:30

Quote:

Originally Posted by General Maximus

It cracks me up. If they cant even get the firmware to the shubs what hope have you got of the firmware actually working.

I don't think they should announce dates for anything anymore because they can never meet them. They should just do stuff and let us be pleasantly surprised when it actually happens. That way we wouldnt know about the constant delays with everything.

LOL. We'll get the conspiracy theorists out in force claiming that it was because R37 downloads were corrupting!!

General Maximus · 30-11-2012, 17:36

well the fact that they put jimexbox back to R36 tells me that there is a massive bug/flaw in R37 which they have only just discovered and didn't pick up in their "successful and extensive trials"

jimexbox · 30-11-2012, 17:40

Quote:

Originally Posted by General Maximus

well the fact that they put jimexbox back to R36 tells me that there is a massive bug/flaw in R37 which they have only just discovered and didn't pick up in their "successful and extensive trials"

I was put back on R37 a couple of weeks ago, only checked the superhub after I had a wireless dropout. The words arse and elbow spring to mind, they apparently had no idea why I was back on R36. I was then ignored.

babis3g · 30-11-2012, 18:12

it looks like they send to your SH wrong firmware, so they stopped...it says v2.37 and not r37

qasdfdsaq · 30-11-2012, 22:04

Quote:

Originally Posted by Hugh

Military time is so much simpler - 23:59 rolled over to 00:00 (all Zulu time).

Indeed however the air force apparently disagrees even on that

From the link I posted earlier:

Quote:

WHEN I was in the RAF 50 years ago this problem was solved by defining it out of existence. Working on the 24-hour clock meant that there was no difficulty with midday - 1200 hours - but the Air Force could not countenance 0000 hours for midnight. We were instructed that the Air Force day began at 0001 hours and ended at 2359 hours. The two minutes between were ours to use as we liked.

If even parts of the military can't get military time right, what hope is there of VM doing it? :-P

**Hugh** · 30-11-2012, 22:09

Methinks he was talking round things - I worked shifts for six years in ten different countries, working thru midnight intercepting sigs, and we logged stuff at 00:00 (and these went to NSA, GCHQ, DSD, CSE, GSCB, etc), so this leads me to believe this was a universally accepted mode of timekeeping...

Sephiroth · 30-11-2012, 22:25

Quote:

Originally Posted by Hugh

Methinks he was talking round things - I worked shifts for six years in ten different countries, working thru midnight intercepting sigs, and we logged stuff at 00:00 (and these went to NSA, GCHQ, DSD, CSE, GSCB, etc), so this leads me to believe this was a universally accepted mode of timekeeping...

If only R37 modem mode was as presact about timekeeping in the logs!

ileikcaek · 01-12-2012, 01:42

The update Mark posted on the VM forum has been edited to not actually mention they have suspended the R37 update. Probably something he was told to do by his superiors as a form of damage control.

This is how it reads now:

Quote:

The deployment of the R37 firmware began this week and we’re looking at the early results of this. As with all roll-outs, it can take a number of weeks – for example R36 took around one month to roll-out to all customers – but we’ll keep you up to date with our progress.

01-12-2012, 02:07

It would be funny if it wasn't pathetic. How long have they had to sort this out? I don't mean just R37 (which perhaps should have been R3, it works now and apologies for the crocks that predated this..). How many incarnations do they need for crying out loud?

General Maximus · 01-12-2012, 08:37

this is great. They have dug themselves a hole before they have even started

They specifically said that it was going to specific tiers on specific dates over the course of a week and now it is going to be a month (if not more) and they don't know when it is coming down.

I think my vmng300 is worth its weight in gold atm

ileikcaek · 01-12-2012, 09:19

What's worse is Virgin has never addressed the issues with FTP/SFTP/SSH sessions etc timing out after a few minutes of idle time requiring you to reconnect to the server you're trying to access many more times than should be acceptable.

It's really annoying, I was hoping they would fix it so I held off on buying a new router and using modem mode but I think I'm going to make an investment pretty soon in one of the fancy ASUS routers (possibly not the RT-AC66U due to the cost but we will see.)

qasdfdsaq · 01-12-2012, 11:30

Quote:

Originally Posted by Sephiroth

If only R37 modem mode was as presact about timekeeping in the logs!

Thing with these embedded devices is if they don't have a real-time clock and a backup battery, it's impossible for them to know the time after a power cycle. The time of any event in the logs can only be determined if, and after, a live connection to the network is made.

Course any screwups after that point are inexcusable, a decent NTP implementation can be fit into just a couple KB of code.

Sephiroth · 01-12-2012, 14:00

Quote:

Originally Posted by qasdfdsaq

Thing with these embedded devices is if they don't have a real-time clock and a backup battery, it's impossible for them to know the time after a power cycle. The time of any event in the logs can only be determined if, and after, a live connection to the network is made.

Course any screw ups after that point are inexcusable, a decent NTP implementation can be fit into just a couple KB of code.

But in router mode, it times and dates the logs correctly. Indeed, you can reach the router mode network log after the modem mode sign-in.
http://192.168.100.1/advanced_list.asp
The logs have the same events but diffeent dates/times.

And the events in the log in modem mode are completely out, including the T3s you get during a live connection.

Sephiroth · 01-12-2012, 16:35

The T3s are because there has been an upstream timeout on a keep-alive response. 16 consecutive T3s and you get a T4 because the CTS thinks you're up the creek and the modem is reset.

The other Ts can be googled!

babis3g · 01-12-2012, 16:47

UPDATE V2.37 firmware (r37)

it seems has settle down the jitter having the modem (in modem mode) continues ON

i am also getting lower ping with my 2850n router
(before with same router,had 10-12ms mainly..now down to 7-9ms)
Firmware look ok for modem mode(time will show) but download speed is poor ...but is always like that most of the times with VM