NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Repeated DHCP assignments in RAX43 log
Starting about a week ago, which is when I think the latest firmware 1.0.12.120 was released, my internet connection across all devices has been very spotty. It will work 100% and then not at all afte...
Further testing showed the issue did actually happen with the ISP-provided router (it’s intermittent so I missed it before). Further digging revealed heavily imbalanced downstream channel power ranging from +0.4 to -11, which the ISP techs confirmed. They have traced the issue much further upstream than the house or local tap and are working on it now.
TL;DR
The router is not the problem and the DHCP logs were likely a result of normal reconnection attempts due to imbalanced downstream bonded channel power levels cause by ISP infrastructure issue(s).
TL;DR
The router is not the problem and the DHCP logs were likely a result of normal reconnection attempts due to imbalanced downstream bonded channel power levels cause by ISP infrastructure issue(s).
Yet another twist. ISP acknowledge infrastructure issues on their end outside of the house, but after they fixed it my situation only improved marginally. This time the ISP provided a dedicated gaming Nighthawk router instead of the combo setup, and the problem was totally resolved. After reconnecting my own RAX43 to troubleshoot, the last thing I hadn’t touched was disabling the Dos attack logs after seeing the false positives coincide with interruptions.
Disabling those logs has resolved about 95% of the problem surprisingly, since CPU usage never showed any strain. Definitely something Netgear should look into (the false positives should have been fixed a long time ago anyway).
It seems the DHCP assignments were just a symptom of these interruptions. I’m going to disable other logs and see if I can iron out the last occasional hangups.
Edit: the ISP’s “fixes” didn’t end up lowering the power level range, which shifted but didn’t get lower in range (~+4 to -8). One tech said it was a problem, the last said anything +10 to -10 is fine… guess the latter was right.
Disabling those logs has resolved about 95% of the problem surprisingly, since CPU usage never showed any strain. Definitely something Netgear should look into (the false positives should have been fixed a long time ago anyway).
It seems the DHCP assignments were just a symptom of these interruptions. I’m going to disable other logs and see if I can iron out the last occasional hangups.
Edit: the ISP’s “fixes” didn’t end up lowering the power level range, which shifted but didn’t get lower in range (~+4 to -8). One tech said it was a problem, the last said anything +10 to -10 is fine… guess the latter was right.