NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAXE300 AXE7800 Reserve IP addresses
Hello!
1st time, long time!
Details:
1. Brand new (3 days old) RAXE300 Nighthawk Router | Tri-Band WiFi 6E Route : Router Firmware Version V1.0.7.62_1
2. Home setup with Netgear Modem CM1000 (1-2 yrs old) connected to COX high-speed internet: Typical 650-700 Mbps down / 100 Mbps up
3. Router connected to (4 ports in back) 2 netgear switches (8 ports each) and directly to Alexa Fire TV Cube 4k and also to home camera system.
Issue: (yes , you guessed it, that old chestnut) IP Address reservation!
History: go look at these forums, this issue goes back to when Moses wore short pants (Junior Soprano reference there, natch)
Seems to me (based on the NG community forums) that NG doesn't really have a strong IP Reservation game going on.
I've got about 35-40 things attached to my network: tablets, computers, iOT stuff, etc. I tried setting up all to be *reserved* (not static! seems like that's used to define when the address is set on the *device*, not the router). I set my Router to have DHCP 192.168.0.2 thru 192.168.0.99 available, then spent oh an hour or so reserving all my stuff (ok, was re-bingeing narcos at the time).
So at the end of the nite my Advanced: Setup: LAN Setup page looked like I wanted it: A range of devices with addresses from 100 (i.e. 192.168.0.100) to 150. All are in that range, none are outside that range. (Edit: I did all this work from my laptop (HP SPectre 360, connected via ethernet **directly connected** to RAXE300 router)
Now today I get up, look at my LAN setup page, and all's good, just like it was last night. BUT I go to the Advanced: Admin: Attached Devices page and... what what WHAT? 17 of the 36 devices are BACK in the 2-100 range! (the rest are using the addresses I assigned them).
Cmon, NG. Not again.
This AM changed my DHCP range back to default (192.168.0.2 thru 192.168.0.254), reset the computer, no change.
Went thru ipconfig flushdns, reset, renew, re-whatever, re-started computer, no change.
Haven't yet powered down modem and router, will do that now then reply...
OK peeps, hit me. Wtf is going on with NG. I'm thinking they are weak with address reservation, and ....
TL;DR: NG ip address reservation isn't working for me, and apparently not for others for a long time. Little hope for change. Just tell me straight up if I really am expecting too much from this router. It's ok, I can take it. I'd rather not waste more time if I'm just expecting too much.
2 Replies
O_Titus_Media wrote:
I tried setting up all to be *reserved* (not static! seems like that's used to define when the address is set on the *device*, not the router).
There are two different things here.
You can either use Address Reservation on the router, or fix a Static IP Address on the device itself. You seem to be doing both at the same time. Is that correct?
This AM changed my DHCP range back to default (192.168.0.2 thru 192.168.0.254), reset the computer, no change.
Why did you pick 192.168.0.1 rather than the usual default 192.168.1.1?
I am sure you had good reasons for both choices, I ask these questions simply to get to the bottom of what is going on at your end. That may help the real IP experts to cut to the chase.
I've figured out everything, and everything is now awesome!
I got rid of the RAXE300 and jumped ship to ASUS RT-AX86U : got it at BestBuy and this thing ROCKS (for those who enjoy tinkering and having an admin console page that isn't dumbed down, and a DHCP server and reserved address system that lets you do them all at once rather than update after each single entry).
Goodbye Netgear! Hello ASUS!
