FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

[RogersMargaret]

Hello Community,

We are currently offering our users an exclusive opportunity to participate in an upcoming trial of the new firmware for our Rocket Wi-Fi Modem (CGN3ACR, CGN3AMR and CGN3ACSMR) and Rocket Gigabit Wi-Fi Modem (CGN3552 and CODA-4582). For details of this program, please see this thread.

This thread will be used for feedback regarding the firmware.  We've invited @RogersSergio, @RogersSyd & @RogersBob from our Networking team to participate in this thread.  Your feedback is very valuable and will be used to enhance the firmware before it is released publicly.

Thank you for your continued feedback and support.

[VivienM]

---

@blues_clues wrote:

---

@mozerd wrote:
I absolutely agree with @Datalink

a single SSID for both networks is a VERY BAD idea. Keep them separate ... BETTER still put the Gateway in BRIDGE mode and use a good quality Router that will perform MUCH better for every function and capability under its control.

---

Not so.  All routers should have this as an option.  If it does not work how the user expects, they can choose to make them separate.  My personal experience with various makes of Enterprise and SOHO Wireless routers have not been an issue with this configuration.  I would blame the chipset on the client and the drivers rather than the wireless router having this capability.  I have deployed an enterprise wireless and numerous home environments for over 60K users without an single isse.

---

We're talking about residential equipment here, which in my experience for whatever reason tends to end up on 2.4 far too often. I agree that separate SSIDs are unelegant, but devices stupidly ending up on 2.4 is far worse. The advantage of a separate SSID for 5GHz is that 1) devices will never go on the 2.4 SSID accidentally, and 2) you can very readily identify 2.4-only client devices since they won't see the 5GHz SSID.

In Windows, at least, it's relatively tricky to tell whether you are connected to 2.4 or 5GHz if you have the same SSID on both. OS X is much easier. Not sure about mobile devices. 

Do you really expect home users to be able to tell whether their same-SSID-for-both-bands network is working properly and troubleshoot it if it isn't? Or they'll just get horrendous performance when their 802.11ac clients in a dense urban environment decide that because the signal strength 'looks' better on 2.4, that's what they should use... 

In any event, if you want to set up a proper one-SSID network using serious access points, nothing is stopping you. But I think the Hitron gateways are problematic enough without adding the complexity of clients connecting to the wrong band on top of things... 

[blues_clues]

---

@VivienM wrote:

---

@blues_clues wrote:

---

@mozerd wrote:
I absolutely agree with @Datalink

a single SSID for both networks is a VERY BAD idea. Keep them separate ... BETTER still put the Gateway in BRIDGE mode and use a good quality Router that will perform MUCH better for every function and capability under its control.

---

Not so.  All routers should have this as an option.  If it does not work how the user expects, they can choose to make them separate.  My personal experience with various makes of Enterprise and SOHO Wireless routers have not been an issue with this configuration.  I would blame the chipset on the client and the drivers rather than the wireless router having this capability.  I have deployed an enterprise wireless and numerous home environments for over 60K users without an single isse.

---

We're talking about residential equipment here, which in my experience for whatever reason tends to end up on 2.4 far too often. I agree that separate SSIDs are unelegant, but devices stupidly ending up on 2.4 is far worse. The advantage of a separate SSID for 5GHz is that 1) devices will never go on the 2.4 SSID accidentally, and 2) you can very readily identify 2.4-only client devices since they won't see the 5GHz SSID.

In Windows, at least, it's relatively tricky to tell whether you are connected to 2.4 or 5GHz if you have the same SSID on both. OS X is much easier. Not sure about mobile devices. 

Do you really expect home users to be able to tell whether their same-SSID-for-both-bands network is working properly and troubleshoot it if it isn't? Or they'll just get horrendous performance when their 802.11ac clients in a dense urban environment decide that because the signal strength 'looks' better on 2.4, that's what they should use... 

In any event, if you want to set up a proper one-SSID network using serious access points, nothing is stopping you. But I think the Hitron gateways are problematic enough without adding the complexity of clients connecting to the wrong band on top of things... 

---

Let's not excuse Hitron for not getting it right, whereas other SOHO router makers have this working.  Residential users should not have to care about multiple SSIDs, radio bands and complex configurations.

[Datalink]

@blues_clues I would definitely agree with that.  

Personally speaking, it sounds like you're the perfect candidate for the position of Wifi Configuration Expert.

All in favour?

Aye.....

Motion carried.  Isn't democracy wonderful.  🙂

