24 institutions, 10,000 devices:
http://www.muniwireless.com/2009/11/10/student-use-of-80211n-twice-general-p
opulation/
Or
http://tinyurl.com/yzt87h4
Tom Zeller
Indiana University
**
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philippe Hanset wrote:
-NAT can help but logging is a pain
Just a reminder for those who use Linux routers for NAT, we
published some code to create Netflow v5 which can be very effective
for tracking and tracing user activity.
Thanks for the information, Brandon. This brings up an interesting question we
wrestle with: we find Apple to be almost impossible to engage reliably and
regularly to try to get feedback to. Does anyone have any better luck, and if
so, how do you do it?
We have 45% Apple wireless clients,
I applied this update to a Mac as a test client today, and I can confirm that
it's still experiencing the same issue as it was pre-patching. Interestingly
enough, toggling on broadcast of the SSID results in the client connecting
immediately. Disable Airport, disable broadcast, re-enable
Lee,
Open a Apple developer-select account (I think it's $500 a year). That gives
you access to OS seeds as well as the ability to submit bugs. With the ability
to submit bugs, you could open a case for your wireless issues and then work
with Apple developer support on a fix.
Additionally,
