RogersDave wrote: ...
Will the modems from trial FW pool download latest production FW from Rogers server on modem Reset? Or revert to FW stored on ROM?
Also, why in Bridge mode a LAN router wired to CODA with 0.33 FW gets Rogers WAN IP from a different range (like 98) compare to CODA in Gateway mode (like 140), and respectively max wired speed on a Gigabit sub in Bridge mode notably drops probably limited by the new IP pool speed restrictions?
I am on .33 coda 4582 gateway mode and yes the modem reboot about twice daily, however I prefer to stay on .33 because I don't get huge lag spikes when I play video games like I used to on previous firmware version.
.33 did something good with the random lag spikes but it re-introduced the random reboot, hopefully you guys can sort this out.
@arnym21 there is no speed restriction for the 4582, in terms of the modem operating in Gateway or Bridge mode. You should see the same speedtest results from either mode. Why you don't see that is mystifying to say the least. As you indicated earlier, installing a different NIC might make a difference. Beyond that, the processor speed, memory amount on the motherboard and hard drive type and transfer rate also comes into the picture.
One thought that came to mind, you will see different WAN IP addresses when you shift the modem from Gateway to Bridge mode. The CMTS assigns IP addresses which are in part based on the device MAC address. The IP address are not static and do not appear to be assigned statically to a specific port at the CMTS which then connects to the modem. If you run the modem in Bridge mode, you can actually change the routers MAC address by cloning different MAC addresses. However, you would have to ensure that the MAC address you are using isn't already in use at your CMTS. The router will let you know if the MAC address that you are attempting to use is not a valid MAC address. I'm wondering if the reason that you see a speed drop is partly or wholly based on a MAC address issue?
It looks like Rogers hub routers have QoS settings differences based on customer IP pool range. Otherwise how would they give priority to commercial customers? To my understanding, all residential users are mixed into same busy Rogers pipe regardless of their sub level, so we can observe real world internet speeds are way slower compare to Rogers Speed Test results. Also I observe large file & torrent download speeds are limited to 15MB/s on a Gigabit sub any time of day or night, while they should be at 125MB/s or near that maxed.
It appears varying IP pools may be assigned to different hub router ports, and each port likely has own QoS settings. Speaking of Bridge mode, I use the same physical setup either in Gateway or Bridge mode, so while other factors you mentioned are important, they remain the same. That's why it looks as either FW issue, or hub router IP range based QoS limitation.
Keep in mind that although one can run ~950Mb/s on a download test, that doesn't mean real world sites are going to give you the same data rates from their servers. So, in a way the speedtests are artificial and really prove that the "last mile" from the CMTS to the modem, and your equipment can support rates up to and including 950 Mb/s on a gigabit plan.
Two points come to mind:
1. Its always possible that you have a bad modem. That's actually pretty rare from what we see in the forum, but, you could swap it out for test purposes. That would eliminate the modem from the list of causes; or
2. There is a configuration issue with your CMTS. If so, this is the first issue of its type that has been posted in the forum, where one modem mode works and the other doesn't. That would require someone like @RogersDave to check your CMTS configuration.
Good suggestions. Lets hope they'll look into that before the next trial FW build.
As to "real world sites", interesting point, especially when you discuss it with Bell Fiber Gigabit subscribers who wows their real world browsing experience.
I just received some fresh news from Hitron. They believed they have identified the source of the reboot issue and will be providing me an incremental build tomorrow (I'm expecting it to be 184.108.40.206T2).
As soon as I have this firmware, I will push it to the firmware trial participants who identified this as an issue in this thread (@tester2013, @JohnBeaudin, @hoopdogg, @zardoz99, @lethalsniper, @Windwalker, @pacerdjl, @RyzenFX, @georgic, @Nadernt, @Triple_Helix, @Mythen, @User1445713, @sputnik62, @arnym21, @WestPoint). I'll then proceed with all the other modems Thursday and Friday based on stability.
Some other answers
@WestPoint, the firmware 220.127.116.11T2 does exist and is really the production one. I believe that frontline agents however don't see it labelled as 28T2 but only 28. The reason it is not in the release notes in this thread is because this firmware was never tested as part of this firmware trial program. It is essentially the same as firmware .27 without Rogers branding.
@arnym21, Factory reset will make the modem accept a full configuration from the network. This configuration states that the modem must be running network firmware 18.104.22.168T2 (which the modem will download automatically).
Regarding the IP pools between Bridge modem and Gateway modes, they are not different. What happens is that each CMTS has multiple IP pools from very different ranges (it occurred over the years as we added IP blocks). When a new MAC address is seen on the network, or a MAC address we haven't seen in the last seven days, our DHCP server pick an available IP and assign it to the device. In gateway mode, the MAC address that our DHCP server sees is the modem MAC while in bridge mode, it will be the MAC of the 3rd party router. Switching from bridge to gateway therefore results in an IP change but they could technically be in the same range, it is random.
The QoS configuration also is not tied to the IP address but to your modem class of service which is linked to the plan you subscribed to. For example, if you subscribe to Ignite 500u, the class of service will cap the speed at 500 Mbps downlink and 20 Mbps uplink. There is no difference between the class of service in bridge or gateway mode.
In your specific case, if your speed is reduced when in bridge mode compared to gateway, I suspect it has to do with the capability of your 3rd party router but you'd have to provide some specifics on the model of router you are using. We have experts in this community that should be able to assist in optimizing the settings for the best performance.