Seriously, with your experience in this area, if and when you have time, it would be nice to see a guide to setting up multiple networks with singular SSIDs, and making it work.  If there are issues to look for in terms of wifi clients and drivers, please include details such as that.  Absolutely no pressure, but I'm sure that users on the forum will appreciate the advice.

[blues_clues]

Thanks for the vote of confidence.  I will help as much as I can,  This topic is the first thing I noticed in going from my Linksys e4200 to the Hitron.  I was disappointed when I tried configuring the Hitron to a single SSID for both bands as it was working flawlessly with my lowly Linksys.  The reason I stuck with the Hitron and not got to bridge mode is the processing power and the ability to support close to line speed Gigabit.  My Linksys capped out at 250Mbps.   Plus, I did not see spending $100+ on fixing wireless issues that could not be remediated via work arounds.

[VivienM]

---

@blues_clues wrote:

---

@VivienM wrote:

---

@blues_clues wrote:

---

@mozerd wrote:
I absolutely agree with @Datalink

a single SSID for both networks is a VERY BAD idea. Keep them separate ... BETTER still put the Gateway in BRIDGE mode and use a good quality Router that will perform MUCH better for every function and capability under its control.

---

Not so.  All routers should have this as an option.  If it does not work how the user expects, they can choose to make them separate.  My personal experience with various makes of Enterprise and SOHO Wireless routers have not been an issue with this configuration.  I would blame the chipset on the client and the drivers rather than the wireless router having this capability.  I have deployed an enterprise wireless and numerous home environments for over 60K users without an single isse.

---

We're talking about residential equipment here, which in my experience for whatever reason tends to end up on 2.4 far too often. I agree that separate SSIDs are unelegant, but devices stupidly ending up on 2.4 is far worse. The advantage of a separate SSID for 5GHz is that 1) devices will never go on the 2.4 SSID accidentally, and 2) you can very readily identify 2.4-only client devices since they won't see the 5GHz SSID.

In Windows, at least, it's relatively tricky to tell whether you are connected to 2.4 or 5GHz if you have the same SSID on both. OS X is much easier. Not sure about mobile devices. 

Do you really expect home users to be able to tell whether their same-SSID-for-both-bands network is working properly and troubleshoot it if it isn't? Or they'll just get horrendous performance when their 802.11ac clients in a dense urban environment decide that because the signal strength 'looks' better on 2.4, that's what they should use... 

In any event, if you want to set up a proper one-SSID network using serious access points, nothing is stopping you. But I think the Hitron gateways are problematic enough without adding the complexity of clients connecting to the wrong band on top of things... 

---

Let's not excuse Hitron for not getting it right, whereas other SOHO router makers have this working.  Residential users should not have to care about multiple SSIDs, radio bands and complex configurations.

---

Who has it working?

My bad experiences were not with a Hitron; they were with a D-Link, a fancy dual-band one, maybe a DIR-825? I forget the model number, but it was a total disaster. 

I have never tried running single-SSID with Asus, say, but I know their firmware defaults to separate SSIDs as well. 

[mozerd]

---

@blues_clues wrote:

---

@mozerd wrote:
I absolutely agree with @Datalink

a single SSID for both networks is a VERY BAD idea. Keep them separate ... BETTER still put the Gateway in BRIDGE mode and use a good quality Router that will perform MUCH better for every function and capability under its control.

---

Not so.  All routers should have this as an option.  If it does not work how the user expects, they can choose to make them separate.  My personal experience with various makes of Enterprise and SOHO Wireless routers have not been an issue with this configuration.  I would blame the chipset on the client and the drivers rather than the wireless router having this capability.  I have deployed an enterprise wireless and numerous home environments for over 60K users without an single isse.

---

60K users --- wow --- ... 

[blues_clues]

---

@mozerd wrote:

---

@blues_clues wrote:

---

@mozerd wrote:
I absolutely agree with @Datalink

a single SSID for both networks is a VERY BAD idea. Keep them separate ... BETTER still put the Gateway in BRIDGE mode and use a good quality Router that will perform MUCH better for every function and capability under its control.

---

Not so.  All routers should have this as an option.  If it does not work how the user expects, they can choose to make them separate.  My personal experience with various makes of Enterprise and SOHO Wireless routers have not been an issue with this configuration.  I would blame the chipset on the client and the drivers rather than the wireless router having this capability.  I have deployed an enterprise wireless and numerous home environments for over 60K users without an single isse.

---

60K users --- wow --- 

---

Yes, wow! In keeping with the topic, 60K users on single SSID, dual band radios, no issues.

