Skip to content

Network & Internet Access

CTS works with the Drexel IT Networking group to manage physical networks in Engineering classrooms, labs, and offices. We are also able to pass along concerns about wireless signal strength and throughput.

Wireless Networks

Drexel IT Networking provides information and instructions for connecting a wide variety of devices to Drexel's wireless networks.


All faculty, staff, students, and researchers with valid domain account credentials should use the Dragonfly3 wifi network. Manual and automatic configuration options for a variety of operating systems are available here.


Basic internet connectivity for visitors is provided via the DrexelGuest network. Users connecting to this network must open a web browser to accept terms and conditions before they are allowed general internet access. Devices connected to DrexelGuest will not be able to access most Drexel network resources.


Members of the Drexel community visiting other schools may be able to access the EduRoam system. Participating colleges and universities provide wireless access via a shared authentication system, so that Drexel users may connect using their credentials. EduRoam configuration utilities are available for a variety of computer and mobile operating systems.

Manual Eduroam connection settings
Setting Value
SSID eduroam
Phase 2 Auth MSCHAPV2
CA Cert Default or Use system certs
Anonymous identity leave blank
Password your Drexel password

Make sure to replace with your own Drexel account name.

Other Wifi Networks

dragonfly is considered a legacy network for devices that don't support WPA2 & 802.1X authentication. You should consider traffic on this network to be functionally unencrypted, and should avoid using it when possible.

dragonfly-play is available in and around the residence halls for connecting entertainment devices such as smart TVs, video game systems, wireless AV, etc. The network is open and unencrypted.

Ethernet Jacks

CTS manages Ethernet jack activations for Engineering rooms. For inactive jacks, Drexel IT Networking charges $150 per 1Gbps port activation. If you need new Ethernet jacks installed, please contact us so we can have Drexel IT Networking prepare a quote (on the order of $1000).

VPN Access

Many computing resources within the College of Engineering are available from off-campus by connecting your computer to Drexel's Virtual Private Network (VPN) service. Please visit this page for more information and connection instructions.

IP Addresses

Aside from web servers that require the ability to serve pages to the world, we recommend that all servers and workstations be connected to Drexel's private RFC1918 networks to prevent direct access from external networks. IP addresses on these networks will appear as 10.x.x.x.

IPv6 Networks

We do not currently use IPv6 addresses for any purposes. Certain functions in Windows require that IPv6 be enabled, even if it is not actively used. Fully disabling IPv6 is not recommended.

Requesting a static IP address and hostname

CTS submits and tracks all requests for hostnames and static IP addresses as required for various computing needs. If you need a static IP / DNS entry for a host on the wired network, please contact us. Drexel Networking does not allow static IP addresses or custom hostnames for devices connected to the wireless networks.

The College of Engineering maintains multiple subdomains, including:

  • (College of Engineering)
  • (Civil, Architectural, and Environmental Engineering)
  • (Chemical & Biological Engineering)
  • (Electrical & Computer Engineering)
  • & (Materials Science & Engineering)
  • (Mechanical Engineering & Mechanics)

Network Policies

Acceptable Use Policy

All use of Drexel's networks is subject to Drexel's Acceptable Use Policy (AUP). In addition to specific guidelines covering Access Requirements, Prohibitions, and Monitoring, the general guidelines for acceptable use of the Drexel Network are based on the following principles:

  • Users must behave responsibly with respect to the Drexel Network at all times.
  • Users must respect the integrity and the security of the Drexel Network.
  • Users must behave in a manner consistent with Drexel's mission and comply with all applicable laws, regulations, and Drexel policies.
  • Users must be considerate of the needs of other Users by making every reasonable effort not to impede the ability of others to use the Drexel Network and show restraint in the consumption of shared resources.
  • Users must respect the rights and property of others, including privacy, confidentiality and intellectual property.

As part of Drexel's Data Security Initiative, all data entering or exiting Drexel's networks travel through a Palo Alto firewall designed to scan for and block potentially malicious activity. As stated on Drexel IT's information page linked to above, this border firewall is a supplement to, not a replacement for, recommended security practices.

"Rogue" Wifi Networks

The Drexel Networking group forbids the use of any networking equipment, wireless or otherwise, that affects the operation of Drexel networks. Please do not run wireless routers or wireless presentation devices without first contacting us so we may assess the need and request a possible waiver from Networking.

Disconnecting suspect devices

The Drexel IT Networking team uses various methods of monitoring the network for devices exhibiting malicious behavior, which will lead to the wall Ethernet jack the device is connected to being disabled. If you are using a switch to connect multiple computers to a specific wall jack, all of the devices connected to that switch will also lose connectivity.

If you find that a network jack used by your device has been disabled, please do not attempt to move it to a new jack -- this will result in the new jack being disabled as well. Please contact CTS so we may assist with whatever remediation is required by Networking to allow the device back onto Drexel's network. Depending on the severity and cause of the device being blocked, potential steps may include thoroughly scanning and removing the cause of the behavior (if possible), recovering the device from a backup taken before infection, or a full reinstall of the device's operating system.