I have another issue for investigation. DHCP reservation table is not working anymore.
Old data entered from the past is correct and it works. All new entries are not working.
I added new device to DHCP table and it shows up with random number and note on the side "DHCP-Reserved" in active device list. Changes to the DHCP table are also causing hard reboot of the entire modem. I don't remember modem doing this in the past.
Word of warning to anyone using OOMA VOIP.
In working to track down my HTTPS issues, I re-enabled the gateway function of the modem and decided to use it for traffic routing instead of my Apple Time Capsule.
Everything went fine until I plugged my OOMA Telo station into the CODA-4582 (via ethernet). Within minutes, I could no longer access the CODA's GUI page, and my speeds had dropped to about 10Mbit. The gateway then started rebooting every hour or two.
Unplugging the Telo resulted in an *immediate* reboot of the CODA Gateway, then everything was back to normal.
Ironically, this device had been connected with the gateway functions disabled, in exactly the same way, without issue prior to this.
I decided to connect via Wi-Fi instead, in case this was some sort of ethernet issue. But the same thing happened.
Enabling SIP ALG, however, seems to have completely resolved the issue. If you *disable* SIP ALG, the gateway absolutely freaks out with the Telo connected.
I'm not sure if Ooma is doing something weird with the VOIP setup or not, but it's telling that the device connected to the CODA Gateway, with gateway functions disabled, works perfectly fine. It was literally the last thing I was expecting to cause the slowdown since it moves nearly no traffic when idle.
Also, as an update, this switch (removing the Time Capsule) *seems* to have resolved the HTTPS issues I was experiencing, but I need a few more days to confirm.
Just an FYI for both Rogers and anyone else with a similar setup on the Beta Firmware.
CODA modem and streaming issue
I just received a new CODA modem which I successfully put into bridge mode and is connected to my EERO mesh router system - via ethernet port.
Since getting the new modem, I have noticed that when I am streaming something on my android box, at times, it will buffer and then just stop ad not resume playing. I never had this issue before with previous modem.
It is not the router system as it is brand new, and the modem too was new.
Can anyone offer me a simple solution to fix this?
Thank you for your post and welcome to the Rogers Community Forums!
I know how much of a pain it can be when your streaming devices are not working properly especially if it only happened after upgrading your modem. =(
You've definitely reached the right place to find a solution to this matter. We can start by answering the questions below:
We look forward to hearing from you!
The android box is connected to the router directly by ethernet.
I have only noticed the issue when streaming on android box but speeds are good - approx 300 down 20up.
It came factory reset.
I have tried configuring a different DNS on router but that didn't help.
As I said I am only seeing the issue when streaming directly on the android box via ethernet which should have the strongest connection, via Wifi it's the same story.
Its almost like the ethernet port is shutting off mid stream. That possible?
@dzygadlo I wonder if you're getting momentary dropouts in the cable service? Do you happen to run anything else like cable tv where you would notice the same issue?
To prove or disprove the point, you could run a ping test to the Cable Modem Termination System, which the modem connects to. That would show if you're seeing any packet loss between the modem and the CMTS. That packet loss should be down below 0.01 percent, so, anything much higher would probably point to a cable or connector issue. If you happen to be on an unlimited plan try the following:
1. with a pc connected to the modem via ethernet, run a trace to anywhere;
2. The first IP address in the trace will be the modem, the second will be the CMTS. If you happen to have the modem in Bridge mode with a follow on router, the first IP address will be the router, the next address will be the CMTS.
3. Ping the CMTS: Ping xxx.xxx.xxx.xxx -t
4. Use Control^C to stop the test after several hours and have a look at the ping stats. While the data is scrolling by, if there are timeouts you will be able to see them as they occur. You shouldn't be seeing any timeouts. I usually run this type of test for 24 hours when I test for ICMP, UDP or TCP/IP response times.
If you were to run Pingplotter, the dropouts, if there are any would be shown on the plot. Pingplotter will run for 14 days in a freebie Pro mode before it kicks down to a limited free mode. At that point its up to the end user to buy a pro or standard licence. The standard licence is more than adequate, and, you don't have to buy a licence at all. Its a matter of personal choice.
So, if you can, give the ping test a go to see what turns up, if anything.
Sorry but I didn't quite understand what you wanted me to do.
I understood using command prompt to ping and I tried google.com and this is what I got
Pinging google.com [126.96.36.199] with 32 bytes of data:
Reply from 188.8.131.52: bytes=32 time=14ms TTL=55
Reply from 184.108.40.206: bytes=32 time=14ms TTL=55
Reply from 220.127.116.11: bytes=32 time=11ms TTL=55
Reply from 18.104.22.168: bytes=32 time=12ms TTL=55
Ping statistics for 22.214.171.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 14ms, Average = 12ms
Does this reveal anything or not?
I am running pingplotter too
Just FYI too,
I went back to Rogers store and switched back to Rocket modem in case that was the issue.
It sadly wasn't.
Those results are from the Rocket modem not CODA.
@dzygadlo the ping results above don't tell me anything. That test should be run for several hours, looking for dropouts, which will show up as packet loss stats. When you add the -t to the ping command, it will continue to ping until you use Control C to abort the test.
For pingplotter the same idea applies. The default display is the target, so if you are pinging google.com for example, your plot will show the return times and losses for the last hop. What we need to see is the second hop. If you click or double click on the second IP address in the IP address list, that will display the plot for the modem to CMTS hop. Anything else beyond the second hop can be ignored. To close a plot, right click on the the plot in question and select close.
What you can do is use that second hop IP address and copy/type it into the address bar so that the only IP address that Pingplotter pings, is the CMTS itself. That modem to CMTS path is usually the problem path. Typically you will see cable and/or connector issues show up, resulting in packet loss. There shouldn't be any packet loss.
In terms of overall latency, you're better off with the CODA-4582 if you happen to be a gamer or run latency sensitive applications such as voip, video conferencing, etc, etc.
If you happen to be watching the display and see a time period where there is regular packet loss, as in every few seconds or every minute for example, call tech support and ask the CSR to ping the modem from the CMTS, or, ping the CMTS from the modem, either one will do. Explain to the CSR that your experiencing packet loss problems and that your asking for the CSR to run a ping test in order for him or her to see the same occurrence. When you see packet loss, the CSR should see packet loss as well. Also ask the CSR to run a signal check on your modem, just to see if the current signal levels and signal to noise ratios are within spec. Between the signal check and ping test, the CSR should be able to make some determination that a cable/connector issue is afoot and arrange for a tech visit at your convenience.
Also, please have a look at the following post regarding your amplifier configuration: