> From: Brandon Allbery [mailto:allber...@gmail.com]
>
> It
> depends on whether the OS actually tears down the interface while
> renegotiating or leaves it valid;
Acknowledged: It's OS dependent. If you jump from one AP to another, on the
same network with the same SSID, and get the same IP a
The L2 broadcast domain would grow...excessive, I suspect. If you've got a
campus large enough to require this, you've got enough people and devices
that you're probably don't want them all on the same subnet. Again, just
guessing. I've never dealt with a network this large - my largest is my
curre
On Sun, Apr 7, 2013 at 7:22 AM, David Lang wrote:
> When the AP's don't support roaming, the client needs to dissociate from
>> the original AP, give up its IP address and request again from DHCP. The
>> fact that DHCP assigns the same IP again is largely irrelevant - the fact
>> that the client
On Sun, 7 Apr 2013, Robert Hajime Lanning wrote:
On 04/07/13 04:15, David Lang wrote:
also, as you move from one zone to another, all your connections will
drop as the new router won't have them in it's masquerade tables.
Yes, that would be true. I spaced on the NAT state table, though, you
On 04/07/13 04:15, David Lang wrote:
also, as you move from one zone to another, all your connections will
drop as the new router won't have them in it's masquerade tables.
Yes, that would be true. I spaced on the NAT state table, though, you
could probably find a way to sync them, across rout
On Sun, 7 Apr 2013, Edward Ned Harvey (lopser) wrote:
Date: Sun, 7 Apr 2013 12:03:24 +
From: "Edward Ned Harvey (lopser)"
To: David Lang , Frank Bulk
Cc: "tech@lists.lopsa.org"
Subject: RE: [lopsa-tech] Wifi
From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org]
On Beh
On Sun, 7 Apr 2013, Robert Hajime Lanning wrote:
Date: Sun, 07 Apr 2013 04:03:52 -0700
From: Robert Hajime Lanning
To: LOPSA Tech
Subject: Re: [lopsa-tech] how to do multi-zone WiFi with stock Linux?? was Re:
Wifi
On 04/07/13 02:34, David Lang wrote:
So, I had a couple of hours of solo
> From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org]
> On Behalf Of David Lang
>
> Ahh, but if they keep the same SSID, and the APs are bridged with DHCP
> being
> handled at some central server (not on the individual APs, then moving from
> one
> AP to another is just dis-as
> From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org]
> On Behalf Of David Lang
>
> why does the movement of users matter much?
If you associate to an AP because it's the closest to you, and then you move
away from it, your computer has to "scream louder" so the AP can hear
On 04/07/13 02:34, David Lang wrote:
So, I had a couple of hours of solo driving tonight and started thinking
about this more.
Thinking about it, if your users are very mobile, I think it's probably
better to try and have everything bridged (tunneling things back and
forth is extra overhead.
Bu
On Sat, 6 Apr 2013, Matt Simmons wrote:
Apologies for not recognizing your name. Of course none of that was new to
you. But of course, you also know about the enterprise wifi solutions with
tunneling and handoff, so I'm not sure what we're even discussing anymore
:-)
No problem, I deliberatly
On Sat, 6 Apr 2013, David Lang wrote:
On Sat, 6 Apr 2013, Matt Simmons wrote:
how large do you need to be fore this to break? I've done this at
conferences with over 2000 people, 40 APs across a large hotel. >There were
no signs of problems. I'm interested to learn what problems to look for.
duh, that's right, 802.11x and 802.1x I wasn't remembering them.
David Lang
On Sat, 6 Apr 2013, Frank Bulk wrote:
Because the Wi-Fi authentication happens *before* the IP address is handed
out.
Frank
-Original Message-
From: David Lang [mailto:da...@lang.hm]
Sent: Saturday, April 06,
13 matches
Mail list logo
