"The hub (W35) reports data usage, but by the calendar month and Rogers says explicitly that their billing measurements do not correlate with what the Hub reports. Any time I have looked at the Hub report, it has seemed chaotic and irrelevant....."
I have posted on this elsewhere, but let me put forth an excerpt from page 31 of the Ericssen W3x Users Guide:
"Note: The data size and packet counters have the upper limits of 4 GiB
and 232 packets (more than 4 billion packets). When these limits
have been reached, the counters wrap around to zero."
The Users Guide is silent on how these counters are synchronized to a monthly period, be it the calendar month, or perhaps a month since the device was started/restarted.
Thus, despite the mention on the Internet Web Page of the W35 User Interface, of Previous Month and Current Month, the implication of the above quote from the Users Guide is that the counters will keep on increasing until they wrap back to zero when they reach 4 Gbyte. I have not checked what is possible through the CLI user interface which is inaccessible to us in any event. I also do not know if there is a backdoor to the W35 which Roger could be, or is in fact, using to reset these counters at whatever time suits them. Somehow I doubt that this is happening.
I have not attempted to track the progress of the W35 counters to determine what patterns, mysterious or otherwise, they are displaying. It would be interesting to see what the correlation is between Ericssen's version of data volume usage and Rogers version of the same thing.
Of course, the W35 Web Page does include the following caveat as a CYA:
"Note: Approximate figures only. Please refer to your bill for final amounts and charges."
if your wife is using Vista be sure you check out the following URL:
This corrects a Vista DHCP-related problem. It was what I needed to use my Vista system successfully with DHCP and the W35. I suspect other devices will also be a problem in using DHCP from them to a Vista system.
You read my mind. I was just researching that when the annopuncement email arrived. Thanks.
BTW, I just checked and the Bell Galaxt Tab I am using on a prepaid plan (with renewal turned off) has an easy to reach web page that reports the data use to the minute and to two decimal places!
It can be done.
You gotta love UBB! But I also love technical transparency.
As you have so admirably documented, transparency is not part of the picture at this time. You ever heard of the saying about the foxes watching the hen house? Yeah, I'm talking about our "friends" at Rogers.
What you and I, and what we all need to do is what xplornetsucks suggested in a previous posting:
"As far as tracking data for multiple computers connected to hub, i think the logical thing to do is add a DD-WRT/Tomato enabled router to you rocket hub via RJ45/wired link.. and let it handle all your wired and wireless connections."
Technically, we need to set up our connection to the Rogers network to include the totally essential feature of a utility connection, the equivalent of the kilowatt-hour meter. This will enable us all to know with certainty that the billings we receive are based on truth and reason.
So, let's put together a joint project to instrument our RocketHub installations with an appropriate router and "tomato" firmware. We all need to document our efforts and the results we get so we can spread the knowledge around for the benefit of all. We will likely need to start a new thread in the Forum to cover the issues related to this unique technical aspect of the use of the RocketHub.
So let's get started!
I would like to take the data volume/charging issues discussion a bit further and compare it with the power utility volume measurement and charges most of us deal with regularly.
In the first place, common practice is that we are billed for electrical power usage based on what we use as measured by the kilowatt-hour meter installed where the power grid connects to our premises. Kilowatt-hour meters are designed and tested for accuracy, and can be easily read by both the power utility and the customer.
At one time I took a course on heavy power, and learned that the power grid has its own internal power losses. In the power grid these can be caused by systemic factors which cannot easily be avoided, as well as by engineering issues, routinginefficiences and equipment failures which can be improved or corrected to reduce or eliminate the power losses.
OK, so get the point, you say. And well you should!
The point is this: the network infrastructure used by Rogers, wireless, wired, broadband, etc., has many features analogous to the commercial power grids. It has systemic factors such as protocol overheads which cannot be avoided. They are a feature of the technology. They are fixed and relatively easy to quantify, and hence to include in your costing algorithm.
But the network infrastructure also has other losses and inefficiences within its fabric. The network will have equipment that fails intermittently, it will have routing inefficiencies that affect the user, and it will need regularly to retransmit user data due to the nature of the media used (e.g., wireless) or due to other complex issues. These are much more variable and hence more of a challenge to include in a costing algorithm. They are also directly affected by how well the network is designed, implemented and maintained.
Anyone who has ever worked in the management and maintenance of a complex network environment has experienced that network failures constantly happen. The MTBF (Mean TIme Between Failure) numbers for equipment are the formal definition of statistically how often failures will happen. You get lots of equipment out there in a large network, and you get lots of failures.
So, Rogers gets to design, build and maintain the network. We the customers get to use the result of their efforts. And we get to pay for it.
The issue is who pays for what. I want to pay for what I use. I want those charges to be reasonable and proportional to what I use. I do not want to pay, nor should I have to pay, directly for inefficiencies and failures in the network which are under the control of the network provider. Rogers needs to have the incentive to implement and maintain the network efficiently. That is entirely under Roger's control. The costs need to be paid by the customers/users. But Rogers needs to have the incentive to make it less costly and more efficient.
So, Rogers (the whole industry, actually) needs to figure out how to put that Gigabyte meter at the point where their network connects to my home or place of business. At that point we can discuss whether their charges per Gigabyte are appropriate.
In the short-term that router with DD-WRT/tomato may be the only practical way for us the user to implement a "Gigabyte meter" for our Internet connection. Information is power, and once we have that information we can determine the appropriateness of the volume-based charges we are sustaining.
"Additionally, web browsers which normally remember usernames and passwords do not automatically fill in credentials on local sites such as 192.168.1.1. making viewing over time a chore."
What browser are you using? I use Firefox which does that no problem at all.
Your comment on UBB and the data volume allotment rolling over on the monthly boundary is apropos. In a pure data volume usage scenario you would not expect otherwise.
The Hub is programmable, and the Linux CLI is documented by Ericssen (see other posting of mine in this Forum). However Rogers has elected not to make the CLI accessible to us by not publishing the password. I can understand the support issues that would ensue if users could go into the CLI. However, particularly for troubleshooting, CLI access would be invaluable.
Assuming that the W35 firewall allows access through on the telnet port, Rogers (or anyone, for that matter) should be able to access our W35's for whatever suits their fancy. So keeping password information hidden is also good for the customers' security.
In correspondence with Ericssen it is made clear that they cannot reveal how to access the CLI for contractual reasons without Rogers' permission. W35's for other vendors have not been so obfuscated.
New! Introducing a new feature: groups. Read more.