I used to have a FAQ that explained how to re-purpose a wireless router as an access point (AP). But it occurred to me that some folks might be able to use a little more of a step-by-step, so here it is. I'm going to use the virtually ubiquitous Linksys WRT54G as the object of our conversion.
Step 1: Connect a computer that is set to obtain its IP address information automatically to a LAN port on the wireless router that you want to convert to an AP. If you don't know how to do this, Figure 1 shows the applicable Windows XP screens. (Get to the Network Connections window by Start > Settings > Network Connections.)
Figure 1: Checking for "Obtain an IP address automatically"
Log into the admin page of the wireless router that you want to convert to an access point. From here on, I'll call this the "AP".
Step 2: For simple, one segment LANs, there must be only one DHCP server. Your LAN's router has a DHCP server and you don't want the two to conflict. So turn off the DHCP server on the AP. In Figure 2, you can see that the DHCP server in the WRT54G AP has been disabled.

Figure 2: Shut off the DHCP server; change the IP
Step 3: Find your LAN Router's DHCP server range. Figure 3 shows the Basic Network Settings page of the D-Link DGL-4300 that is my LAN's router. This is where the DHCP server controls happen to be. Different routers might have the DHCP server controls on a separate page, so you may have to poke around a little.

Figure 3: LAN router settings
The 4300 normally has its Router IP Address set to 192.168.0.1 by default. But you can see in Figure 3, I changed it to 10.168.3.254. This shifted the DHCP server to the 10.168.3.X subnet instead of the 192.168.0.X. I also could have used 10.168.3.1 or any address as long as it wasn't between 10.168.3.100 and 10.168.3.249, which is the DHCP server's range.
The bottom line is that the my LAN router's DHCP server range is 10.168.3.100 to 10.168.3.249.
Step 4: Change the address of the AP to an unused LAN IP address. This will ensure that you can reach the admin pages of the AP to change settings when needed. Referring back to Figure 2, you can see that I set the AP to 10.168.3.250. Again, this could be any IP from 10.168.3.1 to 10.168.3.99 or 10.168.3.250 to 10.168.3.254, which are all outside the LAN DHCP server range.
Step 5: Connect the AP to the LAN. Unplug the computer you used to configure the AP and plug it back into one of your LAN router's switch ports. Now take an Ethernet cable, plug one end into another unused router switch port and the other end into one of the AP's LAN ports. Be sure to use a LAN port and not the WAN port. Figure 4 shows the proper connection for the WRT54G.

Figure 4: AP connection detail
Step 6: Check the AP LAN connection. You should now be able to use any of your LAN's computers to reach the AP. So open a browser, enter the address that you set for the AP in Step 4 (which is at 10.168.3.250 in this example) and you should get the login prompt.
If you don't get the prompt, recheck that you have the Ethernet cable running from LAN port to LAN port on your router's switch and the AP. The respective port lights on the router and AP should be lit.
Step 7: Check the AP wireless connection. Fire up a wireless notebook or other client and check that it properly associates and pulls an IP address from your LAN router's DHCP server. Congratulations! You now have a new AP!
Now use this article if you want to use your new AP to extend your current wireless network.





Our test of six Wi-Fi 6 routers found no significant benefit from OFDMA.
We resume our quest to find OFDMA's promised benefits, by first trying to find a good benchmark test.
OFDMA, a key Wi-Fi 6 feature, is still mostly absent from consumer routers and makers are not telling us.
We take a look at how five Wi-Fi 6 routers perform with a Wi-Fi 6 client.
The first Wi-Fi performance test standard will change the way we test Wi-Fi products.
Updated - Our first look at the performance of NETGEAR's RAX80 and ASUS' RT-AX88U shows little benefit functioning as AC routers.
Our 160 MHz channel bandwidth investigation had some incorrect results. So we retested to set the record straight.
Jim Salter took ASUS' AiMesh for a drive and found your mileage may vary...a lot!
Updated: The first draft 11ax routers are almost here. Take a little time to know what you might be buying into.
Updated - In our latest exploration of Wi-Fi Roaming, we take a look at the roaming behavior of five Wi-Fi systems.
Cloud managed networks aren't just for Enterprises anymore.
TP-Link's Deco M9 Plus brings lots of features and a third radio to the Wi-Fi mesh system party.
Open Mesh's OM5P-AC is not the way to go for an inexpensive AC1200 access point.
ASUS Lyra Trio's three-stream approach to mesh Wi-Fi fails to impress.
The new version of TP-Link's inexpensive AC access point has a lot to like.
Linksys' takes a run at cheaper version of its Velop Mesh Wi-Fi System and comes up too short.
In the third part of our Wi-Fi Roaming exploration, we look at Windows and Android roams.
Updated - In Part 2 of our Wi-Fi Roaming exploration, we show how to tell if your devices support 802.11k,v or r.
Been thinking about buying a mesh Wi-Fi system? You might already own the start of the best one you can get.
Ever wonder what happens behind the scenes when Wi-Fi devices roam, or more likely don't? We'll show you why the "seamless" roaming Wi-Fi gear makers promise is still as elusive as a Yeti.
Updated - ASUS' Blue Cave Dual Band AC2600 Wireless Router has much better routing performance than we initially thought.
A gaming router can give you the edge you need. Learn how.
Updated - Jim Salter takes another run at our collection of 2x2 AC APs, this time testing multi-client load handling in open air, with roaming too!
Phicomm's K3C AC1900 MU-MIMO Gigabit Router provides our first look at an router with Intel Wi-Fi inside.