In the last episode of ,
Char Jackson said:

On Mon, 23 Dec 2013 16:23:01 -0800, DevilsPGD
wrote:

In the last episode of , Tony Hwang
said:

Do you use inSSIDer pro version or even free version? I think having
same SSID is not good. Won't it create confusion when connecting?

If the underlying networks are bridged, this is a supported
configuration and it allows client machines to move between the access
points seamlessly.

If the networks are not bridged, this will cause IP conflicts and other
problems.

If they aren't bridged, they're probably routed. Then, if each segment has a
unique IP address space, it should just work. But if each segment has the
same IP address space, the main problem won't be IP conflicts but rather IP
routing issues. The IP stack will treat it as Layer 2 but it needs to be
treated as Layer 3. I assume that's the "other problems" mentioned above.

The issue is more that when a mobile device jumps from one access point
to another (with the same SSID), it'll attempt to re-use it's existing
IP and ARP the default gateway. If the default gateway has the expected
MAC address it's assumed to be the same network and the device can
proceed as though nothing changed.

If the APR test succeeds, the total network interruption time is that of
one ARP lookup, which is probably on the order of 100ms-200ms, which is
barely noticed by the user. Small networks will be even faster,
obviously.

If the ARP fails, or returns a different MAC address, the device will
silently drop it's IP and start a new DHCP request. This is fine, but it
will cause a momentary interruption in traffic from the user's
perspective, possibly lasting long enough to generate application level
errors. In this case, using a different SSID is better because a smart
device may track past DHCP allocations and use the quick-start process
described above when returning to a SSID it recognizes, within it's
original DHCP lifespan.

--
'Outlook not so good.'
That magic 8-ball knows everything!