[BS]

---

@blues_clues wrote:

---

@mozerd wrote:

---

@blues_clues wrote:

---

@mozerd wrote:
I absolutely agree with @Datalink

a single SSID for both networks is a VERY BAD idea. Keep them separate ... BETTER still put the Gateway in BRIDGE mode and use a good quality Router that will perform MUCH better for every function and capability under its control.

---

Not so.  All routers should have this as an option.  If it does not work how the user expects, they can choose to make them separate.  My personal experience with various makes of Enterprise and SOHO Wireless routers have not been an issue with this configuration.  I would blame the chipset on the client and the drivers rather than the wireless router having this capability.  I have deployed an enterprise wireless and numerous home environments for over 60K users without an single isse.

---

60K users --- wow --- 

---

Yes, wow! In keeping with the topic, 60K users on single SSID, dual band radios, no issues.

---

I will go along with @dlink I would love to see some documentation on using single SSID's using SOHO equipment - I know it can be done on a large scale with high end Cisco equipment and other brands, but these are level 2 networking solutions, and can actually be pushed out on one single SSID to many places all over the world.  So absolutely it is theoretically possible to push out on one  SSID over multiple Wan connections, and mix of enterprise and SoHO products, as long as you find the mixes of equipment that can facilitate this and I am sure that he is more than capable of doing this.  I would love to hear more or see white papers showing how to do this with SOHO and enterprise mix.

Finally, @blues_clues, I too would love reference to how you achieved this, the equipment, the setup (as much as you can say given the need to keep propritaritory information confidential).  I always love to learn and I know theoretically it can be done, I have done it with support from specialists across close to 1000 users, plus guest logins, across many sites in one major city, just not sure how far we could push the typical SOHO equipment.

Bruce

[blues_clues]

---

@BS wrote:

---

@blues_clues wrote:

---

@mozerd wrote:

---

@blues_clues wrote:

---

@mozerd wrote:
I absolutely agree with @Datalink

a single SSID for both networks is a VERY BAD idea. Keep them separate ... BETTER still put the Gateway in BRIDGE mode and use a good quality Router that will perform MUCH better for every function and capability under its control.

---

Not so.  All routers should have this as an option.  If it does not work how the user expects, they can choose to make them separate.  My personal experience with various makes of Enterprise and SOHO Wireless routers have not been an issue with this configuration.  I would blame the chipset on the client and the drivers rather than the wireless router having this capability.  I have deployed an enterprise wireless and numerous home environments for over 60K users without an single isse.

---

60K users --- wow --- 

---

Yes, wow! In keeping with the topic, 60K users on single SSID, dual band radios, no issues.

---

I will go along with @dlink I would love to see some documentation on using single SSID's using SOHO equipment - I know it can be done on a large scale with high end Cisco equipment and other brands, but these are level 2 networking solutions, and can actually be pushed out on one single SSID to many places all over the world.  So absolutely it is theoretically possible to push out on one  SSID over multiple Wan connections, and mix of enterprise and SoHO products, as long as you find the mixes of equipment that can facilitate this and I am sure that he is more than capable of doing this.  I would love to hear more or see white papers showing how to do this with SOHO and enterprise mix.

Finally, @blues_clues, I too would love reference to how you achieved this, the equipment, the setup (as much as you can say given the need to keep propritaritory information confidential).  I always love to learn and I know theoretically it can be done, I have done it with support from specialists across close to 1000 users, plus guest logins, across many sites in one major city, just not sure how far we could push the typical SOHO equipment.

Bruce

---

I am a Network Architect for Wired/Wireless networks for a major corporation.  I will gladly explain the technology and design around achieving what seems simple with Enterprise gear but a challege with SOHO equipment.  I suggest we move this discussion to another Rogers forum.  This forum is for beta testing the firmware for our host at Rogers and providing feedback.

[RogersDave]

This is getting slightly off topic and I figured it would turn into a heated debate but I love to see passion 🙂

I am still working on the getting this as an enhancement request but if it does make it, it will probably be accompanied with a popup or warning that this is not the recommended configuration and may degrade performance.
 
When it comes to WiFi design, the most complex design is arguably a stadium due to very high density of users and the inherent interference issues that a large open area creates.

I worked on the Rogers Centre WiFi design (53,000 seats) and single SSID for both bands is the only possibility we had because the traffic levels are so high and all available spectrum must be used. We can’t expect visitors to move from one SSID to another either.

