Most configurations happen via the web interface (tplinkwifi.net) or the TP-Link Tether app (iOS/Android). Always update firmware first via the app or website for security and stability.
Accessing the Web Management Interface
To understand and configure the settings for your TP-Link Archer (Tri-Band Wi-Fi 6E Router), you’ll primarily use the web-based management interface. Here’s how to access it:
- Connect to the Router: Use an Ethernet cable to connect your computer to one of the router’s LAN ports, or connect wirelessly using the default Wi-Fi network name (SSID) and password printed on the router’s label.
- Open a Web Browser: Launch a supported browser like Chrome, Firefox, or Edge.
- Enter the Address: Type http://tplinkwifi.net or http://192.168.0.1 in the address bar (not the search bar) and press Enter.
- Log In:
- On first access, you’ll be prompted to set a secure admin password (no default username/password for newer models; older ones use admin for both).
- If you’ve set a password previously, enter it. If forgotten, reset the router by holding the Reset button for 10 seconds (this erases all settings).
The interface is intuitive, with a dashboard showing connection status, connected devices, and quick links. It’s also accessible via the TP-Link Tether app for mobile management.
Main Menu Structure and Key Settings
The web interface is divided into Basic and Advanced tabs for easy navigation. Below is a hierarchical overview of the typical menu structure for the Archer AXE95 (based on standard TP-Link Archer series design, including Wi-Fi 6E-specific features like the 6 GHz band). Each category includes brief descriptions of key options and what they control. Note: Exact labels may vary slightly by firmware version—check for updates under Advanced > System Tools > Firmware Upgrade.
Basic Tab (For everyday monitoring and simple tweaks)
- Home/Status/Dashboard
- Overview of internet speed, Wi-Fi coverage, connected devices, and system info (e.g., firmware version, uptime).
- Quick actions: Restart router, run speed test, or view alerts.
- Internet
- Displays WAN connection status (e.g., IP address, connection type).
- Basic tweaks: Reconnect, clone MAC address, or enable/disable IPv6.
- Wireless
- Configure SSID, password, and security for each band (2.4 GHz, 5 GHz, 6 GHz).
- Options: Enable/disable bands, set channel width (20/40/80/160 MHz), channel selection (auto or manual), and broadcast SSID.
- Wi-Fi 6E specifics: Enable 6 GHz band for low-latency devices; supports WPA3 encryption.
- Guest Network
- Set up separate SSIDs for guests (one per band).
- Controls: Bandwidth limits, access to local network (on/off), and expiration timers for security.
- Network Map
- Visual topology of your network, showing router, connected devices, and signal strength.
- Clients
- List of connected devices with details (IP, MAC, hostname).
- Actions: Block devices, prioritize traffic, or label for easier management.
Advanced Tab (For detailed configuration)
- Quick Setup
- Wizard for initial setup: Select time zone, internet connection type (Dynamic IP, Static IP, PPPoE, L2TP/PPTP), enter ISP credentials (e.g., username/password for PPPoE), and optional VLAN ID.
- Also configures Wi-Fi settings in one go.
- Network
- Internet: Advanced WAN settings like MTU size, DNS servers (manual override for custom DNS like Google 8.8.8.8), dynamic DNS (DDNS), and IPv6 configuration.
- LAN: Set local IP address (default 192.168.0.1), DHCP server range, and static IP reservations for devices.
- IPTV: Enable VLAN tagging for IPTV services if provided by your ISP.
- Wireless > Advanced Settings
- Per-band fine-tuning: Transmit power, WMM (for multimedia prioritization), MU-MIMO/Beamforming (Wi-Fi 6E enhancements for multi-device efficiency), and OFDMA settings.
- WPS: Wi-Fi Protected Setup for easy device pairing (push-button or PIN).
- Wireless Schedule: Set times to auto-disable Wi-Fi for energy savings or bedtime controls.
- HomeShield (TP-Link’s built-in security suite)
- Security: Real-time threat detection, malware blocking, and intrusion prevention (powered by Trend Micro).
- Parental Controls: Profile-based rules for kids—block sites, set time limits, content filters (e.g., pause internet during homework).
- Insights: Usage reports, vulnerability scans, and network health summaries.
- USB Sharing
- Share printers or storage devices plugged into the router’s USB ports.
- Options: Enable Samba/FTP servers, media server (DLNA for streaming), and access controls.
- NAT Forwarding
- Virtual Servers/Port Forwarding: Open ports for servers (e.g., gaming, web hosting).
- Port Triggering: Dynamic port opening for apps like torrent clients.
- DMZ: Expose a device to the internet (use cautiously for security).
- UPnP: Auto-port forwarding for compatible devices (e.g., consoles).
- VPN Server
- Set up built-in VPN server: OpenVPN (for secure remote access) or PPTP (legacy compatibility).
- Generate config files for clients.
- Bandwidth Control / QoS
- Prioritize traffic (e.g., gaming over streaming) by device or app.
- Set upload/download limits per device or overall.
- System Tools
- Time Settings: Sync with NTP server or manual timezone.
- Diagnostic: Ping/traceroute tools for troubleshooting.
- Firmware Upgrade: Check and install updates (latest as of Dec 2025: V1.6_1.1.6 Build 20241203).
- Factory Defaults / Backup & Restore: Reset or save/load configs.
- Administration: Change admin password, enable local/remote management (set port 80/443, restrict IPs).
- LED Control: Dim or schedule LED lights (e.g., night mode).
- Log / Statistics: View event logs, traffic stats per interface.
Operation Mode
- Switch between Router Mode (default, for full NAT/firewall) and Access Point Mode (extends existing network without routing). Found under Advanced > Operation Mode or during setup.
Network Settings
1. Status
The Advanced > Network > Status page on the TP-Link Archer AXE95 (AXE7800 Tri-Band Wi-Fi 6E Router) is primarily a diagnostic and monitoring tool designed to help troubleshoot internet connectivity issues. It provides a snapshot of the router’s WAN (Wide Area Network) connection status, focusing on whether the router has successfully obtained an IP address from your Internet Service Provider (ISP). This page is not for direct configuration but serves as a starting point for identifying and resolving problems like “no internet access” errors on connected devices.
Access it via:
- Log in to the web interface at http://tplinkwifi.net or http://192.168.0.1.
- Click the Advanced tab.
- Select Network from the left sidebar.
- Click Status (typically the first or overview sub-tab in the Network section).
A) Internet
| Field | Description | Typical/Valid Values | Troubleshooting Notes |
|---|---|---|---|
| 1) Status | Overall indicator of the WAN connection health. This is a high-level summary (e.g., “Connected” or “Disconnected”) that reflects whether the router can reach the ISP’s network. It aggregates data from other fields like IP Address and Connection Type. | – Connected (green/success icon) – Disconnected (red/error icon) – Connecting… (transient state) | If “Disconnected,” start with physical checks: Ensure the WAN cable is plugged into the blue WAN port from your modem. Power cycle the modem (wait 2 min) then router (wait 1-2 min). Re-check after 1 min. If persistent, proceed to IP Address troubleshooting below. Run a diagnostics ping from Advanced > System Tools > Diagnostics to test ISP reachability. |
| 2) Internet Connection Type | The method your router uses to authenticate and obtain an IP from the ISP. This must match your ISP’s requirements (e.g., most cable/fiber uses Dynamic IP). | – Dynamic IP (DHCP: auto-assigns IP) – Static IP (manual entry) – PPPoE (username/password for DSL) – L2TP/PPTP (VPN-like for some ISPs) | If mismatched (e.g., shows Dynamic IP but your ISP uses PPPoE), go to Advanced > Network > Internet, select the correct type, enter credentials (e.g., username/password for PPPoE), and click Save. Restart the modem and router. Contact your ISP if unsure of the type. Invalid type often causes cascading errors in other fields. |
| 3) IP Address | The public IPv4 address assigned to your router’s WAN interface by the ISP. This uniquely identifies your network on the internet. | – Valid: A routable public IP (e.g., 73.45.12.34; not starting with 10.x, 172.16-31.x, 192.168.x, or 169.254.x) – Invalid: 0.0.0.0 (no connection) or 169.254.x.x (APIPA: self-assigned fallback) | If 0.0.0.0: 1. Verify WAN cable and modem lights (link/activity). 2. Clone MAC: Advanced > Network > Internet > MAC Clone > Select “Use Computer MAC Address” > Save > Reboot. 3. Change LAN IP to avoid conflicts: Advanced > Network > LAN > Set to 192.168.2.1 > Save. 4. Power cycle modem/router. 5. If valid but no internet: Check DNS fields below. Upgrade firmware via Advanced > System Tools > Firmware Upgrade. |
| 4) Subnet Mask | Defines the network portion of the IP address, determining how many devices can share the subnet. It “masks” the IP to separate host and network IDs. | – Default for home ISPs: 255.255.255.0 (/24: allows 254 devices) – Other common: 255.255.0.0 (/16) for larger subnets | Rarely changes unless using Static IP. If invalid (e.g., 0.0.0.0), it’s tied to IP failure—follow IP Address troubleshooting. For Static IP setups, enter manually in Advanced > Network > Internet matching your ISP’s specs (e.g., via ISP portal). Mismatches can cause routing loops; verify with ISP if editing. |
| 5) Default Gateway | The IP address of the next “hop” for traffic leaving your local network (usually your modem or ISP’s router). All outbound internet requests route through this. | – Often the ISP’s gateway (e.g., 73.45.12.1 if your IP is 73.45.12.34) – Invalid: 0.0.0.0 (no route) | If 0.0.0.0, same as IP Address fixes: Check connections, MAC clone, LAN IP change, power cycle. For Static IP, manually set in Advanced > Network > Internet > Default Gateway. Test by pinging the gateway IP from Diagnostics—if it fails, contact ISP for modem/gateway issues. Essential for internet access; without it, devices can’t route beyond LAN. |
| 6) Primary DNS | The first Domain Name System server queried to resolve domain names (e.g., google.com to 142.250.191.14). Provided by ISP or manually set. | – ISP-provided (e.g., 75.75.75.75 for Comcast) – Public: 8.8.8.8 (Google), 1.1.1.1 (Cloudflare) | If blank/0.0.0.0 or resolution fails (valid IP but sites won’t load): Go to Advanced > Network > DHCP Server > Use the following DNS > Set Primary to 8.8.8.8 > Save. Restart devices. This overrides ISP DNS for privacy/speed. Test by pinging google.com from Diagnostics. |
| 7) Secondary DNS | Backup DNS server used if Primary fails. Provides redundancy for name resolution. | – ISP secondary or public like 8.8.4.4 (Google secondary) – Often left blank if using Primary only | Similar to Primary: Set in DHCP Server to 8.8.4.4 for fallback. If both fail, it mimics Primary troubleshooting—manual override resolves most “DNS probe finished” errors. Use for load balancing; e.g., mix Google and Cloudflare for better uptime. |
| 8) Online Duration | The elapsed time since the WAN connection was last established (uptime counter). Resets on disconnects or reboots. | – Format: HH:MM:SS or days HH:MM:SS (e.g., 02:45:30 for 2 hours, 45 min) – 00:00:00 if disconnected | Not directly configurable. If stuck at 00:00:00, follow Status/IP troubleshooting. Useful for monitoring stability—short durations indicate flaky connections (e.g., due to modem issues). Log resets via Advanced > System Tools > System Log for patterns. No specific fixes beyond resolving underlying connectivity. |
B) LAN Status
| Field | Description | Typical/Valid Values | Troubleshooting Notes |
|---|---|---|---|
| MAC Address | The unique hardware identifier (Media Access Control) for the router’s LAN interface. This is a 12-digit hexadecimal address burned into the router’s Ethernet chip, used for local device discovery and communication. It doesn’t change unless you clone it for advanced setups. | – Format: XX:XX:XX:XX:XX:XX (e.g., A1:B2:C3:D4:E5:F6) – Valid: Any unique 48-bit address (first 3 bytes are TP-Link’s OUI, like 50:C7:BF for Archer series) | If mismatched (e.g., devices can’t see the router): Verify against the label on the router’s bottom. For conflicts (rare), go to Advanced > Network > LAN > MAC Address to customize (not recommended for beginners). Restart router if recently changed. Use Basic > Network Map to confirm devices detect this MAC. No direct impact on internet, but essential for wired/wireless LAN bridging. |
| IP Address | The router’s local IPv4 address on the LAN, acting as the “default gateway” for all connected devices. This is the address you use to access the web interface (e.g., typing it in a browser). | – Default: 192.168.0.1 or 192.168.1.1 – Valid: Private IP in ranges like 192.168.x.x, 10.x.x.x, or 172.16-31.x.x (Class C for home use) | If invalid (e.g., 0.0.0.0 or conflicting with another device): 1. Go to Advanced > Network > LAN > IP Address > Set to a non-conflicting value (e.g., 192.168.1.1 if your modem uses 192.168.0.1) > Save > Reboot. 2. Update static IPs on devices to match the new subnet. 3. Power cycle router. Common issue: Double NAT with ISP modem—set modem to bridge mode via ISP app. Test by pinging the IP from a connected device. |
| Subnet Mask | Defines the size of your local network by separating the network ID from host IDs in the IP Address. It determines how many devices can connect (e.g., /24 allows 254 hosts). | – Default: 255.255.255.0 (/24) – Valid: 255.255.255.0 (most common for homes), 255.255.0.0 (/16 for larger networks) | If mismatched (e.g., 0.0.0.0 or causing IP exhaustion): Edit in Advanced > Network > LAN > Subnet Mask > Set to 255.255.255.0 > Save > Reboot. Ensure it aligns with IP Address (e.g., don’t use /16 with 192.168.0.x). Symptoms: Devices get IPs outside the range (e.g., 169.254.x.x APIPA). Fix by reserving IPs in DHCP Server or checking for subnet overlaps with other networks (e.g., VPNs). Verify with ipconfig (Windows) or ifconfig (Mac/Linux) on a client device. |
2. Internet Settings
A) Internet connection type: Dynamic IP
The Advanced > Network > Internet page on the TP-Link Router is where you configure your Wide Area Network (WAN) connection to your ISP. When selecting Dynamic IP as the Internet Connection Type, the router uses DHCP (Dynamic Host Configuration Protocol) to automatically request and receive network parameters from your ISP’s modem or server. This is the most common setup for cable, fiber, or Ethernet-based internet services, as it requires no manual entry of credentials or static details.
Below is a detailed breakdown of the key fields and options on this page for Dynamic IP.
| Field/Option | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| Internet Connection Type | Dropdown to select the WAN authentication method. Dynamic IP enables automatic assignment via DHCP, ideal for most home ISPs without username/password requirements. | – Default: Dynamic IP (for cable/fiber). – Options: Dynamic IP, Static IP, PPPoE, L2TP/PPTP, Bigpond Cable. | Select Dynamic IP and click Save. If your ISP uses PPPoE (e.g., DSL), switch here and enter credentials. Mismatch causes no connection—verify with ISP. Test post-save by checking Status page for valid public IP. |
| IP Address | The public IPv4 address assigned to your router’s WAN port by the ISP. Read-only; auto-obtained via DHCP lease (typically 24 hours, renewable). | – Auto-filled (e.g., 73.45.12.34; public/routable). | No manual edit. If 0.0.0.0 or local IP: Click Release then Renew; power cycle modem (2 min) then router (1 min); clone MAC if ISP-bound (MAC Clone section below). Run speed test from dashboard. |
| Subnet Mask | Defines the network range for the assigned IP, separating network and host portions. Auto-assigned with IP. | – Default/Auto: 255.255.255.0 (/24 subnet, supports 254 devices). | Read-only. Rarely needs adjustment; mismatches cause routing issues. If invalid, follow IP troubleshooting. |
| Default Gateway | The IP of the upstream device (e.g., ISP modem/router) for outbound traffic. Auto-assigned. | – Auto: Often ends in .1 (e.g., 73.45.12.1). | Read-only. If 0.0.0.0, same as IP fixes. Ping it from Diagnostics to test ISP link. |
| Primary DNS | First server for resolving domain names. Auto-from ISP, but overridable. | – Auto: ISP’s (e.g., 75.75.75.75 for Comcast). | Read-only here; override in Advanced Settings > DNS. Set to 1.1.1.1 for faster/privacy. If blank, sites won’t load—manual DNS fixes “DNS probe” errors. |
| Secondary DNS | Backup DNS for redundancy if Primary fails. | – Auto: ISP secondary (e.g., 75.75.76.76). | Same as Primary. Use pairs like 8.8.8.8/8.8.4.4 (Google) for reliability. Test resolution by pinging google.com. |
| RENEW / RELEASE | Buttons to manage the DHCP lease. Renew requests a fresh IP/config from ISP; Release drops the current lease (forces re-request on next boot/renew). | – N/A (action buttons). | Use for troubleshooting: Release if IP conflict (e.g., “address in use”), then Renew. If no change, reboot or check modem lights. Avoid frequent use to prevent ISP flagging. |
| Advanced Settings (Expandable Panel) | Toggle for deeper tweaks; expands to show DNS, MTU, etc. Click the arrow to access. | – N/A (section header). | Enable for customizations; Save applies changes. Useful if auto-settings fail (e.g., VPNs, jumbo frames). |
| DNS Address | Dropdown/option to source DNS servers: Auto from ISP or manual entry. | – Default: Get Dynamically from ISP. – Options: Use These DNS Servers (manual). | Select manual to override (e.g., for ad-blocking via 1.1.1.2). Restart devices after change. |
| MTU Size | Maximum packet size in bytes for WAN transmission. Larger MTU can boost speed but risks fragmentation. | – Default: 1500 bytes. – Range: 576–1500 (do not change unless advised by ISP). | Lower to 1492 for PPPoE encapsulation issues (e.g., “can’t load pages”). Test with ping -f -l 1472 (Windows) for optimal. |
| Host Name | Optional identifier sent in DHCP requests; helps ISP track your device (e.g., for logs). | – Default: Blank (uses MAC address). | Enter a name like “MyRouter” if required by ISP. Rarely used; leave blank unless troubleshooting. |
| Get IP using Unicast DHCP | Checkbox to use targeted (unicast) DHCP requests instead of broadcast. Improves efficiency in complex networks (e.g., with relays). | – Default: Disabled (broadcast mode). | Enable if in a subnet with DHCP relay or multi-router setup (e.g., enterprise). Test connectivity post-enable; revert if issues. |
B) Internet connection type: PPPoE
When PPPoE (Point-to-Point Protocol over Ethernet) is selected as the Internet Connection Type, the router establishes a direct, authenticated session with your ISP’s server—common for DSL, VDSL, or some fiber services. This requires credentials (username/password) provided by your ISP, and it encapsulates Ethernet frames in PPP for secure tunneling.
Unlike Dynamic IP (fully automatic), PPPoE handles authentication and can assign dynamic IPs post-login. Actual setup will auto-populate IP/DNS after saving and authenticating. If fields remain invalid post-save, it indicates credential errors or modem issues.
Below is a detailed breakdown of the key fields and options for PPPoE.
| Field/Option | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| Internet Connection Type | Dropdown for WAN method. PPPoE enables username/password authentication over Ethernet, establishing a virtual dial-up session. | – Default for DSL: PPPoE. – Options: Dynamic IP, Static IP, PPPoE, L2TP/PPTP, etc. | Select PPPoE and Save. If your ISP uses Dynamic IP (cable), switch back. Mismatch prevents connection—confirm with ISP. Post-save, check Status for “Connected” and public IP. |
| Username | ISP-provided login for PPPoE authentication (often email-like). Sent to ISP server during connection. | – ISP-specific (e.g., user123@isp.com). | Enter exactly as provided (case-sensitive). If connection fails (“Authentication Failed”), verify spelling/typos or contact ISP for reset. Clear browser cache or try incognito for login issues. |
| Password | ISP-provided secret for PPPoE. Masked for security (eye icon to toggle visibility). | – ISP-specific (alphanumeric, 8+ chars). | Enter securely; enable eye icon only temporarily. Wrong password causes disconnects—reset via ISP portal if forgotten. Use strong, unique creds; avoid “admin” in production. |
| IP Address | Public IPv4 assigned post-PPPoE login. Read-only; dynamic unless ISP specifies static. | – Auto: Public (e.g., 73.45.12.34). | No edit. If 0.0.0.0 post-save: Re-enter creds, power cycle modem/router, or check MTU. For static, contact ISP to enable. |
| Primary DNS | First DNS resolver, assigned by ISP post-login or manual. | – Auto: ISP’s (e.g., 208.67.222.222 for OpenDNS). | Read-only here; override in Advanced Settings > DNS. Use 1.1.1.1 for speed/privacy. If blank, pages won’t load—set manual. |
| Secondary DNS | Backup DNS for failover. | – Auto: ISP secondary. | Same as Primary. Pair with Primary (e.g., 8.8.8.8/8.8.4.4) for reliability. Test: Ping google.com from Diagnostics. |
| Advanced Settings (Expandable Panel) | Toggle for PPPoE-specific tweaks; click arrow to expand. | – N/A (header). | Essential for DSL optimization; Save applies. Use if basic auth succeeds but connection drops. |
| Secondary Connection | Failover WAN link (e.g., another PPPoE session or Dynamic IP) for redundancy if primary fails. | – Default: None. – Options: None, Dynamic IP, Static IP, PPPoE. | Set to PPPoE with alternate creds for dual-line ISPs. Enable auto-failover; monitor in Status. |
| MTU Size | Max packet size for PPPoE (accounts for 8-byte header). Lower than Ethernet’s 1500 to avoid fragmentation. | – Default: 1492 bytes (PPPoE standard). – Range: 576–1492. | Don’t change unless ISP advises (e.g., 1480 for some VDSL). Symptoms of mismatch: Slow speeds/large file failures. |
| Service Name | Optional PPPoE tag identifying the service (e.g., “DSL-Home”). | – Default: Blank. | Enter only if ISP requires (rare). Wrong value blocks auth—omit unless specified. |
| Access Concentrator Name | ISP’s PPPoE server identifier (e.g., “isp-server1”). | – Default: Blank. | ISP-specific; usually auto-detected. If connection fails, get from ISP support. |
| Detect Online Interval | How often (in seconds) the router pings to check/renew PPPoE session. | – Default: 30 seconds. – Range: 10–120. | Lower for faster failover (e.g., 20); higher for stability. If frequent drops, increase to 40. |
| IP Address (Advanced) | How to obtain WAN IP post-auth: Dynamic (DHCP) or Static. | – Default: Get Dynamically from ISP. | Keep dynamic unless ISP assigns static (enter manually). Static avoids lease issues but requires ISP coordination. |
| DNS Address (Advanced) | Sourcing of DNS servers: Auto from ISP or manual. | – Default: Get Dynamically from ISP. | Switch to manual for custom (e.g., ad-block). |
| Primary/Secondary DNS (Advanced) | Manual DNS overrides if not using ISP’s. | non-standard—use 8.8.8.8/8.8.4.4). | Enter if overriding (e.g., for privacy). Restart after change; fixes resolution errors. |
| Connection Mode | Controls auto-dial behavior: Always on (default), Manual (user-initiated), or Time-based (schedule). | – Default: Always on. – Options: Always on, Manual, Time-based. | For home use, Always on. Time-based useful for data caps; Manual for troubleshooting. |
| Connection Time | Schedule for Time-based mode (start/stop hours:minutes). | – Format: HH:MM to HH:MM (24-hour). | Set daily schedule (applies to all days). If mis-set (e.g., end before start), defaults to Always on. Monitor uptime in Status. |
C) Internet connection type: Static IP
Selecting Static IP as the Internet Connection Type means you enter fixed network parameters provided by your ISP, rather than auto-obtaining them via DHCP. This is typically used for business, dedicated servers, or static residential plans where the ISP assigns a permanent public IP (e.g., for hosting websites or avoiding IP changes). Unlike Dynamic IP or PPPoE, there’s no auto-negotiation—incorrect entries will block internet access.
Below is a detailed breakdown of the key fields for Static IP.
| Field/Option | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| Internet Connection Type | Dropdown for WAN method. Static IP requires manual entry of all details—no authentication or auto-assignment. | – Default for static plans: Static IP. | Select Static IP and Save. Post-save, check Status for valid connection. Wrong type = no internet. |
| IP Address | Your fixed public IPv4 address assigned by ISP. Defines your router’s identity on the WAN. | – ISP-provided (e.g., 73.45.12.34; public/routable). | Enter exactly (no auto-fill). If private post-save: Confirm with ISP (may need public IP upgrade). Symptoms of error: 0.0.0.0 in Status. |
| Subnet Mask | Specifies the network size/subnet for the IP (e.g., how many addresses are usable). | – Default: 255.255.255.0 (/24; 254 usable IPs). | Enter ISP’s value. Mismatch causes isolation (devices can’t communicate). Common: /24 for single static IP. |
| Default Gateway | IP of the upstream router/gateway (ISP’s) for routing outbound traffic. | – ISP-provided (e.g., ends in .1 like 73.45.12.1). | Enter precisely. If wrong, no internet despite valid IP. Ping Gateway from Diagnostics; if fails, cable/modem issue. For private setups, ensure no double NAT. |
| Primary DNS | Main server for domain name resolution (e.g., translates google.com to IP). | – ISP-provided or public (e.g., 8.8.8.8). | Enter ISP’s or override with 1.1.1.1 (Cloudflare) for better speed/privacy. If blank/wrong, sites won’t load (IP pings work, but DNS fails). Set in DHCP Server for LAN-wide. |
| Secondary DNS (Optional) | Backup DNS for redundancy if Primary is unreachable. | – ISP secondary or public (e.g., 8.8.4.4). | Recommended: Add 1.0.0.1 or ISP’s. Improves uptime; test by disabling Primary temporarily. Leave blank if ISP handles failover. |
| MTU Size | Maximum packet size (bytes) for WAN transmission. Affects efficiency; too high causes fragmentation. | – Default: 1500 bytes (Ethernet standard). – Range: 576–1500. | Don’t change unless ISP specifies (e.g., 1492 for PPPoE, but Static often 1500). |
D) Internet connection type: L2TP
L2TP (Layer 2 Tunneling Protocol) creates a virtual tunnel for secure data transmission, often paired with IPsec for encryption, and is used by some ISPs (e.g., for DSL/VPN hybrid services) or enterprise networks. It requires ISP-provided credentials and a VPN server address, then assigns an IP dynamically or statically post-tunnel establishment. Unlike PPPoE (Ethernet-focused), L2TP is more VPN-oriented and can encapsulate PPP frames.
Below is a detailed breakdown of the key fields for L2TP.
| Field/Option | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| Internet Connection Type | Dropdown for WAN method. L2TP sets up a tunnel to the ISP’s VPN server for authenticated access. | – Default for L2TP ISPs: L2TP. – Options: Dynamic IP, Static IP, PPPoE, L2TP/PPTP, etc. | Select L2TP and CONNECT. If your ISP uses PPPoE, switch. Post-connect, verify in Status for tunnel uptime. Wrong type blocks tunnel—confirm with ISP. |
| Username | ISP-provided login for L2TP authentication (sent over the tunnel). | – ISP-specific (e.g., user@isp.com). – Screenshot: “admin” (placeholder; insecure—use real creds). | Enter case-sensitively. Auth failure (“Invalid Credentials”) means wrong username—contact ISP for verification/reset. |
| Password | Secret for L2TP session. Masked (eye icon toggles). | – ISP-specific (8+ chars). – Screenshot: Hidden (•••••). | Enter securely. Wrong password drops tunnel—reset via ISP if needed. Enable IPsec if required (advanced; not in UI). |
| IP Address | WAN IPv4 assigned post-tunnel (dynamic or static). Read-only until connected. | – Auto: Public (e.g., 73.45.12.34). | No direct edit. If 0.0.0.0 after connect: Re-enter creds, click DISCONNECT then CONNECT, or check server. |
| Primary DNS | First DNS resolver, assigned post-tunnel. | – Auto: ISP’s or public. | Read-only; override in advanced DNS. If blank, no name resolution—set manual post-connect. |
| Secondary DNS | Backup DNS for reliability. | – Auto: ISP secondary. | Same as Primary. Add for failover; test ping google.com. |
| Dynamic IP / Static IP (Radio Buttons) | Chooses IP assignment mode post-auth: Dynamic (DHCP over tunnel) or Static (manual). | – Default: Dynamic IP (easier). | Select Dynamic for most; Static if ISP assigns fixed. Switch and reconnect. Static needs exact ISP details. |
| VPN Server IP/Domain Name | Address of ISP’s L2TP server (endpoint for tunnel). | – ISP-provided (e.g., vpn.isp.com) | Critical: Wrong server = no tunnel. Enter domain or IP; test ping from Diagnostics. Common error: “Server Unreachable.” |
| IP Address (Static Section) | Fixed WAN IP if Static selected. | – ISP-provided. | Only for Static: Enter public IP. Mismatch isolates network. |
| Subnet Mask (Static) | Network range for static IP. | – Default: 255.255.255.0 (/24). | For Static: Match ISP. Wrong = routing fails. |
| Default Gateway (Static) | Upstream gateway IP over tunnel. | – ISP-provided (e.g., .1). | For Static: Enter exactly. Ping it post-connect; failure = config error. |
| Primary DNS (Static) | Manual DNS if Static. | – ISP/public. | For Static: Set to 8.8.8.8 for reliability. |
| Secondary DNS (Static, Optional) | Backup for Static. | – ISP secondary. | Add 8.8.4.4. Improves uptime. |
| MTU Size | Max packet size for L2TP tunnel (lower due to headers). | – Default: 1500 bytes. – Range: 576–1500. | Adjust if slow/large transfers fail (e.g., 1400 for IPsec overhead). Test: Ping -f -l [MTU-40]; lower if “fragmented.” |
| Connection Mode | Controls tunnel behavior: Always on, Manual (user-triggered), or Connect on Demand. | – Options: Always on, Manual, Connect on Demand. | Manual for testing; Always on for home. Demand dials on traffic (saves bandwidth). |
| Max Idle Time | Disconnects tunnel after inactivity (0 = always connected). | – Default: 0 (always). – Range: 0–99 minutes. | Set 0 for constant; 30+ for metered plans. If drops too soon, increase or switch mode. |
| CONNECT / DISCONNECT | Buttons to initiate/drop tunnel. | – N/A (actions). | Click CONNECT to start; gray if already connected or mode mismatch. Use for troubleshooting: Disconnect, wait 30s, reconnect. |
E) Internet connection type: PPTP
PPTP (Point-to-Point Tunneling Protocol) is an older VPN-like protocol used by some ISPs for authenticated internet access (e.g., certain DSL or legacy services). It establishes a tunnel to the ISP’s server using provided credentials, then assigns an IP dynamically or statically. Note: PPTP is considered insecure (vulnerable to attacks) and deprecated in favor of modern protocols like L2TP/IPsec or PPPoE—use only if required by your ISP.
Below is a detailed breakdown of the key fields for PPTP, based on the standard TP-Link interface.
| Field/Option | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| Internet Connection Type | Dropdown for WAN method. PPTP creates an encrypted tunnel (basic GRE + PPP) to the ISP server for auth. | – Default for PPTP ISPs: PPTP. – Options: Dynamic IP, Static IP, PPPoE, PPTP, L2TP, etc. | Select PPTP and Save. If your ISP uses L2TP, switch. Post-save, check Status for “Connected” and public IP. Wrong type = auth failure. |
| Username | ISP-provided login for PPTP authentication. | – ISP-specific (e.g., user@isp.com). – Default/placeholder: “admin” (insecure—replace). | Enter case-sensitively. Failure (“Invalid Login”): Verify with ISP; clear spaces/typos. |
| Password | Secret for PPTP session. Masked (eye icon to view). | – ISP-specific (8+ chars). – Default/placeholder: Hidden (•••••). | Enter securely. Wrong password causes disconnects—reset via ISP if lost. |
| IP Address | WAN IPv4 assigned post-tunnel. Read-only until connected. | – Auto: Public (e.g., 73.45.12.34). – Placeholder: 1.1.1.1 (invalid—updates on connect). | No edit. If 0.0.0.0: Re-auth, power cycle, or check server/MTU. |
| Primary DNS | First DNS post-tunnel. | – Auto: ISP’s. – Placeholder: 1.1.1.1 (Cloudflare). | Read-only; manual override in advanced. Blank = no resolution—set to 8.8.8.8. |
| Secondary DNS | Backup DNS. | – Auto: ISP secondary. – Placeholder: 11.11.11.11 (use 1.0.0.1 instead). | Same as Primary. Test: Ping external site. |
| Dynamic IP / Static IP (Radio Buttons) | Post-auth IP mode: Dynamic (DHCP) or Static (manual). | – Default: Dynamic IP. – Often Dynamic for PPTP. | Dynamic for auto; Static if ISP assigns fixed (enter details below). Switch and reconnect. |
| VPN Server IP/Domain Name | ISP’s PPTP server endpoint for tunnel. | – ISP-provided (e.g., pptp.isp.com). – Placeholder: www.tp-link.com (replace). | Essential: Ping it first. Wrong = “Server Unreachable”—get from ISP docs. |
| IP Address (Static) | Fixed WAN IP if Static selected. | – ISP-provided. – Placeholder: Blank. | Static only: Enter public IP. Error = no routing. |
| Subnet Mask (Static) | Subnet for static IP. | – Default: 255.255.255.0. – Placeholder: 255.255.255.0. | Static only: Match ISP. Mismatch = isolation. |
| Default Gateway (Static) | Upstream gateway post-tunnel. | – ISP-provided (e.g., .1). – Placeholder: 192.168.137.1 (private—verify). | Static only: Ping post-connect; fails = config issue. |
| Primary DNS (Static) | Manual DNS for Static. | – ISP/public (e.g., 192.168.137.1). – Placeholder: Matches Gateway. | Static only: Use 8.8.8.8 for reliability. |
| Secondary DNS (Static, Optional) | Backup for Static. | – ISP secondary. – Placeholder: Blank. | Add 8.8.4.4 for failover. |
| MTU Size | Max packet size (lower for PPTP overhead ~40 bytes). | – Default: 1420 bytes. – Range: 576–1500. – Placeholder: 1300–1420 (ISP-tuned). | Adjust if fragmentation (slow speeds): Test ping -f -l 1392; lower if needed. Don’t exceed 1492 typically. |
| Connection Mode | Tunnel behavior: Always on, Manual, Connect on Demand, or Time-based. | – Default: Always on. – Placeholder: Manual. | Always on for constant; Manual for testing; Demand for idle disconnects; Time-based for schedules. |
| Max Idle Time | Auto-disconnect after inactivity (0 = always on). | – Default: 0 minutes. – Range: 0–99. – Placeholder: 22 minutes. | Set >0 for metered; 0 for home. Frequent drops? Increase or switch mode. |
| Connection Time (Time-based) | Schedule start/end (HH:MM). | – Format: HH:MM to HH:MM. – Placeholder: 12:13 to 23:25. | Time-based only: Logical range (e.g., 08:00 to 22:00). Mis-set defaults to Always on. |
| CONNECT / DISCONNECT | Manual tunnel control. | – N/A (buttons). – CONNECT gray if idle; DISCONNECT active. | Use in Manual mode: Click CONNECT to dial; monitor logs for errors. |
F) MAC Clone Settings
The MAC Clone feature, found under Advanced > Network > Internet, allows you to modify the MAC (Media Access Control) address of the router’s WAN (internet-facing) port. This is useful when your ISP binds internet access to a specific device’s MAC address (e.g., your computer’s), rejecting the router’s default MAC and causing connection failures (like a 0.0.0.0 WAN IP). Cloning “spoofs” the router to mimic another MAC, enabling seamless connectivity without ISP reconfiguration.
The Router MAC Address specifically refers to the default, manufacturer-assigned MAC for the WAN interface (displayed read-only). Selecting this option reverts to the original, un-cloned state. It’s one of three options in the MAC Clone dropdown/section, which appears below the main Internet Connection Type fields (e.g., Dynamic IP). Changes take effect after clicking Save and may require rebooting the modem/router.
This setting is most relevant for Dynamic IP or cable/fiber ISPs; it’s not needed for PPPoE/L2TP/PPTP (which use credentials).
Key Options in the MAC Clone Section
The section includes a dropdown with three choices, plus a read-only display of the current WAN MAC. Below is a breakdown:
| Option | Description | Configuration Notes & Troubleshooting |
|---|---|---|
| Use Default MAC Address | Uses the router’s factory-default MAC address for the WAN port. This is the “original” hardware identifier (e.g., A1:B2:C3:D4:E5:F6) burned into the device. Selecting this disables cloning and reverts to stock settings. | Select to reset after testing clones (e.g., if custom causes issues). No input needed—Save applies instantly. If ISP rejects: Switch to clone options below. View current via Basic > Status. Common fix for “MAC binding” errors. |
| Clone Current Device MAC Address | Automatically detects and clones the MAC from the currently connected computer (wired preferred; wireless MACs differ). Ideal for quick ISP compatibility without manual entry. | Click to clone, then Save. Disconnect/reconnect WAN cable post-save. If fails (e.g., “No MAC detected”): Ensure direct Ethernet to LAN port; restart browser. Test: Check Status > Internet for updated MAC. |
| Use Custom MAC Address | Manually enter a specific MAC (e.g., from an old router or another device). Useful for advanced setups or if ISP requires a non-computer MAC. | Enter in the text field, Save. Validate format first (use online tools if needed). If connection drops: Revert to Router MAC. Ensure uniqueness to avoid conflicts. |
G) Internet Port Negotiation Speed Setting
The Internet Port Negotiation Speed Setting (also referred to as WAN Port Negotiation or Ethernet Port Speed) on the TP-Link Archer allows you to manually control the speed and duplex mode of the WAN (internet) port, overriding the default auto-negotiation. This is useful when auto-detection fails due to incompatible modems, faulty cables, or ISP equipment, resulting in connection issues like no WAN IP (0.0.0.0), intermittent drops, or capped speeds (e.g., stuck at 100 Mbps instead of 1 Gbps or 2.5 Gbps).
Default: Auto Negotiation (router and modem negotiate the highest compatible speed/duplex automatically).
Key Options and Their Meanings
The dropdown offers speed/duplex combinations based on the port’s capabilities (10/100/1000/2500 Mbps; half/full duplex). Half duplex allows bidirectional but not simultaneous traffic (older/legacy); full duplex is standard for modern setups.
| Option | Description | Typical Use Case |
|---|---|---|
| Auto Negotiation | Router auto-detects and matches the modem’s speed/duplex (e.g., settles on 2500 Mbps full if compatible). | Default for most users; works with varying ISP gear. |
| 10 Mbps Half Duplex | Forces 10 Mbps bidirectional (no simultaneous send/receive). | Legacy/very old modems or diagnostic testing. |
| 10 Mbps Full Duplex | Forces 10 Mbps full bidirectional. | Same as above, but slightly better for short bursts. |
| 100 Mbps Half Duplex | Forces 100 Mbps bidirectional. | Faulty auto-neg on 100 Mbps plans or cable issues. |
| 100 Mbps Full Duplex | Forces 100 Mbps full. | Same; preferred over half. |
| 1000 Mbps Half Duplex | Forces 1 Gbps bidirectional. | Gigabit plans with negotiation glitches. |
| 1000 Mbps Full Duplex | Forces 1 Gbps full (Gigabit Ethernet standard). | Standard for 1 Gbps ISPs; fixes auto-fail. |
| 2500 Mbps Full Duplex | Forces 2.5 Gbps full (multi-gigabit). | High-speed fiber (2.5G plans) with compatible modem. |
H) Flow Controller Settings
Flow Control is an Ethernet protocol designed to regulate data transmission between devices (e.g., router and connected PCs/switches) to avoid packet loss when one side is overwhelmed. When enabled, the router can send or receive “PAUSE” frames (brief signals) to temporarily halt traffic from the peer device. This is useful in high-traffic environments (e.g., with many devices streaming or transferring large files) but can introduce latency in low-congestion scenarios like home networks. By default, it’s Disabled to prioritize speed over congestion avoidance, as modern Wi-Fi 6 (with OFDMA/MU-MIMO) handles bursts efficiently.
| Option | Description | When to Enable | Potential Impact | Recommendations |
|---|---|---|---|---|
| RX Enabled (Receive Flow Control) | Allows the router to receive PAUSE frames from connected devices (e.g., a PC signals the router to stop sending data if the PC’s buffer is full). This protects the receiver from overload on incoming traffic. | When LAN devices (e.g., NAS or switches) frequently drop packets due to high inbound rates from the router. | Reduces packet loss during bursts; may add slight latency (10-50 ms pauses). No effect if peer doesn’t support 802.3x. | Enable if you notice retransmits in System Tools > Traffic Statistics (high errors on RX). Disable for gaming/low-latency apps to avoid unnecessary pauses. |
| TX Enabled (Transmit Flow Control) | Allows the router to transmit PAUSE frames to connected devices (e.g., router signals a PC to stop sending if the router’s buffer fills). This protects the router from overload on outgoing LAN traffic. | When the router handles heavy upstream traffic (e.g., multiple uploads) and peers can’t keep up. | Prevents router buffer overflows; can cause upstream stalls if overused. Default may auto-enable in some firmwares. | Enable only if TX errors spike in stats; otherwise, disable to maintain full throughput. Users report no issues disabling both for home use. |
2. LAN Settings
A) LAN Settings
The Advanced > Network > LAN page on the TP-Link Archer Router is the primary configuration area for your local network settings. This editable section defines the router’s internal network parameters, which all connected devices (wired or wireless across 2.4 GHz, 5 GHz, and 6 GHz bands) use to communicate. Changing these can resolve IP conflicts (e.g., with an upstream modem), expand your network size, or customize for advanced setups like VLANs or multi-subnet environments.
| Field | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| 1) MAC Address | The unique hardware identifier (Media Access Control) for the router’s LAN interface. This 48-bit address is used for local device discovery, ARP resolution, and bridging to Wi-Fi. You can customize it (spoof) for advanced needs, like migrating from an old router without changing device configs. | – Default: Factory-assigned (e.g., 50:C7:BF:XX:XX:XX; viewable on device label). – Format: XX:XX:XX:XX:XX:XX (hexadecimal). – Custom: Any valid MAC (e.g., from old router). | Click Use Custom MAC Address > Enter value > Save. Reboot required. If changing: Ensure uniqueness to avoid conflicts (e.g., duplicates cause ARP storms). Troubleshooting: If devices can’t detect router (e.g., “No Gateway”), revert to default. Rarely needed for home use—only for ISP LAN binding or lab testing. Verify in Basic > Network Map. |
| 2) IP Address | The router’s static IPv4 address on the LAN, serving as the default gateway for all devices. This is the address you use to access the web interface (e.g., typing it in a browser). It anchors the local subnet. | – Default: 192.168.0.1 (Class C private range). – Valid: Private IPs like 192.168.x.1, 10.x.x.1, or 172.16-31.x.1 (avoid public IPs). – Custom: e.g., 192.168.1.1 (to avoid modem overlap). | Enter new address > Save (auto-updates DHCP pool). Reboot disrupts connections—notify users. Troubleshooting: If “Network Unreachable” post-change: Devices may still use old IP; flush DNS (ipconfig /flushdns on Windows) or set static routes. Common issue: Double NAT (modem on same subnet)—change to 192.168.2.1. Test: Ping new IP from a device. |
| 3) Subnet Mask | Defines the network portion of the IP Address, determining the size of your local subnet (how many devices can connect without a separate network). It “masks” bits to split network ID from host IDs. | – Default: 255.255.255.0 (/24; allows 254 usable IPs, e.g., 192.168.0.2 to .254). – Common: 255.255.0.0 (/16; 65,534 IPs for large networks). – Valid: /8 to /30 (e.g., 255.0.0.0 for 10.x.x.x). | Enter new mask > Save. Must align with IP (e.g., /24 for 192.168.0.x). Troubleshooting: Mismatch causes “IP outside subnet” (devices get 169.254.x.x APIPA). Symptoms: Inter-device isolation. Fix: Match mask to IP range; expand for >254 devices (e.g., /23: 255.255.254.0 for 510 IPs). Verify with ipconfig on clients—subnet should match router’s. |
B) Flow Controller
The Flow Controller (also called Flow Control) setting on the TP-Link Archer Router is an advanced Ethernet-level feature designed to manage data flow on the LAN ports to prevent packet loss during network congestion. It implements IEEE 802.3x standard, allowing the router to send or receive “PAUSE” frames—brief signals that temporarily halt traffic from connected devices (e.g., PCs, switches, or NAS) when buffers overflow. This is particularly useful in high-traffic environments with many devices or large file transfers, but it’s typically overkill for home networks and can introduce minor latency (e.g., 10-50 ms pauses).
This setting applies to all physical LAN ports (including the 2.5 Gbps multi-gig ones) and indirectly affects wired-to-Wi-Fi bridging but not wireless bands directly. It’s a business-grade option carried over from TP-Link’s enterprise lineup, and enabling it is rarely necessary for consumers—most users can safely leave it off without issues.
Flow Controller Options
These are independent checkboxes for bidirectional control. Enabling both activates full flow control, but you can fine-tune for specific traffic patterns (e.g., heavy downloads but light uploads).
| Option | Description | Purpose | When to Enable | Potential Drawbacks & Troubleshooting |
|---|---|---|---|---|
| RX Enabled (Receive Flow Control) | Permits the router to receive PAUSE frames from connected LAN devices. If a device (e.g., your PC) detects overload on incoming data from the router, it sends a PAUSE to temporarily stop the router from transmitting more packets. | Prevents buffer overflows on the receiving end (e.g., during high-speed downloads from the router to a device), reducing packet loss and retransmissions. | When LAN devices frequently drop inbound packets (e.g., NAS transfers or multiple streams). Check System Tools > Traffic Statistics for high RX errors. | May cause brief upload stalls if over-triggered. If latency spikes (e.g., in gaming), disable and rely on TCP recovery. Test: Run iPerf3 download; monitor for pauses. |
| TX Enabled (Transmit Flow Control) | Permits the router to transmit PAUSE frames to connected LAN devices. If the router’s buffer fills (e.g., from heavy upstream traffic like uploads), it signals devices to pause sending data. | Protects the router from congestion on outgoing LAN traffic, ensuring stable multi-device performance (e.g., when several PCs upload simultaneously). | In dense wired setups (e.g., 10+ Ethernet devices) with bursty traffic. Enabled by default in some older firmwares but off here. | Can halt device transmissions unnecessarily, impacting real-time apps. If enabled without need, disable to boost throughput. Verify: Ping flood from a device; look for delays in Diagnostics. |
3. IPTV/VLAN Settings
A) IPTV/VLAN Settings
The Advanced > Network > IPTV/VLAN page on the TP-Link Archer Wi-Fi 6 Router enables configuration for Internet Protocol Television (IPTV) services and Virtual Local Area Network (VLAN) tagging, which are often required by ISPs for delivering TV streams over the same connection as internet (e.g., via fiber or DSL). This setup isolates IPTV multicast traffic (using IGMP for group management) from regular data, preventing buffering issues or interference with your home network. It’s essential for services like AT&T U-verse, Verizon FiOS, or European providers (e.g., British Telecom) that use VLAN IDs for authentication or QoS prioritization.
Without this, IPTV set-top boxes (STBs) may not receive channels, or streams could lag due to unhandled multicast.
Key Configuration Elements
| Element | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| Enable IPTV/VLAN | Activates VLAN tagging (802.1Q) for separating IPTV traffic via IDs, allowing simultaneous internet/TV on one line. | – Default: Disabled. – Checkbox: Checked to enable. | Use if no IGMP (e.g., VLAN-only ISPs). Expands to mode selection. If enabled but no TV: Verify ISP VLAN IDs (e.g., Internet: 0, TV: 20). |
| IPTV Mode | Defines how VLANs are handled—pre-configured for major ISPs or custom. | – Default: None (disabled). – Dropdown: Bridge (auto for listed ISPs like CenturyLink), Custom (manual VLAN entry). | Bridge: Auto-assigns ports (e.g., LAN4 for TV). Custom: Enter ISP params. Troubleshooting: Wrong mode = no STB signal—switch to Custom and input VLAN ID (e.g., 4094 for some). Test with STB reboot. |
| VLAN ID (Custom Mode) | Unique tag for IPTV traffic (e.g., 100 for internet, 200 for voice/TV). | – Default: Blank. – Numeric fields: Separate IDs for Internet, IPTV, VoIP (e.g., 0/20/30). | ISP-provided (e.g., via welcome email). Enter per service > Save. If blank/mismatch: Streams fail—double-check with ISP portal. Supports 802.1Q tagging. |
| 802.1Q Tag | Checkbox to enable standard VLAN encapsulation on frames. | – Default: Enabled in Custom mode. – Checkbox: Checked. | Required for tagged VLANs. Untick for untagged (rare). Troubleshooting: Packet captures (via Diagnostics) show untagged traffic if disabled. |
| LAN Port Assignment | Designates which physical LAN port(s) for STB connection (e.g., isolates TV to LAN3). | – Default: Auto (e.g., LAN4 in Bridge). – Dropdown: LAN1-LAN8 . | Select after mode > Save. Connect STB to chosen port. Multi-port for VoIP/STB. Issue: Wrong port = no signal—swap cables or reassign. |
B) IGMP Settings
The IGMP (Internet Group Management Protocol) subsection under Advanced > Network > IPTV/VLAN on the TP-Link Archer Router configures multicast traffic handling, which is crucial for IPTV services that deliver live TV channels via IP multicast streams (e.g., from your ISP to set-top boxes or apps like Plex). Multicast allows efficient one-to-many delivery without flooding your entire network, but without proper IGMP support, streams may not reach devices, causing “no signal” errors or bandwidth waste.
IGMP operates at Layer 3 (IP) to manage group memberships: Hosts (e.g., STBs) join/leave multicast groups, and routers/switch forward traffic accordingly.
Key IGMP Elements
| Element | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| IGMP Proxy | Enables the router to act as an intermediary between your LAN (hosts/STBs) and WAN (ISP multicast source). It translates IGMP queries/reports, allowing multicast traffic to cross the router without requiring direct ISP-to-host communication. | – Default: Disabled (checkbox unchecked). – Enabled: Checked. | Tick to enable for multicast IPTV. Works with Snooping for efficiency. Troubleshooting: If STB shows “No Channels,” enable Proxy > Save > Reboot STB. Disable if non-multicast ISP (e.g., unicast streaming like Netflix)—causes log spam. Test: Ping multicast address (e.g., 239.0.0.1) from a tool like VLC. |
| IGMP Snooping | Dynamically monitors IGMP messages on LAN ports to build a multicast forwarding table, sending streams only to subscribed ports/devices. This prevents “flooding” (broadcasting to all ports), saving bandwidth and reducing latency. | – Default: Disabled (checkbox unchecked). – Enabled: Checked. | Always enable with Proxy for IPTV. Supports per-VLAN snooping if IPTV enabled. Troubleshooting: Buffering? Enable Snooping > Save; view table in System Tools > Traffic Statistics (multicast groups). If overkill (small network), disable to free CPU—rare drops occur. |
| IGMP Version | Specifies the IGMP protocol variant for compatibility with ISP equipment and hosts. V2 is basic (group queries/leaves); V3 adds source-specific joins (SSMs) for better security/QoS. | – Default: V2 (dropdown). – Options: V2 or V3. | Select V2 for legacy ISPs (e.g., Comcast); V3 for modern (e.g., Verizon FiOS with IPv6). ISP-specific—mismatch causes “Join Failures” in logs. Troubleshooting: Switch to V3 if V2 drops sources; check System Log for “IGMP Version Mismatch.” |
Additional Context in IPTV/VLAN Page
- Integration with IPTV/VLAN: IGMP works alongside VLAN tagging (e.g., multicast on VLAN ID 20). If VLAN enabled, IGMP applies per-tag for isolation.
- Multicast Routing Toggle: May appear below—enables PIM (Protocol Independent Multicast) for inter-VLAN forwarding (default off; advanced users only).
4. DHCP Server
A) DHCP Server
The Advanced > Network > DHCP Server page on the TP-Link Archer Wi-Fi Router allows you to configure the Dynamic Host Configuration Protocol (DHCP) server, which automatically assigns IP addresses, gateways, DNS servers, and other TCP/IP parameters to devices on your local network (LAN). This simplifies network management, prevents IP conflicts, and ensures devices get optimal settings without manual configuration. The main DHCP Server sub-tab focuses on global settings like the IP pool and lease duration, while Address Reservation (below) handles static assignments for specific devices (e.g., printers or servers).
Key Fields in DHCP Server Configuration
| Field | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| Enable DHCP Server | Toggle to activate the DHCP service, allowing automatic IP assignment to clients. When disabled, devices must use static IPs or get them from an upstream server (e.g., ISP modem). | – Default: Enabled (checkbox ticked). | Tick to enable > Save. Purpose: Core for dynamic networks. If disabled accidentally (e.g., devices get 169.254.x.x APIPA): Re-enable and reboot router/clients. Conflicts with external DHCP? Disable upstream first. |
| IP Address Pool (Start IP / End IP) | Defines the range of IPv4 addresses available for dynamic assignment. The pool excludes the router’s LAN IP and reserved/static ones; size should match your needs (e.g., 50–200 for homes). | – Default: 192.168.0.100 (Start) to 192.168.0.199 (End; 100 addresses). – Valid: Within LAN subnet (e.g., .10–.240 for larger). | Enter Start/End > Save (auto-adjusts if invalid). Purpose: Balances scalability/security. Troubleshooting: Pool exhausted (> devices than size)? Expand (e.g., .50–.250) but stay under 254. Narrow for guest isolation. Verify in Status > DHCP Server > Client List. |
| Default Gateway | The IP address clients use for routing non-local traffic (always the router’s LAN IP). | – Default: Auto-filled as LAN IP (e.g., 192.168.0.1). – Read-only unless manual override (rare). | No edit needed—auto-sets. Purpose: Directs internet access. If mismatched: Recheck LAN IP (Network > LAN) > Save. Devices pinging Gateway but no internet? WAN issue (Status > Internet). |
| Primary DNS | The first DNS server assigned to clients for domain resolution (e.g., google.com → IP). | – Default: Router’s LAN IP (forwards to ISP/WAN DNS). – Common manual: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). | Enter if ISP-provided or custom > Save. Purpose: Enables web access; overrides for privacy/speed. Troubleshooting: “DNS Probe Failed”? Set to public DNS > Restart clients. Test: nslookup google.com on a device. |
| Secondary DNS | Backup DNS server for failover if Primary is unreachable. | – Default: Blank (relies on Primary). – Common: 8.8.4.4 (Google secondary) or 1.0.0.1. | Optional but recommended; enter > Save. Purpose: Redundancy. If both fail: Manual override resolves outages. Pair with Primary (e.g., Google/Cloudflare mix). |
| Lease Time | Duration a DHCP-assigned IP is reserved for a device before renewal/expiration (prevents constant re-assignment). | – Default: 1 Day (1440 minutes). – Range: 1–2880 minutes (1 minute to 2 days). | Select from dropdown (e.g., 1 Hour, 1 Day, 1 Week) > Save. Purpose: Stability vs. flexibility. Troubleshooting: Frequent IP changes? Increase to 7 Days. Short (1 Hour) for public hotspots. View remaining in Status > DHCP Client List. |
B) Address Reservation
The Address Reservation sub-section under Advanced > Network > DHCP Server on the TP-Link Archer Router allows you to assign a fixed (static) IP address to specific devices based on their MAC (Media Access Control) address, while still using the DHCP system for automatic assignment. This creates “DHCP reservations”—devices get the same IP every time they connect, without manual static config on the device itself. It’s ideal for ensuring consistency in port forwarding (e.g., for a NAS or game console), avoiding IP conflicts, or simplifying network management (e.g., printers always at .50).
Unlike full static IPs (set on the device), reservations are managed centrally on the router and fall within the DHCP pool (e.g., 192.168.0.100–.199). You can add up to 32 reservations. Defaults: Empty table (no reservations). Changes take effect after Save; devices renew their IP on next lease (or reboot them manually).
Key Elements of Address Reservation
| Element | Description | Typical/Default Values | Configuration Notes & Troubleshooting |
|---|---|---|---|
| MAC Address | The unique hardware identifier of the device (e.g., from its label or router’s client list). This binds the reservation—device always gets the IP when it requests via DHCP. | – Format: XX:XX:XX:XX:XX:XX (hexadecimal, e.g., AA:BB:CC:DD:EE:FF). – Default: Blank (user-entered). | In “Add New”: Enter manually or Scan (detects connected devices). Purpose: Ensures persistence. Troubleshooting: Wrong MAC (e.g., wireless vs. wired)? Device gets dynamic IP—verify via Basic > Clients (MAC column). Case-insensitive. |
| Reserved IP Address | The fixed IP assigned to the MAC, within the DHCP pool but outside dynamic range if desired (e.g., .50 for static-feel). | – Default: Blank. – Valid: Matches LAN subnet (e.g., 192.168.0.50; must be unused). | Enter in “Add New” > OK. Purpose: Consistency for rules (e.g., port forwarding to .105). Troubleshooting: Conflict (e.g., “IP in Use”)? Choose unused (ping test first) or expand pool (DHCP Server above). Auto-excludes router’s LAN IP. |
| Device Name | Optional label for the device (e.g., “Home Printer” or “Xbox Console”). | – Default: Blank. – Text: Up to 32 chars (alphanumeric). | Enter in “Add New” > OK. Purpose: Easy identification in table/logs. No functional impact—use for organization. |
| Status (Enable/Disable) | Toggles the reservation on/off without deleting. | – Default: Enabled (checked). – Checkbox: Checked for active. | In table: Click Edit > Toggle > OK. Purpose: Temporarily pause (e.g., testing). Troubleshooting: Device ignores? Ensure Enabled and lease expired (reboot device). |
| Add New / Scan | Button/form to create a reservation: Scans LAN for devices or manual entry. | – Scan: Populates dropdown with connected MACs/IPs. – Manual: Fields for MAC/IP/Description. | Click Add New > Select/Enter > Check Enable > OK > Save. Purpose: Quick setup. Troubleshooting: Scan empty? Ensure device connected (Ethernet preferred); manual entry if Wi-Fi. |
| Modify / Delete | Modify or remove entries from the table. | – N/A (action buttons per row). | Select row > Edit (update fields) or Delete > OK > Save. Purpose: Maintenance. Troubleshooting: Delete stuck? Refresh page or reboot router. |
C) DHCP Client List
The DHCP Client List sub-section under Advanced > Network > DHCP Server on the TP-Link Archer Wi-Fi Router provides a real-time, read-only overview of all devices currently assigned IP addresses via the DHCP server. This diagnostic tool lists active leases, helping you monitor network usage, identify unauthorized devices, troubleshoot connectivity issues (e.g., why a device has “limited connectivity”), and manage reservations. It shows details like IP assignments, MAC addresses, and lease expiration, making it easier to spot conflicts or expired entries.
Key Columns in the DHCP Client List Table
| Column | Description | Typical/Example Value | Purpose & Notes |
|---|---|---|---|
| Assigned IP Address | The IPv4 address assigned to the device from the DHCP pool. | 192.168.0.105 | Confirms assignment; sortable. If 169.254.x.x (APIPA), device failed DHCP—check pool size or enable DHCP. |
| MAC Address | The device’s unique hardware identifier. | AA:BB:CC:DD:EE:FF | Identifies hardware; copy for reservations (Address Reservation). Wireless MACs differ from wired—note for troubleshooting. |
| Device Name | The device’s network name (e.g., from OS settings). | MyLaptop or android-123456 | Helps identify users; blank if not set. Edit on device for better visibility. |
| Interface | Connection type (e.g., wired LAN port or Wi-Fi band). | LAN1, Wi-Fi-2.4GHz, Wi-Fi-6GHz | Pinpoints access method; useful for band steering issues (e.g., device stuck on 2.4 GHz). AXE95 shows 6 GHz for compatible clients. |
| Lease Time | Time left before the IP lease expires (renews automatically). | 23:45:12 (HH:MM:SS) or 1d 02:30:00 | Indicates stability; short (<1 hour)? Increase global Lease Time (DHCP Server). Expired? Device reconnects. |
| Status | Online/offline indicator for the device. | Online (green icon) or Offline (gray) | Real-time presence; offline despite connected? Check cable/Wi-Fi signal in Network Map. |
| Actions (if available) | Inline buttons like Reserve or Block. | N/A (contextual) | Quick-add to reservations or block via Clients > Block; not always shown—use for security. |
5. Dynamic DNS
Dynamic DNS (DDNS) is a service that maps a static domain name (e.g., yourhome.dyndns.org) to your router’s dynamic public IP address, which can change periodically from your ISP. This is essential for remote access to your home network—such as accessing a security camera, file server, or the router’s admin page—from anywhere via the internet, without needing to know your current IP. The Archer AX53 supports DDNS under Advanced > Network > Dynamic DNS, allowing automatic updates to keep the mapping current.
Key Benefits for Users:
- Enables secure remote management via the Tether app or web interface.
- Works with Wi-Fi 6 features for stable connections.
- Free with TP-Link’s own service; paid options available from third parties for advanced features.
Prerequisites:
- A stable internet connection (public WAN IP preferred; works with private IPs but may require port forwarding).
- For TP-Link DDNS: Register a TP-Link cloud account and bind it to your router (go to Advanced > System Tools > TP-Link Cloud > Bind).
- For third-party services: Create an account on their website and note your credentials.
Accessing the DDNS Settings
- Log in to the router’s web interface (http://tplinkwifi.net or 192.168.0.1).
- Navigate to Advanced > Network > Dynamic DNS.
- The page displays:
- Service Provider: Dropdown to select the DDNS provider.
- Status: Shows if DDNS is enabled/disabled, connection status (e.g., “Connected” or “Disconnected”), and current IP/domain.
- Enable DDNS: Toggle to activate.
- Provider-specific fields (vary by selection).
- Save button to apply changes.
The router updates the DDNS server every 10-15 minutes or on IP change. If your ISP uses CGNAT (private WAN IP), DDNS may show as connected but remote access could fail—contact your ISP for a public IP.
Supported DDNS Providers and Setup
The AX53 supports several popular providers. Here’s a breakdown:
| Provider | Description | Setup Steps | Required Fields |
|---|---|---|---|
| TP-Link | Free, TP-Link-hosted service (e.g., yourname.tplinkdns.com). Easiest for beginners. | 1. Select TP-Link from dropdown. 2. Click Register. 3. Enter a unique Hostname (e.g., vikhome). 4. Click Save—domain binds automatically to your public IP. | – Hostname (alphanumeric, no spaces; auto-appends .tplinkdns.com) |
| NO-IP | Free tier available; supports multiple hostnames and port forwarding. | 1. Create account at noip.com and get credentials. 2. Select NO-IP. 3. Enter Domain Name, Username, and Password. 4. Click Login to verify, then Save. | – Domain Name (e.g., vikhome.ddns.net) – Username – Password |
| DynDNS | Paid service for reliable updates; good for businesses. | 1. Sign up at dyn.com. 2. Select DynDNS. 3. Enter Hostname, Username, Password, and Key (if required). 4. Click Login and Save. | – Hostname (e.g., vikhome.homeip.net) – Username – Password – Key (API key from DynDNS) |
| Others (e.g., Comexe, Dyn) | Less common; similar to above. | Follow provider’s site for account setup, then fill fields as prompted. | Varies (typically hostname, user/pass). |