NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
omalmals
May 29, 2022Follower
R8000
I had this working for years, but a recent power failure fried my modem
and cleared my router so I had to start over from scratch. I am using a
Netgear Nighthawk X6 R8000 v1.0.4.84_10.1.84 wired to a TDS T3200M modem/router
which goes out to the internet using DSL, we have good speeds
150mbps. I'm thinking I may have something either disabled or not
disabled that should be. Pages will for a couple of seconds show the
"site can't be reached" error, then load just fine. Obviously this slows
everything down. Here are my settings:
Netgear R8000: static IP 192.168.0.2, 255 255 255 0, gatewayIP:
192.168.0.1 DNS server: 192.168.0.1
DHCP enabled 192.168.1.2 to 192.168.1.254 subnet 255.255.255.0
Router Lan IP 192.168.1.2 255.255.255.0
TDS router/modem: wifi off, bridge mode, DMZ disabled....external IP
184.x.x.x 255.255.252.0, Ports forwarded: 192.168.0.2 port 88 (for Blue
Iris for my webcams)....DHCP reservation 192.168.0.2 for the Netgear,
(uses MAC addr) to 192.168.0.2
DHCP enabled 192.168.0.0 to 192.168.0.254 subnet 255.255.255.0
I had a horrible time getting the IP's set up - kept getting errors making a
static IP on my computers (still can't and don't know why) - it would say
not in the same network and windows would put it back to dynamic. (HP
& Acer laptops with windows 8.1,). All of my devices are in the
192.168.1.x subnet and connected to the Netgear and seem to be
working ok with this config. Several are static (like the webcams). I finally
got my cameras to work and wireless to work with this config (but I'm not
sure it's right). Before it would be cameras OR internet, not both but
somehow I fixed it (not sure what I did). But I still have this lag problem.
Should I turn off DHCP somewhere? Turn something else on? Are my IP
configs OK? I have about 25 devices connected to the Netgear -
several being static IP cameras. Thanks in advance for any guidance for
suggestions.
2 Replies
- SmallTraderApprentice
The problems that you described are due to Netgear's infamous firmware bugs across many models. It is worth noting Netgear of today is not the same as the Netgear of yesteryears. Netgear Firmwares are full of bugs and render devices unstable or unusable. Fixes are not forth coming despite being reported long time ago by multiple users.A quick search on this forum and you can easily see the history of firmware problems across multiple models.
On the R8000, this DNS related bug was first reported over a year ago.There are really two options available
(1) Downgrade firmware to V.68
(2) Move away from Netgear devices as Netgear basically could not care less of its products or its customers.
There are some reports that enabling IPv6 is a workaround which may or may not be a viable/practical workaround for people.
- FURRYe38Guru - Experienced User
Your ISP Modem already has a built in router and wifi. This would be a double NAT (two router) condition which isn't recommended. https://kb.netgear.com/30186/What-is-Double-NAT
https://kb.netgear.com/30187/How-to-fix-issues-with-Double-NATCouple of options,
1. Configure the modem for transparent bridge or modem only mode. Then use the NG router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ/ExposedHost or IP Pass-Through for the IP address the NG router gets from the modem. https://kb.netgear.com/25891/DMZ-on-NETGEAR-routers
https://kb.netgear.com/24086/How-do-I-set-up-a-default-DMZ-server-on-my-Nighthawk-router
3. Or disable all wifi radios on the modem and connect the NG router to the modem, LAN to LAN configure AP mode on the NG router.
https://kb.netgear.com/24104/How-do-I-change-my-Nighthawk-router-to-AP-mode-after-I-ve-already-run-setupTry option #2 first.
If your using a static IP address of 192.168.0.2 on the WAN side for the NG router, your ISP modem IS NOT bridged.
Try using a default IP address pool size of 192.168.1.100 to .200 on the R8000 router.
Also try enabling IPv6 on the router.
I've had no problems using current version of FW on my R8000 router.
omalmals wrote:
I had this working for years, but a recent power failure fried my modem
and cleared my router so I had to start over from scratch. I am using a
Netgear Nighthawk X6 R8000 v1.0.4.84_10.1.84 wired to a TDS T3200M modem/router
which goes out to the internet using DSL, we have good speeds
150mbps. I'm thinking I may have something either disabled or not
disabled that should be. Pages will for a couple of seconds show the
"site can't be reached" error, then load just fine. Obviously this slows
everything down. Here are my settings:Netgear R8000: static IP 192.168.0.2, 255 255 255 0, gatewayIP:
192.168.0.1 DNS server: 192.168.0.1DHCP enabled 192.168.1.2 to 192.168.1.254 subnet 255.255.255.0
Router Lan IP 192.168.1.2 255.255.255.0
TDS router/modem: wifi off, bridge mode, DMZ disabled....external IP
184.x.x.x 255.255.252.0, Ports forwarded: 192.168.0.2 port 88 (for Blue
Iris for my webcams)....DHCP reservation 192.168.0.2 for the Netgear,
(uses MAC addr) to 192.168.0.2
DHCP enabled 192.168.0.0 to 192.168.0.254 subnet 255.255.255.0I had a horrible time getting the IP's set up - kept getting errors making a
static IP on my computers (still can't and don't know why) - it would say
not in the same network and windows would put it back to dynamic. (HP
& Acer laptops with windows 8.1,). All of my devices are in the
192.168.1.x subnet and connected to the Netgear and seem to be
working ok with this config. Several are static (like the webcams). I finally
got my cameras to work and wireless to work with this config (but I'm not
sure it's right). Before it would be cameras OR internet, not both but
somehow I fixed it (not sure what I did). But I still have this lag problem.
Should I turn off DHCP somewhere? Turn something else on? Are my IP
configs OK? I have about 25 devices connected to the Netgear -
several being static IP cameras. Thanks in advance for any guidance for
suggestions.