How to Repurpose an Old Wi-Fi Router: Access Point, Wireless Bridge, and Subnet Setup Guide

In this article

1. Phase 1: Initial Hardware Reset and Subnet Planning
2. 1. Perform a Hard Factory Reset
3. 2. Map Your Existing Primary Network
4. 3. Isolate the Secondary Router for Configuration
5. Option 1: Turn an Old Router into a Dedicated Wired Access Point
6. Step-by-Step Configuration Steps
7. Option 2: Use the Old Router as a Wireless Bridge
8. Software Compatibility and Options
9. Configuration Steps for Wireless Bridge Mode
10. Option 3: Create an Isolated Subnet / Lab Network
11. Subnet Addressing Rules
12. Step-by-Step Configuration Steps
13. Security Considerations for Legacy Hardware

Upgrading your primary internet equipment often leaves a functional wireless router gathering dust in a closet. Instead of disposing of legacy hardware, you can reconfigure it to solve common local network challenges, such as eliminating wireless dead zones, adding physical Ethernet ports to remote rooms, or isolating experimental hardware on a separate network segment.

Depending on your hardware capabilities and network goals, there are three primary ways to repurpose an old Wi-Fi router:

• Wired Access Point (AP Mode): Extends your existing Wi-Fi coverage using a wired Ethernet connection back to your main router while maintaining a single, flat network.
• Wireless Bridge (Client Mode): Connects wirelessly to your main network and passes that connection to client devices through its physical Ethernet ports.
• Isolated Network Segment (Secondary Router): Uses a LAN-to-WAN configuration to place devices behind a double NAT, keeping experimental software or smart hardware separated from your primary local devices.

This technical guide walks you through preparing your legacy hardware and configuring each of these three deployment models step-by-step.

Phase 1: Initial Hardware Reset and Subnet Planning

Before modifying any settings, restore the secondary router to its original factory configuration. Factory resetting clears obsolete network credentials, legacy port-forwarding rules, and static routing tables that could cause address collisions or connectivity failures.

1. Perform a Hard Factory Reset

Locate the small physical Reset pinhole on the back or bottom of the router. With the device powered on, press and hold the button for 10 to 15 seconds using a paperclip until the status indicator lights flash, signaling a reboot.

2. Map Your Existing Primary Network

Connect a computer to your primary router (via Wi-Fi or Ethernet) to identify your baseline network configuration:

• Gateway Address: Usually 192.168.1.1 or 192.168.0.1.
• Subnet Mask: Typically 255.255.255.0.
• DHCP Pool Range: For example, 192.168.1.100 through 192.168.1.254.

You can find this information in Windows by opening Command Prompt and running ipconfig, or on macOS/Linux by opening Terminal and executing netstat -nr or ifconfig.

3. Isolate the Secondary Router for Configuration

Disconnect your computer from your main network. Plug an Ethernet cable directly from your computer’s network interface into one of the LAN ports (numbered 1–4) on the old secondary router. Do not connect the old router to the primary router yet. Open a web browser and navigate to the default administration IP address of the old router (commonly printed on the serial label on the device casing).

Option 1: Turn an Old Router into a Dedicated Wired Access Point

If you want to turn an old router into an access point, this configuration provides the best overall performance and network stability. In this model, the main router continues to manage all local IP assignments and DNS routing, while the secondary router acts solely as a wireless transceiver and Ethernet switch.

To avoid IP assignment conflicts, you must prevent both routers from handing out IP addresses simultaneously. Dual active DHCP servers on the same broadcast domain lead to network collisions and lost internet connectivity.

Setting	Primary Gateway Router	Secondary Router (Access Point Mode)
LAN IP Address	192.168.1.1	192.168.1.2 (Static, outside DHCP pool)
DHCP Server	Enabled (e.g., 192.168.1.100–254)	Disabled
Subnet Mask	255.255.255.0	255.255.255.0
Physical Connection	LAN Port	LAN Port (Do not use WAN/Internet port)

Step-by-Step Configuration Steps

1. Assign a Unique Static IP Address: Log into the secondary router’s admin panel. Navigate to the LAN or network settings page. Change the router’s local IP address to an unused address within your main router’s subnet, but outside its active DHCP range. For instance, if your main gateway is 192.168.1.1 and its DHCP pool starts at 192.168.1.100, assign 192.168.1.2 to the secondary router. Save your settings. If the admin interface reloads on the new IP address, log back in using 192.168.1.2.
2. Disable the Secondary DHCP Server: Locate the DHCP server configuration menu on the secondary router. Select Disabled or uncheck the enable DHCP server option. Save and apply changes.
3. Configure Wireless SSID and Security Settings:
   • For Seamless Roaming: Set the SSID (network name), security type, and encryption passphrase on the secondary router to match your primary network exactly. Ensure you select a non-overlapping wireless channel (such as channels 1, 6, or 11 on the 2.4 GHz spectrum, depending on your environment) to minimize radio interference.
   • For Distinct Identification: Alternatively, give the secondary router a distinct SSID (e.g., HomeNetwork_Ext) if you prefer to select which devices connect to specific physical access points manually.
4. Connect the Hardware (LAN-to-LAN): Run an Ethernet cable from a LAN port on your primary router directly into a LAN port on the secondary router. Leave the WAN/Internet port on the secondary router completely empty.

