Mike, > How are you able to get faculty/staff to move off dependencies on L2 > printing, SMB shares, etc? and onto L3 based services? Is there general > acceptance of wireless services vs. wired services?
We have declared ourselves as IP only. (part of a redesign of our network back in 2000, named VolNet... Dewitt Latimer made this happened on our campus) > Do you restrict any protocols/services on the wireless network in an > academic building? Not really. As far as layer2 protocols, people can share all they want within the layer 2: Itunes: quite a bit of multicast!!! , SMB:a broadcasting nightmare, etc... If the broadcasting gets out of hands we might filter SMB and others. Why do people need layer2 to communicate with servers or printers? That sounds very IPX, Ethertalk to me! > Does offering wireless users the same subnet/vlan as the building wired > network makes sense or is it a bad idea? Are there dhcp lease issues > betwwen wired and wireless users? Well wired ports are predictable (we have a semi-zero private hub/switch policy as well, that helps)as far as the number of connectors (IP addresses), Wireless is not. If you have 10 Access-Points, 200 or so people could join it. We are not talking bandwidth here. Just number of IP addresses. So how will you design your subnet? A lot of wasted IP addresses. If you NAT everything, it doesn't matter, but we don't! You have to look at your buildings and decide what's best, but we have been very pleased with our large layer2 design. We recently deployed a Controller Based Architecure in our dormitories, and, though it facilitates the management a lot, I sometimes regret this decision...time will tell. You also have to trust your wireless very well to make it part of the wired subnet (holes!). Also, how will you provide visitor access? > There appears to be a lot of local sharing and low-cost (non-L3) > printing going on in departments. It's unclear what effect adding > wireless coverage with no L2 connectivity will have on these departments. Take a hard stand, IP only, you will not regret it. I saw Vint Cerf with a T-shirt that says: IP on everything... Philippe > Thanks! > > Mike > > *************************************************************** > Michael Dickson Phone: 413-545-9639 > Network Analyst [EMAIL PROTECTED] > University of Massachusetts > Network Systems and Services > *************************************************************** > > Philippe Hanset wrote: > > Michael, > > > > One of the caveat of mixing wireless and wired on the same VLAN > > for a builing is IP contention. Your number of wired ports is fixed, your > > number of clients on APs can vary greatly. You will have to redesign the > > IP assignment of all those wired networks! > > What's wrong with IP printing or even Netbios over IP ;-) > > If you move to a Centralized Wireless Architecture, that Wired/Wireless > > separation gets exacerbated even more! (IP tunnels back to the > > controller!) > > > > Philippe Hanset > > > > ---------------------------------- > > Philippe Hanset > > University of Tennessee, Knoxville > > Office of Information Technology > > Network Services > > 108 James D Hoskins Library > > 1400 Cumberland Ave > > Knoxville, TN 37996 > > ---------------------------------- > > > > On Thu, 4 Oct 2007, Michael Dickson wrote: > > > >> Hi all, > >> > >> We currently put all wireless clients into a unique set of wireless-only > >> vlans. As we expand our coverage into more staff/faculty areas on > >> campus, however, we are start to get the same questions surrounding > >> layer 2 connectivity. > >> > >> Specifically, clients want to print to their local printers and access > >> their local shares on devices which reside on their building's wired > >> infrastructure, but connect their laptops via wireless while in the > >> office. Novell, AD, local shares, shared L2 local printers, etc., all > >> face the same issues. > >> > >> From an IT perspective this could be seen as a feature, but I'm not > >> sure the clients are agreeing. How are others dealing with L2 > >> connectivity issues? We are not sure if simply putting the SSID in the > >> building native 'wired' vlan is the best practice. Telling them to "plug > >> back in" isn't getting a lot of traction, either. > >> > >> Thanks, > >> Mike > >> > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> Michael Dickson > >> Network Analyst > >> OIT - Network Systems and Services > >> University of Massachusetts Amherst > >> > >> ********** > >> 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/. > > ********** > 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/.
