Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Wi-Fi Router Charts

Click for Wi-Fi Router Charts

Mesh System Charts

Click for Wi-Fi Mesh System Charts

Adding Access Points: Ethernet-based

Which brings us back to the good old standby - Ethernet. CAT5 cabling may be a pain (and expensive) to run, but it's a low-tech, sure-fire way to have the fastest and most reliable network. It has the added bonus of eliminating the power outlet requirement if you use remote APs with Power Over Ethernet (POE) capability. POE puts DC power on the unused wires in a CAT5 cable, making it do double duty as both a data and power cable. Although most consumer-grade equipment doesn't include the POE feature, it's not that hard to roll-your-own POE solution.

Before I head for the Wrap Up, I'll pass along a few more tips to keep in mind when adding Access Points:

  • Mix it Up!
    You don't have to use the same make and model as your main unit when adding APs to your WLAN. Using the same product is more a matter of convenience, since you won't have to learn the admin interface for multiple products.

  • Using Wireless Routers
    Wireless Routers can be put into service as expansion Access Points, but require a little reconfiguration to work in this mode.

Configuring Multiple Access Points

Once you get them wired up, configuring multiple Access Points isn't as hard as you might think. Just follow these three basic steps:

1) Set the AP SSID

If you don't want to control which AP your client connects to, set all your APs to the same SSID. But if you want to force your client to connect to specific APs, then set different SSIDs.

Since most wireless clients are very "sticky" and tend to stay associated to the first AP they encounter, even when APs with stronger signals are available, different SSIDs are recommended for small wireless networks with users who know how to switch between wireless networks.

2) Set adjacent AP's to non-overlapping channels

For 802.11b, the usual practice is to use only channels 1, 6, and 11, which are said to be the only non-overlapping frequencies. WLAN startup Cirond Technologies, however, asserts in a whitepaper that channels 1,4, 8, and 11 can be used without significant performance degradation. You can probably use either method and get satisfactory results.

3) Use Static IPs

Although most APs will automatically grab IP address info from your LAN's DHCP server, I recommend you manually assign the IP address info to all APs. Use IP addresses in your LAN's subnet that are above the range of addresses handed out by your DHCP server. That way you always know where to reach out and touch any APs that need attention. And if your expansion AP happens to have its own built-in DHCP server - shut it off! Only one DHCP server per LAN, please!

Example: Your LAN's main router has an IP address of (subnet mask with its DHCP server set to hand out 20 addresses starting at

To make things easy, assign an address of (subnet mask to your first remote AP, and decrement the number by 1 for each additional AP.

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Don't Miss These

  • 1
  • 2