Netgear Nighthawk RS700S Subnet Settings

Netgear Nighthawk RS700S Subnet Settings Guide

The Netgear Nighthawk RS700S is a flagship Wi-Fi 7 router with a 2.5 Gbps WAN port and 19 Gbps aggregate wireless throughput. Its default LAN subnet is 192.168.1.0/24, the most common home router default. For homelab users who connect the RS700S to a managed switch or NAS, changing the subnet to 10.0.0.0/24 or similar private range distinguishes it from ISP modem networks at a glance, which is useful when managing multiple VLANs or running split-DNS for internal hostnames.

Specifications¹

Default subnet configuration

The RS700S defaults to 192.168.1.0/24², a /24 block providing 253 usable DHCP addresses. Most household networks never fill a /24, but the router's WAN 2.5G port and LAN 2.5G ports make it attractive for homelab setups where servers, NAS units, and workstations need separate VLANs for storage traffic isolation. Building on this, the standard DHCP pool 192.168.1.2 through 192.168.1.254 leaves .1 for the router and does not reserve a static range for servers, so adjusting the pool to 192.168.1.100 through 192.168.1.254 frees 192.168.1.2 through 192.168.1.99 for static server assignments without DHCP conflicts.

Planning a static versus dynamic split

Reserving the bottom of the subnet for static assignments is a common convention because it keeps infrastructure addresses clustered and easy to document. A NAS at 192.168.1.10, a Proxmox host at 192.168.1.20, and a TrueNAS instance at 192.168.1.30 all sit below the DHCP range and never collide with dynamic leases. This convention also simplifies firewall rules on the router, since you can write rules that reference the entire static range rather than individual addresses.

Netgear's own configuration guide labels these as the Starting IP Address and Ending IP Address fields under Advanced > Setup > LAN Setup, and both values must fall within the same subnet as the router itself. This constraint is why the static-versus-dynamic split has to happen inside the /24 rather than by carving out a separate subnet for infrastructure devices: the DHCP pool boundaries can only be moved within 192.168.1.2 through 192.168.1.254, not redirected to an entirely different address range.

Changing subnet settings on the RS700S

Open a browser and navigate to http://routerlogin.net or http://192.168.1.1. Log in with your admin credentials. Go to Advanced > Setup > LAN Setup. The IP Address field shows the router's current LAN IP and the Subnet Mask field shows 255.255.255.0. Change these to your desired values, for example 10.0.0.1 with 255.255.0.0 for a /16, and then scroll down to the DHCP pool section to update the start and end IPs to match the new subnet range. Click Apply and the router reboots the DHCP service so devices must renew their leases.

Locking devices to a fixed address with DHCP reservations

Static DHCP reservations are configured on the same LAN Setup page by binding a device's MAC address to a fixed IP. This is preferable to configuring a static IP on the device itself because the reservation stays consistent even if you replace the device's network card or reinstall its operating system, and it keeps all address management in one place on the router.

Multi-subnet and VLAN patterns

The RS700S provides a guest wireless network that runs in an isolated segment, restricting guest clients from accessing the main LAN. For multi-VLAN homelab setups, the RS700S connects to a managed switch that tags traffic with IEEE 802.1Q VLAN IDs. Each VLAN maps to a subnet: management VLAN at 10.0.0.0/24, storage VLAN at 10.0.1.0/24, IoT VLAN at 10.0.2.0/24.

Deciding where inter-VLAN routing happens

The RS700S performs inter-VLAN routing if configured with VLAN subinterfaces, or a dedicated firewall handles routing if the RS700S is used only as a wireless access point in this topology. CapyToolkit's subnet calculator helps pre-plan CIDR allocations for each VLAN before configuring the managed switch, ensuring non-overlapping ranges and a clean per-VLAN DHCP setup. Deciding up front whether the RS700S or an upstream firewall routes between VLANs determines how you configure the trunk port on the managed switch.

Static IP planning for homelab servers and NAS devices

Homelab setups with the RS700S benefit from a clean split between dynamic and static address ranges. Reserving 192.168.1.2 through 192.168.1.99 for static assignments and 192.168.1.100 through 192.168.1.254 for DHCP prevents address conflicts when adding new servers. A NAS at 192.168.1.10, a Proxmox host at 192.168.1.20, and a TrueNAS instance at 192.168.1.30 keep infrastructure addresses clustered at the bottom of the subnet for easy documentation. Building on this, the RS700S DHCP pool configuration at Advanced > Setup > LAN Setup lets you set the start address to 192.168.1.100, automatically skipping the static range. Changing this pool boundary after initial setup requires only one configuration change rather than individual device reconfiguration.

IPv6 prefix delegation and LAN configuration on the RS700S

The RS700S supports DHCPv6-PD (Prefix Delegation) on the WAN side.³ When the ISP delegates a /56 or /60 prefix, the router assigns a /64 from that delegation to the LAN. Enabling IPv6 at Advanced > Advanced Setup > IPv6 assigns LAN hosts their addresses through SLAAC, DHCPv6, or both simultaneously. Building on this, the RS700S displays the current WAN IPv6 prefix and LAN IPv6 prefix in the same IPv6 settings page. If your ISP delegates a /56 (for example 2001:db8:abcd::/56), the router assigns 2001:db8:abcd:0001::/64 to the LAN, leaving 254 additional /64s available for VLANs. Without VLAN support on the RS700S LAN, the single /64 serves all devices, which is sufficient for most home deployments. CapyToolkit shows the /64 boundaries when you enter the delegated prefix, helping you plan multi-VLAN IPv6 if you add a managed switch.

Using the RS700S in AP mode behind a dedicated gateway

Switching the RS700S to AP mode (Advanced > Advanced Setup > Router/AP Mode > AP Mode) disables its NAT and DHCP server, turning the device into a pure wireless access point. Your upstream gateway : pfSense, OPNsense, or a UDM Pro : handles all routing, subnet assignment, and firewall rules. Building on this, AP mode is the correct deployment choice when you run a multi-VLAN setup: the upstream gateway assigns VLAN-backed subnets with 802.1Q trunking to a managed switch, and the RS700S provides Wi-Fi on whichever VLAN the switch port is configured for.

The routerlogin.net admin interface remains accessible at the static IP you assign in AP mode (typically a management VLAN address). All Wi-Fi settings, band steering, and mesh features continue to work; only routing functions are disabled. Before flipping the RS700S to AP mode, map each VLAN to a subnet on the Nighthawk RS700S so the upstream gateway inherits clean CIDR boundaries.