Hi folks,

When we deployed AirBears2 many people asked what our plans were for
the future of the AirBears wifi service.  Both of these networks
actually share a lot of common infrastructure, particularly access
points.  There are a few major differences between the AirBears and
AirBears2 services both in terms of infrastructure and behavior
though.  Before I explain what we are proposing, here's a brief
summary of the differences:


AirBears:
* All data is sent at the wireless layer unencrypted, in the clear.
If you are using HTTPS or other secured protocols obviously that data
is encrypted at that level, but the basic operation of the wireless
network itself does not provide any data privacy.

* Uses a web based authentication system requiring entry of your
CalNet passphrase.

* Authentication is short-lived and must be manually repeated often.

* Uses BSD based servers and custom developed software to provide
network address translation and the web based authentication mentioned
above.

* Provides users with a dedicated public IPv4 address and dedicated
public IPv6 address.


AirBears2/eduroam:

* Encrypts all data at the wireless layer.  Even if you are not using
secured protocols within applications, all data over the air has some
privacy.

* Uses standards based (802.11i) authentication, with a generated key
that is different from your CalNet Passphrase.

* Authentication is automated and devices can store credentials indefinitely.

* Uses carrier grade network address translation equipment with
superior performance and throughput compared with the AirBears captive
portals.

* Provides users with dedicated IPv6 addresses but shares IPv4 Public
addresses for all off-campus connectivity.

Because AirBears does not provide good data privacy, the ITLG feels
that it would be a good idea to abate this older network.  In
addition, the captive portal infrastructure that provides NAT and
authentication for AirBears is aging, and we no longer support the
software which it uses.  If AirBears remains, we would need to spend
some amount of time replacing this infrastructure in the near future.
We don't believe that there are good justifications for doing this
work.

We are considering abating the AirBears network as of the end of the
Spring Semester (i.e. by the end of May 2015).  AirBears2, eduroam and
CalVisitor will remain in service in their current forms.

We would like to solicit feedback from the campus IT community
regarding this course of action.  In particular, we would like to know
of any cases where AirBears is being used because AirBears2 does not
work. While its unlikely we will retain AirBears, we would like to
work with anyone who may have problems to resolve those in some way
before we abate the service.

iso


-- 
Isaac Simon Orr
Manager, Network Operations and Services
IST Telecommunications, UC Berkeley
P: +1 510 643 9837 C: +1 510 517 9408 E: [email protected]

 
-------------------------------------------------------------------------
The following was automatically added to this message by the list server:

To learn more about Micronet, including how to subscribe to or unsubscribe from 
its mailing list and how to find out about upcoming meetings, please visit the 
Micronet Web site:

http://micronet.berkeley.edu

Messages you send to this mailing list are public and world-viewable, and the 
list's archives can be browsed and searched on the Internet.  This means these 
messages can be viewed by (among others) your bosses, prospective employers, 
and people who have known you in the past.

Reply via email to