We have 3 vlans for wireless, one for secure that requires a login, one
for helping students setup the secure connection, and one that is open
for guests. All 3 vlans are available across campus.
We use 1/4 Class B pools.
DHCP lease is for 12 hours.
We allow roaming all over campus.
We use an ASA for NAT and keep logs. If we have an abuser we search the
NAT logs for to find how had the lease.
If we the NAT pool gets full and we PAT, then we can not find the
abuser. So far this has never been an issue.
Kevin McCormick
uTech Network Services
Western Illinois University
On 5/5/2015 10:19 AM, Legge, Jeffry wrote:
Currently we allow roaming over our entire campus. Some buildings have their
own vlan while others do not. Each year we have more devices and thus our DHCP
pools are stressed. We are looking at changing our network design and giving
each building their own vlan and larger DHCP pools. We currently have a class B
IPV4 internet addresses and will move to NAT. When students are abusing
copyright etc. we are given an IP address and asked to determine who is doing
the abusing. As students roam they could end up with multiple IP addresses and
Natting will complicate the ability to find these abusers I am curious about
the following.
Do y'all have one vlan per building?
How large are you DHCP pools?
What is the pool expiration time?
Do you allow roaming over entire campus, per building or what?
How do y'all find these abusers?
Any thoughts will be appreciated.
-Jeff Legge
Radford University
540-250-5224
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
