Hi there guys,
Been trying to fix this issue for the past two hours but with no success. I have the brand new gigabit internet modem/router (CODA 4582) from Rogers. I don't like its wireless signal and want to hook up my dlink DIR-850L router to it for the boost. The firmware for the router is up to date, I have put the modem intro bridge mode by turning off the gateway function, and I have also reset both the modem and the router to factory settings about five times now. Problem is that when the modem is in bridge mode, it will not allow internet access to the router. The router is not broken or damaged as it had been working fine at a friend's house and the modem also seems to be in working order. I called the Rogers support but, as usual, they didn't help with anything. Anyone know the fix for this?
Thanks so much!
Solved! Solved! Go to Solution.
@NickO10 Sign up for the Beta Firmware Program, the latest Beta Firmware should fix the issue with 3rd party routers.
Send a PM to @CommunityHelps with the subject "Rogers Rocket Wi-Fi Modem Firmware Trial"
Tell them you have the new CODA 4582, and provide your Rogers Account Number, Modem Serial Number, and Modem MAC Address, these can all be found on the back of the modem, or login to the modem and the main page has this info
I have a D-Link DIR-880L, and I had the older HiTron CGN3 Black upright modem that had been working fine for quite some time in bridge mode. I too, don't like using the WiFi on these modems, and prefer standalone routers. I have the 250u Ignite package, and I noticed last week that my dl speeds were dropping drastically from averages of 320+Mbps down, and 21+Mbps up to an average of 3-7Mbps down, but uploads still staying at 21+Mbps. This led me to calling in to Rogers tech support, where I was informed that my network had been upgraded and my older black upright HiTron modem no longer supported my internet package and that I needed to exchange my modem for the newer CODA-4582 modem/gateway. Fine I said, exchanged my old modem for the new one, get it home and proceed to set it up. Out of the box direct to my PC, getting speeds upwards of 330+Mbps. So now I set it to bridge mode, and plug into my DIR-880L, run speedtest.net, dl speeds drop to 1-3Mbps over and over, again and again - uploads are still at the same 21-23Mbps... WTH?? So, now I'm on to D-Link tech support, factory reset router, try different router ports, different ethernet cables, still no change, downloads are still 1-3Mbps, uploads still 21-23Mbps, go back to direct to pc from modem, 300+Mbps down, 21-23Mbps up... very frustrating... so now I'm thinking its bad downstream in the router and I go out and buy a brand new, exact same router, upgraded to the latest firmware direct from D-Link tech support, and still the exact same problem: 1-3Mbps down, 21-23Mbps up... I'm at a loss
This might be a lingering problem with communication between the 4582 and 880L . There was an earlier issue where the 4582 would not assign an IP address to D-Link routers due to a problem with how the D-Link routers would connect to a modem (any modem). That's a D-Link issue apparently. I believe that was taken care of with a firmware update to the 4582, and I haven't seen any other complaints with D-Link routers involved. The DIR-880L firmware is dated 14 Nov 2016, which predates the 4582 release, so, there doesn't appear to have been an update for the router since then.
Best bet at this point is for @RogersDave to have a look at this thread and consider the best way forward. Expect a comment or request from him tomorrow. Keep an eye on the thread, and watch for a number overlaid on your avatar at the upper right hand corner when you're logged into the forum. Select the avatar and keep drilling down into the message inbox if you see the number overlaid on the avatar.
I don't get that switch routine. Somehow I doubt that it was absolutely necessary, but, in the bigger picture, the sooner that customers switch to the 4582, the sooner that DOCSIS 3.1 can be enabled at the node.
For now, can you log into the modem, navigate to the DOCSIS WAN page, copy the downstream and upstream tables and paste them into a post. The copy and paste process will paste in the text contents of the tables. This is usually the first place to look for issues. We'll go from there, depending on what turns up.
@Datalink, here is the info requested - running in gateway mode now...
This menu displays both upstream and downstream signal parameters
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||30596000||ATDMA - 64QAM||35.750||4||6400000|
|2||38596000||ATDMA - 64QAM||40.500||6||3200000|
|3||23700000||ATDMA - 64QAM||34.500||5||6400000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
I do not believe it is a problem with your router. I have the Coda modem as well and had the same issue. download speeds were great then they would drop off to around 2-3 mbps. I would reset the modem, called tech support a few times. There were times I even was on 2.4 and about 5 ft away from the modem and it wouldn't let me connect. I figured I would go to best buy and I bought a tp link ac3200 router figuring that would fix the issue by putting the coda in bridge mode. worked great for a couple of days then the same thing happened, went from around 185 mbps on my ignite 100 package down to 2-3 mbps. Called tech support, was advised to swap the modem, did. worked great for about 2 days, then happened again for a few hours, then the speed picked back up to 185 ish.... no idea what is happening. But don't think it is the routers..
not 100% about the modem either.. as there are/can be many which work fine without the drops.
One thing to check.
Are you able to access the modems interface while its in the slow speeds?
Check your signal levels at that time, vs at a good time.
Will indicate if its a signal level drop, etc.
One also thing to do.. would be capture a few good traceroutes to say google.com at a good time, and then a bad time.
May help see if its a node issue nearby causing it.