Hi Jeff,
You know your layout and usage patterns best but for mobile users, my
two cents would avoid vlans by location. Just to much movement: mobile
devices moving between living areas, Libraries, dining halls,
auditoriums, stadiums, academic areas, etc. High numbers in one area,
then off to another! :-)
We have twelve /21 dhcp pools with one hour lease, mapped to main SSID,
not currently using NAT.
Roaming overall works well, did see improvement when enabled 802.1k,
noticeable less churn on the dhcp pools.
best!
jim
On 5/5/2015 11: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/.
