@traghipp in theory you should be able to remove the MoCA adapter that is connected to the modem. However, if you are using the privacy settings on the MoCA adapter, you would have to keep using the adapters as the Modem MoCA privacy settings are not included in this trial build. All MoCA adapters either have to be using the privacy settings, or running in the clear. Personally speaking, even though encryption does cost, in terms of throughput, I'd rather run encrypted than unencrypted. You should also have a MoCA filter attached to the end of the cable as it comes in from the street, or utility pole. That prevents your MoCA data from exiting the home, encrypted or not, and would prevent the MoCA data from any of your neighbors from entering your home cable network.
CODA-4582 refuses to give out IP addresses
We recently started using the new CODA-4582 router and it worked great for a while, but recently it's been giving us a bit of trouble. For some reason, after being on for a few hours, it stops giving out valid IP addresses; instead, it gives our devices bogus addresses like the one below:
(sorry about the French; it's "IPv4 Address", "Subnet Mask", and "Router IP", in order)
However, everything works if we give the device a static IP (but I'd rather not have to do that for every single device we own, and it wouldn't work for our guests). We got our router replaced by the local Rogers store but the issue is still present. We tried factory resetting the router a few times to no avail. It started happening about a month ago on/off, but it's been getting worse lately. Is there any way to solve this problem?
Just to confirm, are you using the modem in Gateway mode as modem and router, or in Bridge mode, with a stand alone router after it? It doesn't make sense that you would have the same issue with two modem, and thats just a comment in general for any modem. In cases like this I would suspect a device has a LAN IP address set as a hard address that isn't agreeing with the modem. Perhaps the IP address is outside of the address range of the modem and the modem isn't happy with it ??
Edit: ok, that looks like a default device IP address when the modem or router DHCP fails to provide an address, or can't in the case where a pc, laptop or other device boots up without a connection to a DHCP server. If I had that issue, I would enable or connect one network at a time, such as ethernet, then 2.4 Ghz wifi, then 5 Ghz wifi, looking for the point where the modem fails to give out a LAN IP address. I'm going on the assumption here that there is a problem with a specific device that is causing the DHCP server on the modem to fail. A step by step approach should allow you to determine if that is the case.
Thank you very much for your quick reply! We're using the modem in Gateway mode. I'll try going through all our devices one by one as you suggested and get back to you as soon as possible.
You might be able to do this fairly fast by doing it in groups.
Pick a group, say ethernet devices first, turn off the 2.4 and 5 Ghz wifi and reboot the modem. See what happens when the ethernet devices receive their LAN IP address after the reboot, all as a group instead of one by one. Look for the existing problem.
Then if you don't see anything untoward happen, turn on the 2.4 Ghz wifi. Look for the issue to come up.
Lastly, turn on the 5 Ghz wifi and watch for the issue to come up.
You could always disconnect the ethernet devices except perhaps one pc or lapotp. Turn on one of the wifi networks and reboot the modem. While the modem is rebooting, disconnect the last ethernet device so that the only network running after the reboot is the wifi network. Then do the same with the other network. Enable the 5 Ghz network, turn off the 2.4 Ghz network and reboot the modem. In each case, what you would do is assign the IP addresses in batches, ethernet, then 2.4 Ghz network, then 5 Ghz network.
Hopefully, by doing this network by network, that will help to determine which network is at fault. Then you can drill down into the network device by device to find the culprit.
@joedrew, this isn't a typical or known issue at this point with this modem. Can you log into the modem and check the Software (firmware) Version on the STATUS tab and let me know what that is. If it is V184.108.40.206, please have a look at the DOCSIS EVENT log, also in the STATUS section and look for:
SW Download INIT - Via NMS
SW download Successful - Via NMS
I'm wondering at this point about the firmware version and whether or not that was updated to that version in the last two to three days.
If you have .27 loaded, have you already restarted the modem, as in pull the power from the modem and reapply power? In the post just above yours is a procedure that I posted to locate any devices connected to the modem that might be causing a problem. Can you read thru that and consider running that procedure? When the DHCP fails, is it an immediate failure, as in you restart the modem and the problem comes up immediately, or does it take minutes/hours to occur?
So if we have .29 firmware is it the same as before if we do a Factory Reset it will go back to the older Firmware?
|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||45.500||1||6400000|
|2||38595727||ATDMA - 64QAM||47.500||3||3200000|
|3||23700000||ATDMA - 64QAM||44.000||2||6400000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|