Hi Ben,
I think it is sane to assume that the IP address _should_ be the same.
The 802.11 spec expects this even. This is to handle bizarre networks
that don't do this
properly.
Can you point me to the section in the spec about this?
Lets see, 802.11-2012, Section 4.3.4.2:
"The key concept is that the ESS network appears the same to an LLC
layer as an IBSS network. STAs within an ESS may communicate and mobile
STAs may move from one BSS to another (within the same ESS)
transparently to LLC."
Section 4.5.3.2,
etc.
If not, how is this different from just re-doing DHCP like normal?
You get to use your old IP address. So e.g. your VoIP call doesn't
disappear if you decide to switch access points.
And if so, you will in some cases be allowing duplicate IP addresses on
a network?
Life is never perfect ;)
If you are breaking networks while trying to optimize something, then I
think you
are going about it wrong.
Seems like we would need some way for the DHCP server and/or AP to
proactively
notify the station that they can skip DHCP, and default to not skipping.
Not unless you're planning to extend the spec? 802.11 doesn't even
mention DHCP in any real manner.
I vaguely recall that FT had some way to verify you were roaming to the
same dhcp-domain
or not, but honestly, it has been a long time since I read through that...
Do you mean a mobility domain? This has nothing to do with DHCP...
Regards,
-Denis
