On 30 Dec 2006 14:00:04 -0800, in alt.internet.wireless , "Karlos"
<buonacorsi@gmail.com> wrote:

>Thanks,
>
>I know that giving them the same SSID is correct as it is very similar
>to Domain naming.

No.

>If you call an SSID a Domain Name, for this example,
>you would have to log on to two completely different networks everytime
>you moved from upstairs to downstairs.

No, you'd be conneting to two different APs. This is a totally
different layer in the protocol stack and doesn't affect what network
you're connecting to.

>I know this as it has been tried and tested and confirmed at my current
>place of work. This was not the issue, so for anyone who wishes to
>argue with this idea, I suggest you try it yourselves.

Either way will work, but you may get different conflicts depending on
the precise hardware and geometry. I've tried both.

>The question was can I turn a Wireless Router into just a Wireless
>Access Point,

Well, yes. Thats all it is - an AP plus a wired router. So turn off
DHCP and don't use the WAN port, and presto! .

>and do it all wirelessly... or does it need to be physically
>connected to a backbone, or similar idea, to connect with the Network.

You almost certainly need a wired backbone.

Most APs cannot be both a client (ie connecting to another router) and
a server (ie serving out connections to your laptop) at the same time.
Those that can must be installed in matched sets from the same maker,
and will suffer performance degradation.

I think you're looking for WDS.
--
Mark McIntyre