NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 Router continually reassigning IP addresses to the satellites.
PROBLEM My router will fall into a pattern of continually re-assigning IP addresses to the satellites. Devices connected to those satellites wind up losing their connection and then getting their ...
Thank you for the details. Will be sure to have NG review this.
LOGS FOR VARIOUS CONFIGURATIONS
Below are the logs corresponding to the network in several configurations.
Time goes from bottom to top. Under each section is the configuration.
Twice below I run the network with no RBS, a configuration in which there still does seem to be a tendency to repeatedly hand out ip's to devices. However, I don't know how normal the behavior is there. I don't have anything to compare it to. I'm assuming that a router should hand out an IP once and be done with it for a set number of hours.
With a single RBS hardwired to the RBR, the RBR still hands out IPs repeatedly to the RBS, and devices attached to that RBS lose connectivity. This problem makes the network unusable, and shows that I can't even use an ethernet back-haul as a workaround. It seems to me that this data also rules out interference on wifi as the problem.
The people on my network need an unbroken connection for their jobs, so I think I've reached the end of the road with this system.
The logs are below, and afterwards there's an updated summary of the problem.
If there's ever a real diagnosis of what's going on please let me know.
[DHCP IP: (192.168.1.12)] to MAC address [device 1], Saturday, Aug 20,2022 18:45:33
[DHCP IP: (192.168.1.6)] to MAC address [device 2], Saturday, Aug 20,2022 18:45:27
[DHCP IP: (192.168.1.23)] to MAC address [device 3], Saturday, Aug 20,2022 18:24:08
[DHCP IP: (192.168.1.23)] to MAC address [device 3], Saturday, Aug 20,2022 18:01:11
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Saturday, Aug 20,2022 17:16:28
[DHCP IP: (192.168.1.29)] to MAC address [device 5], Saturday, Aug 20,2022 17:13:25
[DHCP IP: (192.168.1.16)] to MAC address [device 6], Saturday, Aug 20,2022 17:12:54
[DHCP IP: (192.168.1.16)] to MAC address [device 6], Saturday, Aug 20,2022 16:52:57
[DHCP IP: (192.168.1.16)] to MAC address [device 6], Saturday, Aug 20,2022 16:51:00
[DHCP IP: (192.168.1.29)] to MAC address [device 5], Saturday, Aug 20,2022 16:38:47
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Saturday, Aug 20,2022 15:56:57
[DHCP IP: (192.168.1.13)] to MAC address [device 8], Saturday, Aug 20,2022 14:57:14
Above: Network is one RBR, no RBS again.
(14:44 router time)
[DHCP IP: (192.168.1.18)] to MAC address [device 9], Saturday, Aug 20,2022 14:41:35
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Saturday, Aug 20,2022 14:40:46
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 14:27:48
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 14:27:36
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 14:24:19
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 14:23:57
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 14:23:45
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Saturday, Aug 20,2022 14:22:02
[DHCP IP: (192.168.1.19)] to MAC address [device 11], Saturday, Aug 20,2022 14:20:58
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 14:19:17
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 14:19:05
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Saturday, Aug 20,2022 14:07:55
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 13:57:16
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 13:57:05
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Saturday, Aug 20,2022 12:34:56
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Saturday, Aug 20,2022 12:34:03
[DHCP IP: (192.168.1.16)] to MAC address [device 6], Saturday, Aug 20,2022 12:23:36
[DHCP IP: (192.168.1.16)] to MAC address [device 6], Saturday, Aug 20,2022 12:22:24
[DHCP IP: (192.168.1.18)] to MAC address [device 9], Saturday, Aug 20,2022 12:16:10
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 12:15:54
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 12:15:44
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 11:59:45
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 11:59:33
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Saturday, Aug 20,2022 11:52:39
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Saturday, Aug 20,2022 11:52:07
.
.
.
[DHCP IP: (192.168.1.30)] to MAC address [device 12], Friday, Aug 19,2022 21:48:35
[DHCP IP: (192.168.1.26)] to MAC address [device 13], Friday, Aug 19,2022 21:29:34
[DHCP IP: (192.168.1.12)] to MAC address [device 1], Friday, Aug 19,2022 20:39:03
[DHCP IP: (192.168.1.25)] to MAC address [device 14], Friday, Aug 19,2022 20:38:41
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 20:38:10
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 20:37:58
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 20:37:47
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 20:36:51
Above: Network is one RBR, one RBS [RBS 2] connected via wifi
[DHCP IP: (192.168.1.6)] to MAC address [device 2], Friday, Aug 19,2022 20:31:23
[DHCP IP: (192.168.1.12)] to MAC address [device 1], Friday, Aug 19,2022 20:31:09
[DHCP IP: (192.168.1.24)] to MAC address [device 15], Friday, Aug 19,2022 20:13:10
[DHCP IP: (192.168.1.23)] to MAC address [device 3], Friday, Aug 19,2022 18:35:08
[DHCP IP: (192.168.1.23)] to MAC address [device 3], Friday, Aug 19,2022 18:27:08
[DHCP IP: (192.168.1.25)] to MAC address [device 14], Friday, Aug 19,2022 17:53:54
[DHCP IP: (192.168.1.20)] to MAC address [device 16], Friday, Aug 19,2022 17:46:26
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Friday, Aug 19,2022 17:39:47
[DHCP IP: (192.168.1.16)] to MAC address [device 6], Friday, Aug 19,2022 17:13:44
[DHCP IP: (192.168.1.23)] to MAC address [device 3], Friday, Aug 19,2022 16:51:03
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 16:45:45
[DHCP IP: (192.168.1.18)] to MAC address [device 9], Friday, Aug 19,2022 16:43:58
[DHCP IP: (192.168.1.23)] to MAC address [device 3], Friday, Aug 19,2022 16:24:50
[DHCP IP: (192.168.1.26)] to MAC address [device 13], Friday, Aug 19,2022 15:57:00
[DHCP IP: (192.168.1.19)] to MAC address [device 11], Friday, Aug 19,2022 15:18:32
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Friday, Aug 19,2022 15:07:57
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Friday, Aug 19,2022 15:04:02
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Friday, Aug 19,2022 14:57:53
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Friday, Aug 19,2022 14:43:50
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Friday, Aug 19,2022 14:08:52
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Friday, Aug 19,2022 13:51:48
Above: Network has 1 RBR 0 RBS
killed both satellites at 13:51 (router time),
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Friday, Aug 19,2022 13:21:57
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Friday, Aug 19,2022 12:59:27
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 12:58:52
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 12:23:45
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 12:20:35
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:20:32
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:20:13
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:20:00
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:17:53
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:17:30
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:17:20
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 12:17:19
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:17:17
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:15:14
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:14:51
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:14:40
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:07:39
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:07:22
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:07:10
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:05:00
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:04:36
[DHCP IP: (192.168.1.18)] to MAC address [device 9], Friday, Aug 19,2022 12:04:33
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 12:04:30
[DHCP IP: (192.168.1.23)] to MAC address [device 3], Friday, Aug 19,2022 11:58:11
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 11:35:12
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 11:26:20
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Friday, Aug 19,2022 11:23:34
Above: Network now has one RBR, one hardwired RBS [RBS 1],
killed RBS that was connected via WIFI at 11:23 (router time),
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 11:09:01
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Friday, Aug 19,2022 11:01:32
[DHCP IP: (192.168.1.12)] to MAC address [device 1], Friday, Aug 19,2022 10:53:57
[DHCP IP: (192.168.1.6)] to MAC address [device 2], Friday, Aug 19,2022 10:46:08
[DHCP IP: (192.168.1.6)] to MAC address [device 2], Friday, Aug 19,2022 10:43:03
[DHCP IP: (192.168.1.21)] to MAC address [device 4], Friday, Aug 19,2022 10:40:19
[DHCP IP: (192.168.1.14)] to MAC address [device 17], Friday, Aug 19,2022 10:38:29
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 10:37:35
[DHCP IP: (192.168.1.12)] to MAC address [device 1], Friday, Aug 19,2022 10:22:58
[DHCP IP: (192.168.1.12)] to MAC address [device 1], Friday, Aug 19,2022 10:19:24
[DHCP IP: (192.168.1.22)] to MAC address [device 10], Friday, Aug 19,2022 10:17:27
[DHCP IP: (192.168.1.6)] to MAC address [device 2], Friday, Aug 19,2022 10:11:08
[DHCP IP: (192.168.1.12)] to MAC address [device 1], Friday, Aug 19,2022 10:08:10
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 10:01:07
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 10:01:05
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 10:01:03
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 10:01:02
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 10:01:01
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 10:00:59
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 10:00:58
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 10:00:58
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 10:00:57
[DHCP IP: (192.168.1.17)] to MAC address [device 7], Friday, Aug 19,2022 10:00:57
[DHCP IP: (192.168.1.102)] to MAC address [RBS 2], Friday, Aug 19,2022 10:00:55
[DHCP IP: (192.168.1.101)] to MAC address [RBS 1], Friday, Aug 19,2022 10:00:55
Above, Network has
one RBR,
one RBS hardwired [RBS 1]
one RBS wifi [RBS 2]
***************END LOG
PROBLEM
My router will fall into a pattern of continually assigning IP addresses to the satellites.
Devices connected to those satellites get disconnected.
HARDWARE
- Model RBK853-100NAS,
- 1 router RBR850,
- 2 satellites RBS850
- Firmware: V4.6.8.5_2.1.9
- RBR850 is connected to the internet via ethernet to FIOS ONT box.
- Satellites are connected to router wirelessly.
PROBLEMS RULED OUT
- The problem is not related to our ISP, as I happen to have switched ISP’s recently. And problem still crops up sometimes.
- problem is not with the supply of power to the router because the log does not show rebooting. Also you’d expect to see more devices reinitializing rather than just one.
- problem is note power to satellites because they always ask for their ip’s together.
- Problem is not custom settings on router, I’ve reset the router to factory twice and problem still crops up.
- Problem is not firmware: has been updated.
- Problem is not IP conflicts. No conflicts listed on router. Problem happens regardless of IPs being reserved or not.
- Problem is not WIFI signal strength of router at the satellites
- backhaul always ‘good’ and running at 5Ghz
- orbi’s always glow ‘blue’ signaling good connectivity with router
- problem happens regardless of signal strength of router at sats i
- -45db has problem
- -65db > to > -60db still has problem.
- moving satellite near router doesn’t help.
- Problem probably is not RF interference.
- ran microwave and other possible causes, problem did not happen.
- moving satellite right next to router didn’t help.
- unplugged antenna from a PD machine
- Problem is not that I had a uniquely broken bit of netgear hardware
- replaced the hardware.
- problem is not wifi interference
- I hardwired one satellite to the router and turned the other off, and the router still hands out ip over and over to the satellite.
- problem is not DFS channels
COULD STILL BE
- universal problem with netgear’s hardware. or bad batch.
STUFF I’VE TRIED
- Switched ISP from xfinity to verizon fios.
- Replacing both satellites and the Router
- Reset to factory
- Checking wifi signal strength
- Moving Satellite next to router
- Looking for causes of temporary RF interference: microwaves, printers, lighting etc.
- Updating Firmware on all units (From V4.6.8.2_2.1.9 to V4.6.8.5_2.1.9) manually.
- Reserving IPs for satellites
- Power cycling
- resyncing
- discussing problem with netgear and following their advice.
- unplugging the antenna on a piece of medical equipment
- changing the channels used for wifi
- verified that i’m not using DFS channels.
- moved satellites so that signal from router was between -65db and -60db. not to close and not too far. (recommended by geek squad).
- hardwiring one router to satellite
- one sat hardwired, the other on wifi.
- router only, no satellites.
chewywater wrote:
Twice below I run the network with no RBS, a configuration in which there still does seem to be a tendency to repeatedly hand out ip's to devices. However, I don't know how normal the behavior is there. I don't have anything to compare it to. I'm assuming that a router should hand out an IP once and be done with it for a set number of hours
(I hesitated before posting because I have no clear solution.....)
Routers with DHCP server functionality (almost all consumer routers) do not "hand out" IP addresses. They respond to requests. The default DHCP lease on Orbi routers is one day (86,400 seconds). Following the internet standards for DHCP (https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol ) devices ask to renew the IP lease when half of the time remains (12 hours). So, normal behavior is to see a log entry every 12 hours for each device, including satellites. It does not matter whether the satellites have 'reserved' IP addresses in the LAN Setup table. They are not aware of the reservation. They ask: they receive. Just like every other device on the network. So the statement above is correct. The router should hand out an IP once and be done with it for 12 hours.
For user devices, it is not all that difficult to capture the DHCP process, either by enabling "LAN/WAN Packet Capture" on the debug page, or by "sniffing" the connection. This is how I discovered that a Lenovo laptop was not connecting to the internet when I opened the lid. It kept asking, "Can I have an IP?" The Orbi kept answering, "Use this one." and the laptop just kept asking over and over. (Until a software update on the laptop fixed the problem I had to open the Network Troubleshooting Wizard or disable/enable the Ethernet adapter. Royal pain in the *certain place*.)
Satellites are a mystery. I rather doubt that the DHCP communication for satellites can be captured easily. If the router-satellite link is over Ethernet, then one could "sniff" on the link and record actual packets to see when the satellite requests and the router responds. If the satellite backhaul is over WiFi, that link is encrypted, and much more difficult to sniff.
(Back to confession...)
If this situation has persisted despite:
- swapping the entire network
- removing all satellites
My guess is that there is some device on the network that is causing trouble that prompts a lot of devices to do DHCP requests.
CrimpOn wrote:My guess is that there is some device on the network that is causing trouble that prompts a lot of devices to do DHCP requests.
Good idea, since we're grasping at straws here to understand why the OP's 850 is logging all this DHCP activity whereas other 850 owners are not seeing the same.
OP, do you have any devices configured with static IPs (not DHCP reserved addresses configured via the Orbi admin GUI)? Any unusual network devices or switches in your home network?
Can you list us all brand and model # devices that your seeing this IP address issue with? I see you reported the RBS as well. Please list other brands and model devices as well.
Thank you.Thanks for the input folks. I'll try to look this stuff over and respond in the next few days. I'm a little strapped for time at the moment.
I will reply below to individual questions, however I thought I'd put my general questions here first:1.
If I hire someone to diagnose/fix my network, what tools and skills should they have? Packet sniffing has been mentioned. I assume a spectrum analyzer might be helpful (even though I'm pretty sure wifi has been ruled out). Is there anything else I should expect of a residential IT expert?2.
Can power/voltage fluctuations cause these tyeps of symptoms? I have the router plugged into a surge protector, but the other two are plugged into the wall. Do the AC/DC adapters correct for minor fluctuations in voltage?
FURRYe38 wrote:Can you list us all brand and model # devices that your seeing this IP address issue with? I see you reported the RBS as well. Please list other brands and model devices as well.
Thank you.I don't have the time to determine the make of every device right now, but below is a rough list I made to give you an idea of the problem. I took samples of logs over the course of 4 or 5 days, and then listed the number of DHCP renewals for each device.
Almost every device on the network has a problem with series of renewals for no reason, but the satellites are by far the worst offender. (note I replaced the old RBR and 2 RBS's with a new set during this time period)
The only device that doesn't have a problem is a printer which has its IP set statically on the printer, and set as reserved DHCP on the router.device has ip problemstotal DHCP entries in collected logshardware type device name old satellite rbs850 yes 574 old satellite rbs850 Yes 555 macbook macbook yes. lots- now gone from network, didn't help 391 new satellite rbs850 yes 197 new satellite rbs850 yes 154 ??? ?? YES, this is in the earliest logs, constant issues 139 laptop work-laptop YES. lots probs with ip reassignment
but seem to always come after a string of satellite reassignments135 tv according to router yes seems to happen after satellites are going nuts 103 iphone yes happens, not super long trains though 72 apple according to router yes 59 iphone y 55 yes - short doubles and stuff 48 smartphone samsung-phone more than there should be but not a ton 44 apple in basement according to router yes 41 desktop ursa big trains of reassignments 31 tv firestick amazon family room sometimes one or two in a row 30 desktop rigel mayby not, no continuous rows. 18 tv tv roku basement guest room noi? nothing continuous 16 laptop google chromebook - heather yes has multiple reassignments 15 tv tv blue ray does happen here and there 12 laptop old-laptop 0 matches 0 printer HP printer no 0 tv tv basement unknown 0
Mikey94025 wrote: OP, do you have any devices configured with static IPs (not DHCP reserved addresses configured via the Orbi admin GUI)? Any unusual network devices or switches in your home network?DHCP range is from 2-254, there is no range for static devices on router.
However I do have a printer whose IP is set staticly on the device, and then has a reserved DHCP IP on the router.
This printer doesn't seem to have the problem with repeated IP renewals.
Note that removing this printer from the network doesn't solve the problems with IP renewals.There are no other network-devices on the network, just 2 RBS and 1 RBR.
@CrimpOn wrote
My guess is that there is some device on the network that is causing trouble that prompts a lot of devices to do DHCP requests.Thanks for the info on DHCP and sniffing/DHCP capture.
Regarding your hypothesis that some device on the network may be causing trouble that prompts a lot of devices to do DHCP requests: I suppose I could test this by turning off wifi and hardwiring the RBSs to the RBR. If the RBS's continue to renew DHCP IPs for no reason, then I could rule out any problems with other devices. Is there a way to turn off wifi on RBR/RBS? Or if there is another way of removing all devices please let me know. I suppose I could block them all temporarily but i'm not sure if this would have the desired effect. Or walk around turning off devices, but that's would be a pain, especially if I wanted to rerun the experiment.
chewywater wrote:
DHCP range is from 2-254, there is no range for static devices on router.
However I do have a printer whose IP is set staticly on the device, and then has a reserved DHCP IP on the router.(Perhaps others can confirm) My impression is that it is good practice to keep statically assigned IP addresses separate from the DHCP range. At least, that's what I do.
chewywater wrote:
Can power/voltage fluctuations cause these tyeps of symptoms? I have the router plugged into a surge protector, but the other two are plugged into the wall. Do the AC/DC adapters correct for minor fluctuations in voltage?
Yes, my understanding is that the power adapters accept varying voltage and output a constant voltage. My own practice is to use small UPS units to power network devices. (Mostly because of the havoc caused by restarts after very short power outages.)
We believe this a handling by the FW with devices. Something that is being looked into currently.
chewywater wrote:
I will reply below to individual questions, however I thought I'd put my general questions here first:1.
If I hire someone to diagnose/fix my network, what tools and skills should they have? Packet sniffing has been mentioned. I assume a spectrum analyzer might be helpful (even though I'm pretty sure wifi has been ruled out). Is there anything else I should expect of a residential IT expert?2.
Can power/voltage fluctuations cause these tyeps of symptoms? I have the router plugged into a surge protector, but the other two are plugged into the wall. Do the AC/DC adapters correct for minor fluctuations in voltage?
CrimpOn wrote:
chewywater wrote:
DHCP range is from 2-254, there is no range for static devices on router.
However I do have a printer whose IP is set staticly on the device, and then has a reserved DHCP IP on the router.(Perhaps others can confirm) My impression is that it is good practice to keep statically assigned IP addresses separate from the DHCP range. At least, that's what I do.
Agreed. I've just been resetting the router so much that it was easier to just reserve the ip for now. Regardless, the static printer is not the issue causing problems, as disconnecting the printer from the network does not stop the issues with constant DHCP renewal of the RBS's.
CrimpOn wrote:
chewywater wrote:Can power/voltage fluctuations cause these tyeps of symptoms? I have the router plugged into a surge protector, but the other two are plugged into the wall. Do the AC/DC adapters correct for minor fluctuations in voltage?
Yes, my understanding is that the power adapters accept varying voltage and output a constant voltage. My own practice is to use small UPS units to power network devices. (Mostly because of the havoc caused by restarts after very short power outages.)
I don't think I have actual restarts happening. Although I'm not sure how to rule this out. Do restarts of the RBS's show up in the log?
Note I haven't had time to go learn to read the debug log yet.
FURRYe38 wrote:We believe this a handling by the FW with devices. Something that is being looked into currently.
chewywater wrote:
I will reply below to individual questions, however I thought I'd put my general questions here first:1.
If I hire someone to diagnose/fix my network, what tools and skills should they have? Packet sniffing has been mentioned. I assume a spectrum analyzer might be helpful (even though I'm pretty sure wifi has been ruled out). Is there anything else I should expect of a residential IT expert?2.
Can power/voltage fluctuations cause these tyeps of symptoms? I have the router plugged into a surge protector, but the other two are plugged into the wall. Do the AC/DC adapters correct for minor fluctuations in voltage?By FW I assume you mean firewall? Please let me know if there is a workaround for the problem. I appreciate any feedback you can give me. Thanks.
chewywater wrote:
DHCP range is from 2-254, there is no range for static devices on router.
Sorry I did not realize the implication of this statement earlier.
Yes, there is no provision to state a range for static (or assigned) devices. That is implied by what is "left over" after the DHCP range is defined. For example, if the DHCP range is set to 71-100, then IPs from 2-70 and from 101 to 254 are where IP assignments would be made.
chewywater wrote:
By FW I assume you mean firewall? Please let me know if there is a workaround for the problem. I appreciate any feedback you can give me. Thanks.
FW = Firmware.
Have you updated to v.11 yet?
chewywater wrote:
STUFF I’VE TRIED
- Switched ISP from xfinity to verizon fios.
- Replacing both satellites and the Router
- Reset to factory
- Checking wifi signal strength
- Moving Satellite next to router
- Looking for causes of temporary RF interference: microwaves, printers, lighting etc.
- Updating Firmware on all units (From V4.6.8.2_2.1.9 to V4.6.8.5_2.1.9) manually.
- Reserving IPs for satellites
- Power cycling
- resyncing
- discussing problem with netgear and following their advice.
- unplugging the antenna on a piece of medical equipment
- changing the channels used for wifi
- verified that i’m not using DFS channels.
- moved satellites so that signal from router was between -65db and -60db. not to close and not too far. (recommended by geek squad).
- hardwiring one router to satellite
- one sat hardwired, the other on wifi.
- router only, no satellites.
FURRYe38 wrote:Have you updated to v.11 yet?
The last version I tried was V4.6.8.5
I will try moving to version 11 this weekend.
Is there any reason to believe that the problem I'm having has been fixed in the latest version?
thanks
I believe were still tracking this issue even in v.11.
I've got my 8 series online and it's been working well on v.11.
Email logging is no longer needed to avoid mysterious reboots.
