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 a GREAT disapointment, GREAT!
Once this gets old or tired, I'm switching to Asus, ANYTHING but Netgear, I'm REALY disapointed!
Here are the reasons and all this is even after rebuilding this thing, totaly from scratch!
1. Flaky all the time, losing connection to devices.
2. Refuses to maintain assigned IP to devices.
3. NOT the speed I expected!
4. Assigns duplicate IPs constantly.
I'm fed up, I'm done with Netgear!
> 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?
12 Replies
Today, no dups and all good on address res.
But Here's the flakiness, again, this is new occurance, never seen this before, see attached jpg.
> 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.
> It assigned those devices [...]
"It"? How did you decide where "those devices" got their addresses?
> No other DCHP running. [...]
You determined this how, exactly?
> 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).Are you reading any of this, or are you just "knowing" things?
> [...] I DO have a small (by necessesity, not by choice) wifi plugged
> in but it's in bridge mode. [...]I don't know what your (unspecified) "a small [...] wifi" might be,
or how it's connected to anything, or how it's configured, or what
"bridge mode" means to you.
> [...] 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.I'd expect the whole test to be done in a few minutes.
> It's a Spectrum Arris TG1682 [...]
"TG1682G"? That seems to be a modem+router, not a simple "modem".
Cascading multiple NAT routers can cause multiple problems.> [...] running at 100Mbps (RAX80 reports 83.36Mbps), [...]
You obtained those speeds how, exactly?
> Obiously you don't [...]
Many things seem to be obvious to you, which are not obvious to me.
For example, you seem to have a TG1682G (modem+router), an RAX80
(router), and some mysterious/unspecified "a small [...] wifi" (possibly
a router). Perhaps _you_ can see how you connected and configured all
those devices, but, with my weak psychic powers, I can't. With all
those routers, each of which could be running a DHCP server, I have no
idea how many independent DHCP servers you might be running where.Based on no actual information, I'd guess that you tied all these
devices together in some confused way, and configured them
inappropriately, leading to a bunch of user-caused problems, for which
you blame the RAX80. Obviously, you know much more about this stuff
than I do, because I couldn't even begin to do blame assignment without
some basic information, including an accurate gizmo inventory, an
accurate and complete description of what's connected to what, and at
least some clues as to how all these gizmos are configured.Regarding what's connected to what...
Hint: If a device has different types of ports, then "connected to
device" is not enough detail. IP networking is more complicated than
stringing together multiple sets of Christmas-tree lights, and requires
more care.
> [...] see attached jpg.Your LAN appears to be badly configured. Presumably, "192.168.1.1"
is a duplicate, at which point all bets are off.Rather than try to make any sense of your existing mess, it might be
more productive to power most of it down, disconnect everything, and
build a non-mess, starting with the TG1682G on its own. I assume that
it provides your ISP connection, and that it's configured as a
modem+router ("gateway").Then, when that works, you might try adding the RAX80, which, if the
TG1682G is configured as a modem+router, should probably be configured
as a wireless access point.Visit http://netgear.com/support , put in your model number, and look
for Documentation. Get the User Manual (at least). Read. Look for
"Set up the router as a WiFi access point". (That should disable _its_
DHCP server.)
Because I know absolutely nothing about your (unspecified) "a small
[...] wifi", or why you want to use it, I wouldn't try to do anything
with it.
Oh, also, I forgot...
The "cheap" wifi I mentioned is a Linksys AC1200.
> One thing to let you know, my writing is not my best suite, being this
> is not my native language, but I do my best.Your English is good enough.
> Well, I setup my Address res. ON the RAX80 and obviously the RAX80 has
> given those IPs to those devices.It's not obvious to _me_. It's especially not obvious if your
devices are getting unexpected or duplicate adresses. And if you have
as many as three different routers (potential DHCP servers) on your LAN.> As I understand it, bridge mode [...]
"Bridge" is a widely misused/misunderstood term. "bridge mode" means
different things to different people, and when applied to different
devices. If you're talking about a router, then you probably mean
configuring it as a wireless access point (WAP). Which would probably
be a good idea. Whether it was done, I don't know.
> [...] has no DHCP, gets it's IPs from the main DHCP server, [...]That sounds like a WAP.
> The "cheap" wifi I mentioned is a Linksys AC1200.
Ok, but I don't know how it's configured or how it's connected. And,
as with Netgear, "AC1200" is a speed, not a model number. Which makes
it difficult when one of us wants to consult its user manual.For all I know, this "Linksys AC1200" might still be using
"192.168.1.1" as its LAN IP address, instead of getting some
new/different IP address using DHCP.> [...] I assumed you were asking about the modem.
I was, but a "TG1682G" is more than a modem; it's a modem+router.
Unless you've configured it as a modem-only. (Which is also known as
"bridge mode", and which is nothing like configuring it as a WAP. As I
said, "widely misused/misunderstood".)
> [...] I've had Netgear probably close to how long you've been alive.
> [...]Not likely. Perhaps you should assume less. About me, about your
DHCP servers, ...> I am a retired computer engineer, [...]
In these forums, people who write poor problem descriptions often
cite their vast experience or expertise. I've never seen such claims
improve their problem descriptions.> Rather than try to make any sense of your existing mess, [...]
That's still my advice.
