More germane to the subject, I meant to add that we began to upgrade to
6.0.182 since released without issue.  I've a handful of APs using HREAP on
these controllers (traffic is locally switched) as well.

--
Garry Peirce   
Network Analyst,  ITS
University of Maine System


> -----Original Message-----
> From: The EDUCAUSE Wireless Issues Constituent Group Listserv
> [mailto:[email protected]] On Behalf Of Garry Peirce
> Sent: Thursday, August 20, 2009 6:28 PM
> To: [email protected]
> Subject: Re: [WIRELESS-LAN] WiSM 6.0.182.0
> 
> Might you have proxy-dhcp enabled (is by default) on the controllers?
> I ran into bug CSCsx96815 when I went to 5.2.157 in the past which
> caused
> clients to not receive an address (the virtual address was corrupted
> through
> an upgrade).
> 
> --
> Garry Peirce   +1-207-561-3539
> Network Analyst,  ITS
> University of Maine System
> 
> 
> > -----Original Message-----
> > From: The EDUCAUSE Wireless Issues Constituent Group Listserv
> > [mailto:[email protected]] On Behalf Of Lee H Badman
> > Sent: Thursday, August 20, 2009 10:46 AM
> > To: [email protected]
> > Subject: Re: [WIRELESS-LAN] WiSM 6.0.182.0
> >
> > Peter,
> >
> > Can you describe your bus implementation in more detail?
> >
> > -Lee
> >
> > -----Original Message-----
> > From: The EDUCAUSE Wireless Issues Constituent Group Listserv
> > [mailto:[email protected]] On Behalf Of Peter
> Arbouin
> > Sent: Wednesday, August 19, 2009 11:14 PM
> > To: [email protected]
> > Subject: Re: [WIRELESS-LAN] WiSM 6.0.182.0
> >
> > Hi,
> >
> > We also upgraded to 6.0
> > We have several aps on busses using HREAP. For some reason clients
> were
> > not able to get a valid ip and we had to revert to the previous
> version
> > of code. Anyone else seen this issue?
> >
> > Another issue is some random hosts have issues getting an ip address
> by
> > DHCP in some locations, but work fine in other locations.
> >
> > The WCS interface is far better than previous versions.
> >
> > Peter.
> >
> >
> > -----Original Message-----
> > From: The EDUCAUSE Wireless Issues Constituent Group Listserv
> > [mailto:[email protected]] On Behalf Of Procyk, Ian
> > Sent: Thursday, 6 August 2009 5:11 AM
> > To: [email protected]
> > Subject: Re: [WIRELESS-LAN] WiSM 6.0.182.0
> >
> > UBC upgraded our campus (39 controllers consisting of 4402's 4404's
> > WiSM's and 5508's) on July 18th to 6.0.182.
> >
> > -We had some AP's with Static IP's that needed attention.
> >
> > -We also noticed that the wired ACL in 6.0x doesn't work - we noticed
> > this even during our 6.0 beta test.
> >
> > -AP's that were located at remote sites (via DSL/cable) that were
> > directly connected to controllers, are now having difficulty
> connecting
> > to controllers running 6.x  The solution has been to put these AP's
> > into office extend mode or HREAP mode, where the latency timers are
> > longer.
> >
> >
> >
> > Thanks
> > Ian Procyk
> > UBC IT
> > 604-827-5707
> >
> >
> > -----Original Message-----
> > From: The EDUCAUSE Wireless Issues Constituent Group Listserv
> > [mailto:[email protected]] On Behalf Of Dennis Xu
> > Sent: Wednesday, August 05, 2009 7:15 AM
> > To: [email protected]
> > Subject: [WIRELESS-LAN] WiSM 6.0.182.0
> >
> > Has anybody upgraded to WiSM 6.0.182.0? Any feedback?
> >
> > Thanks!
> >
> > Dennis Xu
> > Network Analyst
> > Computing and Communication Services
> > University of Guelph
> > 5198244120 x 56217
> >
> > **********
> > 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/.

Reply via email to