University Wireless Policies
University Policy on Deployment, Operation, and Registration Requirements for Wireless Access Points on PennNet states that unauthorized APs are not permitted in areas where AirPennNet is in operation. End users may request permission to install privately-owned APs in areas not serviced by AirPennNet. However, they must first register each device with ISC N&T. Please read further for more detailed information.
Wireless LAN Registration Required
ISC Networking & Telecommunications has established registration requirements for campus wireless APs in areas where AirPennNet is not in operation. Registering privately-owned APs allows ISC N&T to record and track the use of the unlicensed frequency range utilized by various wireless services and to coordinate the deployment of these APs to avoid situations in which local configurations result in frequency range conflicts that directly impact service to users. To comply with the University policy registration requirements, you can register your school/center's wireless LAN online. Please note that ISC N&T reserves the right to remove these wireless devices at a later date if AirPennNet is expanded into this same location.
To learn more about University policies that influence wireless
services on campus, click on the policy links below.
Policy on Deployment, Operation, and Registration Requirements for Wireless Access Points on PennNet
This policy specifies the requirements for Wireless Access Points (APs) and related wireless LAN infrastructure operating on PennNet. It also provides related "best practice" recommendations.
Policy on Requirements for Authenticated Access at Public Jacks, Public Kiosks,
Wireless Networks, and Lab Computers on PennNet
This policy specifies authentication and accounting requirements for
access to PennNet from locations or devices that are not directly associated
specific individual Penn user. Primary examples are access to PennNet from public
jacks, public kiosk computers, wireless networks, and lab computers. This policy
document also provides related "best practice" recommendations on configuration
decisions associated with authentication and accounting.