Skip to main content

RUWireless policies

Policies and guidelines

Use of RUWireless is governed by the Rutgers Acceptable Use Policy, policies specific to Office of Information Technology systems and the RUWireless Virus and Bandwidth Guidelines. By using our networks you agree to follow these policies and be responsible for any failure to do so. It is solely the user’s responsibility to familiarize themselves with and adhere to the policy that is linked below.

By using the unsecured RUWireless network, you acknowledge that it is possible for personal information to be compromised while being transmitted. Rutgers University cannot be held responsible for any resulting loss or damages and, as such, RUWireless encourages its users to utilize secure services when accessing network resources wirelessly.

If you wish to use RUWireless with encryption, please click here to set up RUWireless Secure.

Virus propagation guideline

RUWireless networks are monitored for virus like activity automatically. Certain virus propagation techniques are scanned for and if detected are logged. The user of the offending host is then blocked from transmitting data until either the suspect activity can be explained or disinfection can be proven. Users are automatically notified when they attempt to log in to RUWireless of their “infected” status. It is the responsibility of the user to notify RUWireless administration when they are informed of their “infected” status, no attempt will be made to notify users by any other means.

It should be noted that certain seemingly harmless hacking attempts, such as, port scanning or ping flooding a host can be mistaken as virus propagation and will result in a loss of privileges on RUWireless.

Bandwidth Utilization Guideline

Bandwidth that passes though RUWireless and RUWireless Secure is dynamically allocated based on the combined usage of all clients. This approach generally results in higher network speeds than the previous limit of 3Mbps per host. The Internet bandwidth allocated to RUWireless is capped at 2Gbps however internal University traffic is not metered.

The system passively monitors network throughput when traffic is light. The system issues per connection penalties as the overall usage approaches its limit based on the the duration of each connection, a device’s bandwidth consumption and the number of active connections. The longer-term, large consumers of data are more likely to be penalized when utilization is high, while bursty traffic, such as voice, email and web browsing, will be given priority. The system does not inspect the payload of the traffic that passes through it at any time in this process.

This is still a best effort technology. Actual network speeds will vary based on a number of factors including the model of access point, client device, client load on the local access points, interference, overall network congestion and remote server.

We are evaluating this approach on the New Brunswick/Piscataway campuses now and hope to employ it elsewhere in the future.