Your legacy hardware now operates as a transparent network bridge. Devices connecting via Wi-Fi or physical LAN ports on the secondary unit will receive IP addresses directly from the primary router.

Option 2: Use the Old Router as a Wireless Bridge

When you need to bring wired devices—like desktop PCs, network attached storage, or home media equipment—online in a room without an Ethernet drop, you can use an old router as a wireless bridge (often called Wireless Client or Media Bridge mode).

In this operational mode, the old router’s Wi-Fi radios connect back to your main wireless router as a client. The secondary router’s built-in Ethernet switch then redistributes network traffic to devices physically connected to its LAN ports.

Software Compatibility and Options

Native support for wireless bridging varies depending on vendor stock firmware:

• Native Stock Support: Certain router manufacturers include a simple toggle in their UI for media bridge or wireless client mode.
• Third-Party Firmware Options: If your stock vendor menu lacks client bridging functionality, legacy routers built on supported hardware can sometimes be updated with open-source firmware platforms such as OpenWrt or DD-WRT. Flashing third-party firmware unbinds restricted hardware capabilities, though it carries a risk of rendering the device inoperable if interrupted or configured incorrectly.

Configuration Steps for Wireless Bridge Mode

1. Log into the administrative dashboard of the secondary router.
2. Navigate to the operating mode or wireless settings.
3. Select the wireless bridge, client mode, or media bridge option.
4. Initiate a wireless site survey or manually enter the SSID, security protocol, and password of your main Wi-Fi network.
5. Set the secondary router’s LAN IP address to a static address within the primary subnet (e.g., 192.168.1.3) to maintain remote administrative access later.
6. Disable the secondary router’s local DHCP server if the operating system does not automatically disable it upon switching modes.
7. Save changes and reboot the router.

Position the bridge in a region with clear wireless line-of-sight to your main router. Once connected, attach your wired endpoints directly into the secondary router’s Ethernet switch ports. Prior to deploying real-time streaming services or latency-sensitive workloads across this bridge, consider checking your connection stability to identify potential packet loss or packet queueing over the wireless backhaul link.

Option 3: Create an Isolated Subnet / Lab Network

If you build experimental software projects, run localized automation scripts, or want to sandbox unknown hardware, setting up an isolated network segment using a LAN-to-WAN topology provides an effective physical and logical boundary.

This setup uses a routing technique known as Double NAT (Network Address Translation). Traffic originating on your secondary network can access the internet through the main router, but devices on the primary network cannot inspect, probe, or initiate connections directly to devices hidden behind the secondary router’s firewall unless explicit port forwarding or routing rules are established.

Subnet Addressing Rules

For a LAN-to-WAN setup to route traffic, the primary router’s network domain and the secondary router’s local network domain must occupy separate IP subnets.

• Primary Network Subnet: 192.168.1.x (Subnet Mask 255.255.255.0)
• Secondary Network Subnet: 192.168.2.x (Subnet Mask 255.255.255.0)

If both routers attempt to route local traffic over 192.168.1.x on both sides of the WAN interface, internal routing tables will fail, breaking internet access for downstream devices.

Step-by-Step Configuration Steps

1. Connect your computer directly to a LAN port on the isolated router.
2. Log into the administrative interface and locate the LAN settings page.
3. Change the local IP address of the isolated router to a unique subnet, such as 192.168.2.1.
4. Ensure that the secondary router’s internal DHCP server remains enabled, configured to hand out addresses within its new local pool (e.g., 192.168.2.100 to 192.168.2.200). Save changes.
5. Set the secondary router’s WAN or internet connection type to DHCP (automatic IP).
6. Connect an Ethernet cable from a LAN port on your Primary Router into the WAN (Internet) port on the Secondary Router.

The secondary router’s WAN interface will request an address from your primary router while maintaining its own fully isolated local segment on 192.168.2.x. For further reading on isolating high-risk hardware or smart home devices across local subnets and VLANs, read our dedicated guide on how to segment your home network for IoT security.

Security Considerations for Legacy Hardware

Re-using legacy networking gear is an economical way to extend home infrastructure, but unpatched hardware requires intentional security oversight. Once network equipment reaches End-of-Life (EOL) status, manufacturers may discontinue software patches, leaving identified firmware vulnerabilities open to exploitation.

To safely operate reconfigured network devices, implement these baseline security measures:

• Update to Final Vendor Firmware: Check the vendor support page to ensure your device is running the final firmware release issued by the manufacturer before placing it into active service.
• Change Default Admin Credentials: Never retain default credentials. Assign a strong administrative passphrase immediately.
• Disable Remote Management: Turn off web access via WAN, telnet, SSH, and Universal Plug and Play (UPnP) within the secondary router’s management interfaces to limit external attack surfaces.
• Audit Wireless Encryption Standards: Avoid obsolete encryption algorithms like WEP or WPA-TKIP. Use WPA2 or WPA3 security standards exclusively where supported.
• Evaluate Third-Party Firmware Alternatives: If your router vendor stopped updating its firmware years ago, verify if the hardware platform supports modern open-source distributions like OpenWrt. Open-source communities often maintain updated software builds and security patches for legacy hardware long after manufacturer support expires.

By enforcing clean IP address mappings, disabling overlapping services like secondary DHCP servers, and establishing secure administration boundaries, you can reliably turn old routers into functional, high-value assets within your home network.