NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

determs's avatar
determs
Aspirant
Mar 16, 2021

Static IP Address Not working on Satellites

I have a RBR50 [2.7.2.104] which has 4 satellites (RBS50x2 [2.7.2.104], RBW30x2 [2.6.2.2]).  In order to help with supporting my routers I have set static IP addresses for satellites.  

 

After the last upgrade all of my static IP address failed to work (showed as disconnected in the admin console) and all of my satellites would not connect to the router.  The only fix I had was to remove the static routes and let DHCP (set by the router) reset new IP addresses for all my satellites.

 

Has anyone else had this problem?  I would really like static routes on my routers.  The weird thing is that I do have one additional static route and that is for my printer.  Which had no issues and kept it's static route.

3 Replies

  • One thing I was wondering, maybe it was self-inflected?  The static routes I had setup were part of the DHCP range...would that have created this issue?  The printer didn't have problems, which is why I'm now wondering about my latest theroy.

     

    • antinode's avatar
      antinode
      Guru

      > [...] I have set static IP addresses for satellites. [...]

       

         Real static addresses, not reserved dynamic addresses?  Why?
      Especially for a device like a satellite, which would be approximately
      useless without the main router (and its DHCP server) working.  Why buy
      trouble?

       

      > [...] The static routes I had setup were part of the DHCP
      > range...would that have created this issue? [...]

       

         "static route" and "static IP address" are spelled differently for a
      reason.

       

         Manually handing out addresses from the DHCP pool could certainly
      cause problems.  If you really want to use static addresses, then shrink
      the DHCP pool, and use only ex-pool addresses for those static
      addresses.

       

      > The printer didn't have problems, [...]

       

         Some of us non-psychics can't see any of your IP addresses, which
      makes it tough to guess which devices might be affected first.