Reply

R8000 Unable to change IP Address

eboston
Aspirant

R8000 Unable to change IP Address

I just got this router and trying to get it configured for my network.  I use 10.x.x.x/255.0.0.0 for my network.  I was able to change the IP address of the router with my older NightHawk, but every time I try saving the change on the new router, it doesn't stick and goes back to 192.168.1.x.

 

I have been trying to contact support, but the web site is acting stupid today (at least I hope it is just acting up and not normal).  I try the contact support and it flashes up the options, but closes down before I can choose anything.

Model: R8000P|Nighthawk X6S AC4000 Tri Band WiFi Router
Message 1 of 5
antinode
Guru

Re: R8000 Unable to change IP Address

> Model: R8000P|Nighthawk X6S AC4000 Tri Band WiFi Router

 

   Firmware version?

 

> [...] I use 10.x.x.x/255.0.0.0 for my network. [...]

 

   Why?  Why not "255.255.255.0"?  How many millions of devices have
you?  I know nothing, but I'd try a more restrictive subnet mask.

 

> [...] I was able to change the IP address of the router with my older
> NightHawk, [...]

 

   Did that one have a model number and a firmware version?

Message 2 of 5
eboston
Aspirant

Re: R8000 Unable to change IP Address

FW: V1.4.1.42_1.3.4

 

I use different address ranges for different device types.  Helps to keep them organized.

 

Other device was an R7800.  Have no idea what firmware it was.

Message 3 of 5
eboston
Aspirant

Re: R8000 Unable to change IP Address

 I know nothing, but I'd try a more restrictive subnet mask.

 

The problem is the router won't let me do anything but a class C subnet mask.  

Message 4 of 5
antinode
Guru

Re: R8000 Unable to change IP Address

> I use different address ranges for different device types. Helps to
> keep them organized.

 

   I do that, too, but I'm satisfied with small multiples of ten (or
larger multiples of two).

 

> The problem is the router won't let me do anything but a class C
> subnet mask.

 

   I'm not amazed.  It really doesn't have the capacity to deal with
many more than 250 devices.  I've never looked at the software, so I
know nothing, but I can imagine, say, a flat table of DHCP pool
addresses, where 16M entries could waste much more space than 256, so
that restricting the address range might solve many potential problems.

 

   Or, it could be a firmware bug.  But a work-around could be pretty
simple.

Message 5 of 5
Top Contributors
Discussion stats
  • 4 replies
  • 557 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 6E