[Top] [All Lists]

Re: [Shop-talk] Wifi access point?

To: Shop-Talk <>
Subject: Re: [Shop-talk] Wifi access point?
From: Doug Braun <>
Date: Tue, 16 Jun 2015 19:02:42 -0400
References: <> <> <> <>
Don't places like large offices, schools, and airports have dozens or
hundreds of access points with the same SSID?


On Tue, Jun 16, 2015 at 4:22 PM, Mike Rambour <> wrote:

>  While its true that any modern device can store access credentials for
> multiple connections, my house wifi barely reaches the garage, its usually
> down to one or 2 bars in the garage and my phone will try and stay
> connected to it, I have to manually tell it to change to the garage wifi
> each time I go in the garage.  They have different names but I had not
> thought of making them the same name and will try that, it sounds like it
> should work but knowing how things work it will likely confuse the phone.
>  In the house my computers are all wired, so no worries about jumping to
> the weak signal, only my phone and my wife's phone are wifi.
>     mike
> On 6/16/2015 1:13 PM, David Hillman wrote:
>> On Tue, 16 Jun 2015, Peter Murray wrote:
>>> - Configure its SSID and encryption the same as your main access point
>>> (so
>>> you can just transparently go from one to the other)
>>    I'm not sure that's a great idea.  If the house signal reaches the
>> shop, even weakly ( or vice versa ), you'll have two networks with the same
>> name available.  I bet that'll cause more problems than it'll solve.
>>    Any modern device can store access credentials for dozens of wireless
>> networks, so there's minimal advantage to naming them the same anyway.
>>    Also, from a troubleshooting perspective, two names would be better.
>> Say you are in the shop -- or outside on the property -- and your
>> connection sucks.  Unbeknownst to you, your shop WAP crashed, and your
>> computer jumped to the weak house signal.  You won't be able to tell them
>> apart from the client device if they are named the same.
>> --
>>  David Hillman
>> _

<Prev in Thread] Current Thread [Next in Thread>