Virus Propagation Guideline
RUWireless and RUWired 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 or RUWired of their "infected" status. It is the responsibility of the user to notify RUWireless/RUWired 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 and RUWired.
Bandwidth Utilization Guideline
RUWireless uses a relatively low bandwidth technology, 802.11g/a, that only supports approximately 20 Mbps of shared bandwidth per wireless access point. Therefore, a QOS (quality of service) restriction is imposed on all users of RUWireless. This QOS restriction limits a host to 1 Mbps of sustained throughput. While this may seem a bit restrictive, realize that RUWireless is meant to provide convenient access to RUNet, it is in no way meant to replace the 10/100 Mbps wired access available at most desktops. If there were no QOS restriction it would also be possible for a single user to sit very close to a wireless access point and consume a very large portion of the available bandwidth. RUWired also employs similiar QoS restrictions to ensure good network speed for all users.
It is also necessary for RUWireless and RUWired to limit how much bandwidth a host consumes over a period of time. This limit is more a matter of conserving Internet hand-off bandwidth than a user QOS issue. Since users are encouraged not to use RUWireless and RUWired for high bandwidth purposes the limit is set at 4,000 MB within a 7-day rolling window. It should be noted that this limit is set purposefully high, so there will be no exceptions made to this policy. Access will be restored the first day that the 7-day rolling window is below 4,000 MB.
BACK TO TOP