However, and that is the big difference compared to a residential deployment, there is actual RF design that comes into play. Power levels are adjusted, mandatory and supported bitrates are tuned to adjust cell edges and features such as RX-SOP to enabled to improve roaming.

On most home routers, the 2.4 GHz mandatory bitrate is set to 1 Mbps which makes the coverage area of 2.4 GHz much larger than the 5 GHz. As clients move away from the access point, they will roam to the 2.4 GHz band and stick to it after. This problem is especially amplified with “i” devices that have an marked preference for 2.4 GHz.

So in enterprise/public deployment, I recommend a single SSID for both band but at home, I run 2 distinct SSIDs.

[JohnBeaudin]

@RogersDave

I have a question for you.

Before you guys announced that you were working on improving latency/ping with new firmware, my only hope to get a better ping was DOCSIS 3.1

DOCSIS 3.1 technology includes the latest and greatest of digital communication technologies such as LDPC encoding, very high modulation orders (4096 QAM for example), more than 1 GHz of usable spectrum and support of QoS and low latencies

According to cablelabs DOCIS3.1 is day and night and the latency is alot better.

Now last week Videotron already announced they will be the first provider in Canada to go DOCSIS 3.1 , so I assume Rogers will likely follow soon.

Now my question is, will DOCSIS 3.1 be as good as cablelabs describe it? in terms of ping for us online gamers?

John

[AtlantisSRT4]

I would appreciate if anyone could push the beta firm to my modem, I just recieved a msg saying within 7 buisiness days.... This is my last ditch attempt at remedying the latency issues I have been having which have made my connection near unusable in the manner I need it. Sorry if this is in the wrong thread

[huh666]

@RogersDave I have a CGNM-3552 on .22 firmware.  I'll gladly try .27.  Thanks

[blues_clues]

Came across this a few times.  Was waiting for it to recur and it did.   Admin/Device Reset/Reboot doesn't always work.  I had to power off/on.  Could be an issue due to long uptime between reboots, related to pesky memory leaks.  My uptime was 22 days.

[BS]

Boy 22 days uptime is certainly nothing to write home about. 

[lethalsniper]

I thought .27 firmware doesn't support CGNM-3552 ?

[RogersDave]

---

@lethalsniper wrote:
I thought .27 firmware doesn't support CGNM-3552 ?

---

The firmware versions on Hitron "AC" modems (that includes CGNM-3552) are unified which means it can be loaded on any of the CGN3ACR, CGN3AMR, CGN3AMF, CGN3ACSMR and CGNM-3552.

That being said, the issue where firmware 4.5.8.27 limits the upload speed to 15-16 Mbps which affects a small proportion of the CGN3ACR, CGN3AMR, CGN3AMF and CGN3ACSMR virtually affects all CGNM-3552.

So onn the CGNM-3552, I haven't pushed a large scale upgrade to .27 yet but I can push it if a user requests it and knowingly accepts the limitation in upload speed.

Dave

[Mythen]

@RogersDave

I have the 3552. What applications should I see the latency improvements. I have the. 27 firmware

Mythen

[alback]

Last Tuesday, I requested the beta to be uploaded to my CGN3ACR modem as it has 4.5.8.16.  I am wondering why it has taken this long to load.

This modem has the 2.4 wireless Led on even though it is run in bridge mode - and I have confirmed the wireless is turned off.

Another question I have is whether this is the correct modem to use for ignite 100 plan, or whether the CGN3ACSMR or CGNM-3552 would be better modems.  I will continue to use the Rogers modem in bridge mode no matter which model I use.

My event list from the modem shows a CMTS-MAC address.  I have only had one disconnect in the past few days, fortunately.

thanks,  

[RogersDave]

---

@alback wrote:

Last Tuesday, I requested the beta to be uploaded to my CGN3ACR modem as it has 4.5.8.16.  I am wondering why it has taken this long to load.

Alback, Not sure how you sent that request or if I've missed it but I sent the upgrade your way.

Another question I have is whether this is the correct modem to use for ignite 100 plan, or whether the CGN3ACSMR or CGNM-3552 would be better modems.  I will continue to use the Rogers modem in bridge mode no matter which model I use.

For Ignite 100 service, the CGN3ACR is perfectly fine.

Dave

[RogersDave]

---

@Mythen wrote:
@RogersDave

I have the 3552. What applications should I see the latency improvements. I have the. 27 firmware

Mythen

---

Firmware 4.5.8.27 only includes ICMP (ping) latency improvement.

I'm hoping to see improvement with TCP and UDP in an upcoming release.

Dave