> Does anyone have advice on wireless lan? What is the recommended > architecture for adding a second access point?
Warning: A lot of this is strictly opinion, since there are many ways to accomplish what you're asking. But like operating systems, I like the concept of semi-independent modules rather than integrated devices when designing/constructing a LAN or wireless LAN. Thus, I shy away from the combo wireless gateway, modem, DHCP server and router devices. I've seen too many quirks and problems with them and IMHO they make diagnosing problems a PITA. If I have the choice, I typically disable the wireless, routing, and DHCP functions of those devices. I want the DSL modem or cable modem to function only as a bridge/modem between the ISP and my LAN. My preference is to do DHCP and routing in GNU/Linux and to use Wireless Access Points (WAPs) to bring in wireless devices into the LAN, the WAPs merely functioning as network bridges, moving people from wireless to the Ethernet that the LAN runs on. Again, this is primarily due to my philosophy about integrated and modular solutions. As to the specific setup, this is largely dependent on your devices and their capabilities/features. But in general, a lot of these devices can be set up as "repeaters" or just access points. Their docs will typically mention something about configuring the device as an "access point". You turn off DHCP in the second WAP, use the same ESSID, and the device functions to just roll you over when you're walking around. You'll be using one WAP and when out of range in a blink of the eye you'll be switched over to another WAP without you even being aware of it. -- "I feel betrayed by the West. The opportunity we seized on behalf of peace has been lost." -- Former USSR leader Mikhail Gorbachev, from a 2000 interview.
