When configuring the settings of the router user must be familiar with the technical aspects of that particular settings, otherwise incorrect settings can lead to instability.

LAN Settings

1. Assign the LAN IP address

User should assign non default IPv4 address to the router because it avoid IP address conflicts in muti-router setup.

LAN IP

• Description: The LAN IP is the router’s IP address on the local network. It serves as:
  • The default gateway for devices to route traffic to the internet.
  • The DNS server (if Advertise router’s IP in addition to user-specified DNS is enabled, as discussed previously).
  • The address used to access the Web GUI (e.g., 192.168.1.1 or http://router.asus.com).
• Default Value: Typically 192.168.1.1 or 192.168.50.1 (varies by model, e.g., ZenWiFi AX uses 192.168.50.1).
• Use Case: Changing the LAN IP is useful to avoid conflicts in multi-router setups or to align with an existing network’s IP scheme (e.g., 192.168.55.1).

Configuration:

1. Log in to the Web GUI (http://router.asus.com or the current LAN IP).
2. Go to Advanced Settings > LAN > LAN IP.
3. In the IP Address field, enter a new IP (e.g., 192.168.55.1).
   • Use a private IP range (e.g., 192.168.x.x)
   • Avoid conflicts with the WAN IP or other routers in the network.
4. Click Apply. The router may reboot, and you’ll need to access the Web GUI using the new IP (e.g., 192.168.55.1).

Private IP range : 192.168.0.0 to 192.168.255.255

Preferred router’s IP address : 192.168.x.1 where the value of x can be of 20 to 254.

Examples of the Preferred router’s IP address: 192.168.20.1, 192.168.30.1, 192.168.35.1, 192.168.46.1, 192.168.57.1, 192.168.69.1, 192.168.73.1, 192.168.96.1, 192.168.102.1, 192.168.125.1, 192.168.175.1, 192.168.186.1, 192.168.214.1

If there are multiple routers in the network then each routers IP address must be different.

Example:

• Router_1 IP address: 192.168.30.1
• Router_2 IP address: 192.168.46.1
• Router_3 IP address: 192.168.55.1
• Router_4 IP address: 192.168.107.1

In this case, the routers LAN IP address assigned is 192.168.55.1

With Subnet mask of 255.255.255.0, the range of IP address that can be assigned to client devices are:

• IP Pool Starting Address: 192.168.55.2
• IP Pool Ending Address: 192.168.55.254

2. DNS Server Setting ( LAN – DHCP Server)

• Purpose: The DNS Server Setting specifies the DNS servers that the router’s DHCP server advertises to devices on the local network. These servers translate domain names (e.g., http://www.google.com) into IP addresses.
• Location: Found under Advanced Settings > LAN > DHCP Server > DNS and WINS Server Setting in the ASUS Web GUI.
• Default Behavior: By default, the router advertises its own LAN IP (e.g., 192.168.1.1) as the DNS server if Advertise router’s IP in addition to user-specified DNS is enabled. The router’s built-in DNS resolver (dnsmasq) handles local hostname resolution (e.g., printer.mylan) and forwards external queries to upstream DNS servers (configured under WAN or ISP-provided).
• Custom DNS Servers: You can manually specify DNS servers (e.g., Google’s 8.8.8.8, Cloudflare’s 1.1.1.1) to override or supplement the router’s DNS resolver.

Key Options:

• DNS Server 1 and DNS Server 2: Fields to enter custom DNS server IPs.
• Advertise router’s IP in addition to user-specified DNS: When enabled, the router’s LAN IP is included as a DNS server alongside any user-specified servers. When disabled, only the specified DNS servers are advertised.
• WINS Server (optional): Used for NetBIOS name resolution in Windows networks (rarely used in modern setups).

User may add custom DNS Servers that will be advertised to the client devices in the LAN.

The client devices, if configured to get DNS servers from the router DHCP server, will assign the advertised DNS servers.

Advertise router’s IP in addition to user-specified DNS:

• Enable (Default): Check this box to include the router’s LAN IP (e.g., 192.168.55.1) as a DNS server. This allows the router’s dnsmasq to resolve local hostnames (e.g., printer.mylan, where mylan is the Domain Name set previously) and forward external queries to the specified or WAN DNS servers.
• Disable: Uncheck to advertise only the specified DNS servers (or WAN/ISP DNS if fields are blank). This bypasses the router’s DNS resolver, which may prevent local hostname resolution unless a custom DNS server (e.g., Pi-hole) handles it.

3. Host Name

• Description: The Host Name is the name assigned to the router itself, used for local identification and DNS resolution. It forms part of the router’s fully qualified domain name (FQDN) when combined with the Domain Name (e.g., RT-AX88U.mylan).
• Default Value: Typically the router’s model name (e.g., RT-AX88U, ZenWiFi_AX).
• Use Case: Allows you to access the router via a friendly name (e.g., MyRouter.mylan) instead of its IP address. Useful for network management and accessing the Web GUI.
• Note: The hostname is resolvable locally only if Advertise router’s IP in addition to user-specified DNS is enabled. For example, with hostname MyRouter and domain mylan, you can access the router as MyRouter.mylan or router.asus.com.

In this case, the Host Name is RT-AX1800 and the Domain Name is left blank. So the WiFi router WEb GUI is accessible using the address:

• http://rt-ax1800 or https://rt-ax1800
• http://rt-ax1800.local or https://rt-ax1800.local

---

WAN Settings

WAN DNS Settings

1. DNS Server

• Description: Specifies the DNS servers the router uses to resolve external domain names. These are the upstream DNS servers for queries not handled by the router’s local DNS resolver (dnsmasq).
• Default Value: ISP (uses DNS servers provided by the ISP via DHCP).
  • DNS servers provided by the ISP may be necessary to enable all the services provided by the ISP. Use alternate DNS server may disable some of the services.
  • DNS servers provided by the ISP is a good choice for certain location based services.
  • You can manually specify servers for better performance, privacy, or features like DNSSEC.
• Use Case:
  • Use public DNS servers (e.g., Google’s 8.8.8.8, Cloudflare’s 1.1.1.1) for faster or more secure resolution.
  • Use ISP DNS servers for compatibility with ISP-specific services.
  • Affects the router’s own DNS queries and, if Advertise router’s IP in addition to user-specified DNS is enabled in LAN settings, the external queries forwarded by the router’s dnsmasq for connected devices.
• Configuration:
  1. Log in to the Web GUI (http://router.asus.com or the router’s LAN IP, e.g., 192.168.1.1).
  2. Go to Advanced Settings > WAN > Internet Connection.
  3. Locate the WAN DNS Setting section.
  4. Click On Assign button.
  5. Set Connect to DNS Server automatically to No to enable manual configuration.
  6. Enter IPs in DNS Server 1 and DNS Server 2. Examples:
     • Google DNS: 8.8.8.8, 8.8.4.4
     • Cloudflare DNS: 1.1.1.1, 1.0.0.1
     • OpenDNS: 208.67.222.222, 208.67.220.220
  7. Click Apply.
• Note:
  • If Connect to DNS Server automatically is set to Yes, the router uses ISP-provided DNS servers, which may be slower or less private.
  • These DNS servers are used by the router and by devices if Advertise router’s IP is enabled in LAN settings (as dnsmasq forwards external queries to these servers).
  • If Advertise router’s IP is disabled in LAN settings, devices use the DNS servers specified under LAN > DHCP Server instead.

2. Forward Local Domain Queries to Upstream DNS

• Description: When enabled, this setting forwards local hostname queries (e.g., router.mylan, where mylan is the Domain Name set in LAN settings) to the upstream DNS servers specified in DNS Server (or ISP DNS if set to Auto).
• Default Value: Typically disabled to keep local queries internal to the router’s dnsmasq resolver.
• Use Case:
  • Useful in enterprise or advanced setups where an upstream DNS server (e.g., a corporate Windows DNS server) is configured to resolve local domain names.
  • Not recommended for most home networks, as public DNS servers (e.g., 8.8.8.8) cannot resolve local domains like mylan and will return errors.
• Configuration:
  1. Go to Advanced Settings > WAN > Internet Connection > WAN DNS Setting.
  2. Check or uncheck Forward local domain queries to upstream DNS:
     • Enable: Local queries (e.g., router.mylan) are sent to upstream DNS servers (e.g., 8.8.8.8 or a custom server).
     • Disable (Recommended): Local queries are resolved by the router’s dnsmasq (if Advertise router’s IP is enabled in LAN settings) and not sent upstream.
  3. Click Apply.
• Note:
  • Requires Advertise router’s IP in addition to user-specified DNS to be enabled in LAN > DHCP Server for local resolution to work when disabled.
  • If enabled, ensure the upstream DNS server is configured to resolve your local domain (e.g., mylan). Public DNS servers like Google or Cloudflare won’t resolve private domains, causing resolution failures.
  • Test with nslookup router.mylan from a connected device to verify behavior.

3. Enable DNS Rebind Protection

• Description: Protects against DNS rebind attacks, where a malicious website tricks the router into resolving a domain to a private IP (e.g., 192.168.55.x), potentially accessing local devices.
• Default Value: Typically enabled for security.
• Use Case:
  • Prevents upstream DNS servers from returning private IP addresses (e.g., 192.168.x.x, 10.x.x.x) in response to queries, reducing the risk of unauthorized access to local devices.
  • May interfere with advanced setups where a custom DNS server intentionally resolves domains to private IPs (e.g., for local services).
• Configuration:
  1. Go to Advanced Settings > WAN > Internet Connection > WAN DNS Setting.
  2. Check or uncheck Enable DNS Rebind protection:
     • Enable (Recommended): Blocks DNS responses containing private IPs, enhancing security.
     • Disable: Allows private IP responses, useful for specific setups with trusted custom DNS servers (e.g., a local DNS server resolving server.mylan to 192.168.1.100).
  3. Click Apply.
• Note:
  • Disabling this increases vulnerability to DNS rebind attacks. Only disable if you trust your upstream DNS servers and need private IP resolution.
  • If disabled and using a custom DNS server (e.g., Pi-hole), ensure it has its own rebind protection to mitigate risks.
  • Test with nslookup to ensure local services still resolve correctly if disabled.

4. Prevent Client Auto DoH

• Description: Prevents devices on the network from automatically using DNS-over-HTTPS (DoH), a protocol that encrypts DNS queries and sends them to DoH-capable servers (e.g., Cloudflare’s 1.1.1.1), bypassing the router’s DNS settings.
• Default Value: Typically enabled for control over DNS traffic.
• Use Case:
  • Ensures devices use the DNS servers specified by the router (via LAN or WAN settings) instead of DoH servers configured by browsers (e.g., Firefox, Chrome) or operating systems.
  • Useful for maintaining control over DNS traffic, especially with custom DNS servers like Pi-hole for ad-blocking or local resolution.
• Configuration:
  1. Go to Advanced Settings > WAN > Internet Connection > WAN DNS Setting.
  2. Check or uncheck Prevent client auto DoH:
     • Enable (Recommended): Blocks DoH requests, forcing devices to use the router’s specified DNS servers.
     • Disable: Allows devices to use DoH, which may bypass your DNS settings (e.g., Pi-hole) and reduce control over traffic.
  3. Click Apply.
• Note:
  • Enabling this ensures consistent DNS behavior, especially for ad-blocking or monitoring with tools like Pi-hole.
  • Some devices (e.g., browsers with DoH enabled) may require manual configuration to disable DoH if this setting is disabled.
  • Test by accessing a site with a DoH-enabled browser (e.g., Firefox with dns.cloudflare.com) and verifying that DNS queries go through your specified servers (use nslookup or Pi-hole logs).

---

WAN – NAT Passthrough

These settings control how the router handles specific types of network traffic that require special handling to traverse Network Address Translation (NAT), which is commonly used in home routers to share a single public IP address among multiple devices on a private network.

What is NAT Passthrough?

• NAT Passthrough allows specific protocols that are sensitive to NAT to pass through the router’s firewall and NAT layer without being blocked or distorted. These protocols often involve complex connection setups (e.g., VPNs or VoIP) that require special handling, such as Application Layer Gateway (ALG) functionality or port forwarding.
• The router uses ALGs to inspect and modify packets for these protocols, ensuring proper connectivity between devices on the LAN and external servers on the WAN.

Why is it Needed?

• NAT modifies IP addresses and ports, which can break protocols that embed IP/port information in their payloads (e.g., VPNs like PPTP or VoIP protocols like SIP).
• Passthrough settings enable the router to rewrite packet headers or open necessary ports dynamically to maintain connectivity.

Location:

• Found in the ASUS Web GUI under Advanced Settings > WAN > NAT Passthrough.

General Considerations:

• Enabling passthrough is typically required only if you’re using specific services (e.g., VPNs, VoIP, or multimedia streaming) that fail without it.
• Disabling passthrough can enhance security by reducing open ports but may break certain applications.
• Some protocols (e.g., IPSec) may require additional configuration, such as port forwarding or disabling NAT for specific devices.

1. PPTP Passthrough

• Description: Enables Point-to-Point Tunneling Protocol (PPTP) traffic to pass through the router’s NAT. PPTP is a legacy VPN protocol that uses TCP port 1723 and the GRE (Generic Routing Encapsulation) protocol.
• Use Case:
  • Allows devices on the LAN to establish PPTP VPN connections to remote servers (e.g., for remote work or accessing a corporate network).
  • Required if you’re running a PPTP VPN server on the LAN or connecting to an external PPTP VPN server.
• How it Works:
  • The router’s PPTP ALG opens TCP port 1723 and allows GRE traffic, which doesn’t use standard ports and is often blocked by NAT without passthrough.
• Considerations:
  • PPTP is considered insecure due to weak encryption (MS-CHAP v2 vulnerabilities). Use newer protocols like L2TP/IPSec or OpenVPN when possible.
  • If disabled, PPTP VPN connections may fail with errors like “connection refused” or “GRE protocol blocked.”
  • Test by connecting to a PPTP VPN server from a LAN device (e.g., using Windows VPN client).

2. L2TP Passthrough

• Description: Enables Layer 2 Tunneling Protocol (L2TP) traffic to pass through NAT. L2TP is often used with IPSec for secure VPN connections and typically uses UDP ports 1701, 500, and 4500.
• Use Case:
  • Supports L2TP VPN clients on the LAN connecting to external VPN servers or hosting an L2TP VPN server locally.
  • Common in enterprise VPN setups or ISP-provided VPN services.
• How it Works:
  • The L2TP ALG ensures UDP port 1701 and related IPSec ports (if used) are properly handled through NAT.
  • Often requires IPSec Passthrough to be enabled as well, as L2TP is commonly paired with IPSec for encryption.
• Considerations:
  • L2TP is more secure than PPTP, especially when paired with IPSec.
  • If disabled, L2TP VPN connections may fail with errors like “timeout” or “port unreachable.”
  • Test by connecting to an L2TP VPN server from a LAN device.

3. IPSec Passthrough

• Description: Enables Internet Protocol Security (IPSec) traffic to pass through NAT. IPSec is used for secure VPNs and relies on protocols like IKE (UDP ports 500 and 4500) and ESP (Encapsulating Security Payload, non-port-based).
• Use Case:
  • Supports IPSec VPN clients on the LAN (e.g., for corporate VPNs) or hosting an IPSec VPN server locally.
  • Often used with L2TP/IPSec or site-to-site VPNs.
• How it Works:
  • The IPSec ALG handles NAT traversal (NAT-T) by opening UDP ports 500 and 4500 and allowing ESP traffic, which NAT can otherwise block.
• Considerations:
  • IPSec is complex and may require additional settings, such as disabling NAT for the VPN client device (using DMZ or port forwarding) or enabling NAT-T on the VPN server.
  • If disabled, IPSec VPNs may fail with “IKE negotiation failed” or “ESP blocked” errors.
  • Test by connecting to an IPSec VPN server or setting up a site-to-site VPN.

4. RTSP Passthrough

• Description: Enables Real-Time Streaming Protocol (RTSP) traffic to pass through NAT. RTSP is used for streaming media (e.g., video or audio) and typically uses TCP/UDP port 554, with dynamic ports for data streams.
• Use Case:
  • Supports media streaming applications, such as IP cameras, media servers (e.g., Plex), or video conferencing systems that use RTSP.
• How it Works:
  • The RTSP ALG dynamically opens ports for RTSP data streams, which are negotiated in the protocol’s control channel.
• Considerations:
  • If disabled, RTSP-based streaming may fail, especially for external access to IP cameras or media servers.
  • For external access, you may also need to configure port forwarding for TCP/UDP 554.

5. H.323 Passthrough

• Description: Enables H.323 protocol traffic to pass through NAT. H.323 is a legacy VoIP and video conferencing protocol, using TCP port 1720 and dynamic ports for media streams.
• Use Case:
  • Supports older video conferencing systems or VoIP applications that use H.323 (e.g., legacy enterprise telephony systems).
• How it Works:
  • The H.323 ALG manages the complex call setup and dynamic port allocation required for H.323, ensuring media streams (audio/video) pass through NAT.
• Considerations:
  • H.323 is largely replaced by SIP in modern VoIP systems, so this is rarely needed unless using legacy equipment.
  • If disabled, H.323 calls may fail to establish or drop media streams.
  • Test by initiating an H.323-based video call from a LAN device.

6. SIP Passthrough

• Description: Enables Session Initiation Protocol (SIP) traffic to pass through NAT. SIP is widely used for VoIP and unified communications, typically using UDP/TCP ports 5060 and 5061, with dynamic ports for media (RTP).
• Use Case:
  • Supports VoIP phones, softphones, or communication apps (e.g., Zoom, Microsoft Teams, or Asterisk PBX) that use SIP for call setup.
  • Required for hosting a SIP server on the LAN or connecting to external SIP providers.
• How it Works:
  • The SIP ALG rewrites SIP packet headers to include the correct public IP and port information, as SIP embeds private IP/port data that NAT would otherwise break.
• Considerations:
  • SIP ALGs can sometimes cause issues with certain VoIP providers due to non-standard implementations. If calls fail (e.g., one-way audio or registration issues), try disabling SIP Passthrough and using port forwarding (e.g., UDP 5060, 5061) or a DMZ for the SIP device.
  • For external SIP access, configure port forwarding or UPnP if required by your VoIP provider.
  • Test by making a VoIP call with a SIP client or phone.

7. PPPoE Relay

• Description: Enables Point-to-Point Protocol over Ethernet (PPPoE) Relay, allowing devices on the LAN to establish their own PPPoE connections through the router to the ISP.
• Use Case:
  • Rare in home networks but useful in scenarios where a specific LAN device (e.g., a secondary router or server) needs to authenticate directly with the ISP using PPPoE credentials.
  • Common in some enterprise or multi-tenant setups where individual devices need separate public IPs or PPPoE sessions.
• How it Works:
  • The router forwards PPPoE authentication requests (using protocols like PAP or CHAP) from LAN devices to the ISP, bypassing the router’s own PPPoE connection (if configured).
• Considerations:
  • Requires the ISP to support multiple PPPoE sessions (not all ISPs do).
  • Typically used when the router is in bridge mode or when a secondary device needs a direct public IP.
  • If disabled, LAN devices cannot establish PPPoE connections independently.
  • Test by setting up a PPPoE connection on a LAN device (e.g., a computer or secondary router) with ISP credentials.

---

Administrator Settings

A. System Settings

1. Reboot Scheduler

The Enable Reboot Scheduler setting in the Administration section of an ASUS WiFi 6 router’s Web GUI allows you to schedule automatic reboots of the router at specified times. Regular reboots can help maintain optimal performance, clear memory, apply pending updates, and resolve temporary network issues. This setting is particularly useful for ensuring network stability in environments where the router runs continuously, such as homes or small offices with always-on devices.

What is Enable Reboot Scheduler?

• The Enable Reboot Scheduler setting allows you to configure the router to automatically reboot at specific times or intervals. This is a proactive maintenance feature that helps prevent performance degradation over time.
• Rebooting clears:
  • Temporary memory usage in the router’s RAM.
  • Stale network connections or DHCP leases.
  • Potential issues with services like dnsmasq (DNS resolver), NAT, or VPN tunnels.
• The scheduler typically allows you to set:
  • Frequency: Daily, weekly.
  • Time: Specific time of day (e.g., 3:00 AM to minimize disruption).
  • Day: For weekly schedules, specific days (e.g., every Sunday).

Why Use Reboot Scheduler?

• Performance Optimization: Routers running for extended periods may accumulate memory leaks or fragmented resources, slowing down performance. Scheduled reboots prevent this.
• Network Stability: Resets connections that may have become unstable (e.g., VPNs or VoIP sessions affected by NAT issues).
• Maintenance Automation: Eliminates the need for manual reboots, especially in setups with high uptime requirements.
• Firmware and Configuration Updates: Some firmware updates or configuration changes (e.g., DNS or firewall settings) require a reboot to take effect. Scheduling ensures these are applied consistently.

---

Factory Reset the Asus Wi-Fi router after the Firmware Upgrade

After upgrading the firmware on an ASUS WiFi 6 router (e.g., models from the RT-AX series like RT-AX58U, RT-AX86U, RT-AX88U, GT-AX series, etc.), the router automatically reboots once the upload and flashing process completes successfully.

At this point, the router is already running the new firmware, and in the vast majority of cases, you do not need to perform a reset immediately — most users continue using their existing settings without any problems.

However, ASUS officially recommends performing a factory reset after a firmware upgrade in many of their support documents. Here’s the complete picture, including when and how to do it safely.

A) Why ASUS Recommends a Factory Reset After Firmware Upgrade

Official ASUS support pages (in multiple languages and regions) frequently include this notice in the firmware update instructions:

Notice: It is recommended to restore to factory default settings by pressing the reset button on the bottom of the wireless router for 5 seconds after doing a firmware update. After the reset is complete, please go to http://www.asusrouter.com and follow the QIS (Quick Internet Setup) to set up your router again.

The main reasons for this recommendation are:

• New firmware versions sometimes introduce changes to internal database structure, default values, new features, renamed settings, or modified default behaviors.
• Old configuration data stored in NVRAM can become partially incompatible → this may cause subtle bugs such as:
  • Wi-Fi not broadcasting properly
  • Certain advanced settings (AiMesh, QoS, VPN, port forwarding, etc.) behaving unexpectedly
  • Guest networks or band steering not working correctly
  • Unexplained performance drops or instability
• ASUS support almost always asks for a factory reset as the first troubleshooting step when you report issues after a firmware change.

B) Do You Actually Need to Reset? (Real-World Practice)

Situation	Recommended Action	Reason / Likelihood of Problems
Update from very old → very new firmware (multiple major versions)	Strongly recommended: factory reset	High chance of config incompatibility
Minor / incremental update (same major version, e.g., .388.xxx → .388.yyy)	Optional — many people skip it	Low to moderate risk
No problems after reboot (Wi-Fi works, internet stable, most settings look correct)	You can usually skip the reset	Most common real-world outcome
Any weird behavior after update (Wi-Fi unstable, devices won’t connect, features missing, etc.)	Factory reset is usually the fastest fix	Very high success rate
Using Asuswrt-Merlin custom firmware	Almost always do a full NVRAM erase / reset after major update	Merlin strongly advises it for clean upgrades
Running AiMesh system	Reset is more strongly recommended	Mesh nodes are very sensitive to config mismatches

In community forums, the split is roughly:

• ~60–70% of experienced users skip the reset on minor updates and only reset if something breaks.
• ASUS support and many guides still say to reset every time (safest official path).

C) How to Perform a Factory Reset After Firmware Upgrade

There are three main methods — choose based on your situation.

Method 1 – Easiest (via Web GUI) – Recommended if you can still log in

1. After the firmware update finishes and the router reboots, wait 2–3 minutes.
2. Connect a computer/laptop via Ethernet cable (preferred) or Wi-Fi.
3. Open a browser → go to http://router.asus.com or 192.168.50.1 or 192.168.1.1
4. Log in (default is usually admin / admin if you never changed it, or your previous credentials).
5. Go to Administration → Restore/Save/Upload Setting
6. Under Factory default click Restore
7. Confirm → wait for the router to reboot (2–4 minutes).

Method 2 – Hardware Reset Button (most common method ASUS recommends)

1. Make sure the router is powered on and has finished booting after the firmware update (power LED stable, not flashing rapidly).
2. Use a paperclip or pen tip → press and hold the RESET button (usually on the back or bottom) for 5–10 seconds.
3. Release when the power LED starts flashing (or all LEDs flash briefly).
4. Wait 2–5 minutes for the router to reboot and return to factory defaults.
5. The Wi-Fi SSID will revert to the default name (ASUS_XX_2G / ASUS_XX_5G) printed on the label.

Method 3 – Hard / Extended Reset (use if normal reset doesn’t fully clear issues)

Some ASUS models require a slightly different procedure for a “hard” NVRAM clear:

• Power off the router.
• Press and hold the WPS button.
• Power on the router while continuing to hold WPS.
• Hold for ~10–20 seconds until LEDs flash in a specific pattern (model-dependent).
• Release → wait for reboot.

Check your exact model in the ASUS support FAQ titled “ASUS router Hard Factory Reset – Method 1 / Method 2” for the precise sequence.

Tip: Before doing the reset, many users take a screenshot of every important page or export the current config file (Administration → Restore/Save/Upload Setting → Save). After reset you can selectively re-apply settings — but be cautious, as importing an old config after major firmware change is the most common cause of instability.

---