NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Fed up with Netgear ANY router
There was a time, up until the purchase of this router almost a year ago or so, I swear by Netgear, still have the old archaic Netgear wifi, REAL old. This [RAX80], I had high hopes, and it has been...
> 2. Refuses to maintain assigned IP to devices.
Generally, it's more helpful to describe actual actions/results,
rather than attribute an attitude to an inanimate device. How, exactly,
does a router "refuse" to do anything? Does it emit an error message
(some place) like "I refuse to do that!"? "fail" and "refuse" are
spelled differently for a reason.Do you mean that devices with Address Reservations get some wrong
addresses?> 4. Assigns duplicate IPs constantly.
"constantly" or "repeatedly"?
The most common reason for either of those DHCP problems is the
presence of another DHCP server on the LAN. Firmware defects in Netgear
routers are common enough, but problems like those are seldom caused by
the router.
For example, occasionally, some Internet-of-Junk gizmo with a
"hotspot" mode might leave its built-in DHCP server running after it's
been configured, and has joined your LAN. A misconfigured Raspberry Pi
computer is another potential culprit. As usual, many things are
possible.One test would be to disable the DHCP server in the RAX80, and see if
devices still manage to get IP parameters (from some other DHCP server).
> 1. Flaky all the time, losing connection to devices.Not a very detailed description of anything. "connection" between
device and router? "connection" between device and Internet?> 3. NOT the speed I expected!
That's fine for a rant, but not a useful description of anything.
The non-psychics in your audience might know very little about "the
speed [you] expected", or the speed you observed, or how you measured
it.Other basic useful info would include the router's firmware version,
and identification of what's connected to the router's WAN/Internet
port.> I'm fed up, I'm done with Netgear!
This is primarily a _user_ forum. Tell someone who cares?
> 2. Refuses to maintain assigned IP to devices.
Generally, it's more helpful to describe actual actions/results,
rather than attribute an attitude to an inanimate device. How, exactly,
does a router "refuse" to do anything? Does it emit an error message
(some place) like "I refuse to do that!"? "fail" and "refuse" are
spelled differently for a reason.
Do you mean that devices with Address Reservations get some wrong
addresses?
> 4. Assigns duplicate IPs constantly.
"constantly" or "repeatedly"?
The most common reason for either of those DHCP problems is the
presence of another DHCP server on the LAN. Firmware defects in Netgear
routers are common enough, but problems like those are seldom caused by
the router.
For example, occasionally, some Internet-of-Junk gizmo with a
"hotspot" mode might leave its built-in DHCP server running after it's
been configured, and has joined your LAN. A misconfigured Raspberry Pi
computer is another potential culprit. As usual, many things are
possible.
One test would be to disable the DHCP server in the RAX80, and see if
devices still manage to get IP parameters (from some other DHCP server).
> 1. Flaky all the time, losing connection to devices.
Not a very detailed description of anything. "connection" between
device and router? "connection" between device and Internet?
> 3. NOT the speed I expected!
That's fine for a rant, but not a useful description of anything.
The non-psychics in your audience might know very little about "the
speed [you] expected", or the speed you observed, or how you measured
it.
Other basic useful info would include the router's firmware version,
and identification of what's connected to the router's WAN/Internet
port.
> I'm fed up, I'm done with Netgear!
This is primarily a _user_ forum. Tell someone who cares?
antinode wrote:> 2. Refuses to maintain assigned IP to devices.
Well, it's simple, initially when I first (after the rebuilding) I set up a few devices with address res.
It assigned those devices from the DHCP pool, NOT from the reserved IP pool.
Today (not sure how long it has been good) all is good on that.
Generally, it's more helpful to describe actual actions/results,
rather than attribute an attitude to an inanimate device. How, exactly,
does a router "refuse" to do anything? Does it emit an error message
(some place) like "I refuse to do that!"? "fail" and "refuse" are
spelled differently for a reason.
Do you mean that devices with Address Reservations get some wrong
addresses?
> 4. Assigns duplicate IPs constantly.
Initially, it would assign two devices w/same IP.
Today (not sure how long it has been good) all is good on that.
Except, if you look at the jpg I provided in a followup post, it has given it's own IP (not really, I don't think so, but... that's what it reports) to a device.
"constantly" or "repeatedly"?
The most common reason for either of those DHCP problems is the
presence of another DHCP server on the LAN. Firmware defects in Netgear
routers are common enough, but problems like those are seldom caused by
the router.No other DCHP running. I DO have a small (by necessesity, not by choice) wifi plugged in but it's in bridge mode.
Also, there are no devices running hotspot. I know Ring & possibly Wiz have that ability, but have not played w/either for a long while. I really don't want to disable DHCP on the RAX80, unless I can get some quite time for a day or so, to find out if there is another DHCP out there.
For example, occasionally, some Internet-of-Junk gizmo with a
"hotspot" mode might leave its built-in DHCP server running after it's
been configured, and has joined your LAN. A misconfigured Raspberry Pi
computer is another potential culprit. As usual, many things are
possible.
One test would be to disable the DHCP server in the RAX80, and see if
devices still manage to get IP parameters (from some other DHCP server).
> 1. Flaky all the time, losing connection to devices.Well, various devices; TVs, Firesticks, Google Home... will off & on lose connectivity for a bit, and mind you, these devices are NOT moving around to suggest losing signal or strength of.
Not a very detailed description of anything. "connection" between
device and router? "connection" between device and Internet?
> 3. NOT the speed I expected!
The speed is not a real issue, but not super happy or perhaps I had high hopes/expectations.
That's fine for a rant, but not a useful description of anything.
The non-psychics in your audience might know very little about "the
speed [you] expected", or the speed you observed, or how you measured
it.
Other basic useful info would include the router's firmware version,
Firmware Version
V1.0.4.120_1.0.61
and identification of what's connected to the router's WAN/Internet
port.It's a Spectrum Arris TG1682 running at 100Mbps (RAX80 reports 83.36Mbps), I'd like to go faster, but, I also like to buy a fast sports car too, but...
> I'm fed up, I'm done with Netgear!
This is primarily a _user_ forum. Tell someone who cares?
Obiously you don't but, your comments are helpfull for those who DO care and possibly w/my answers to those comments may help resolve my issues. Also, I WAS hoping that it would get to someone who DO care, like Netgear staff.