Please reference: http://news.cnet.com/8301-1035_3-20020539-94.html
Anyone contemplating useful ways of employing this, policy re-writes to ban it
(perhaps in admin areas), or anything in between?
-Lee Badman
**
Participation and subscription information for this EDUCAUSE
Was wondering how many other folks have run into the Android device/DHCP issue
well summarized by the Princeton folks
(http://www.net.princeton.edu/android/android-stops-renewing-lease-keeps-using-IP-address-11236.html)
and what folks were doing about this.Rather surprising that it's still
And you though ad-hoc networks created inference issues.
On 11/16/2010 1:48 PM, Lee H Badman wrote:
Please reference: http://news.cnet.com/8301-1035_3-20020539-94.html
Anyone contemplating useful ways of employing this, policy re-writes
to ban it (perhaps in admin areas), or anything in
On Nov 16, 2010, at 2:10 PM, Gogan, James P wrote:
Was wondering how many other folks have run into the Android device/DHCP
issue well summarized by the Princeton folks
(http://www.net.princeton.edu/android/android-stops-renewing-lease-keeps-using-IP-address-11236.html)
and what folks
Our Athletic department provides communication for coaches during
football games via wireless headsets made by a company called Coachcomm.
Their systems work on the 2.4Ghz and use FHSS. Even though Coachcomm
claims that their systems (Tempest NG) play nice with WiFi, we've found
up to 50%
