(RADIATOR) Proxim AP2000 access points ?

[Bret Jordan]

Did you reset the box to defaults and reconfigure the vlans?  The 
configuration for vlans has changed in 2.4.11 from 2.4.5.   We are 
running 802.11g and 802.11a in our APs.

Bret

Dunster, Jon wrote:

>Thanks Terry,
>
>I've just put 2.4.11 on.  The AP2000 was enabled for VLAN before .11 and it
>is still enabled - management interface is still functioning.  Perhaps its
>corrupt somewhere or a different hardware revision ?!  I've only got a 'b'
>card at the moment, waiting for a 'a/b' kit to see what happens.
>
>How about the AP4000 ?  Have you tried that ?
>
>Cheers,
>
>Jon
>
>-----Original Message-----
>From: Terry Simons [mailto:galimore at mac.com]
>Sent: 01 June 2004 23:21
>To: Dunster, Jon
>Cc: 'radiator at open.com.au'
>Subject: Re: (RADIATOR) Proxim AP2000 access points ?
>
>
>The AP 2000 APs don't support dynamic VLANs, unless something has 
>changed recently.
>
>Furthermore, the 2.3.x and higher code is broken in that if you are 
>using an 802.11g radio, your SSID will no longer broadcast if you are 
>using VLANs.
>
>Proxim claims that this is the way the code is supposed to work, but I 
>consider it a huge bug.
>
>The other issue that you'll run into is that 2.4.11 code is severely 
>broken.  Turning VLANs on breaks the management interface.  We are 
>unable to talk to the AP with anything other than ping.  (I.E. No 
>telnet or http).  I have filed this as a bug with Proxim.
>
>Hopefully that helps. :-)  If you need a more specific question 
>answered let me know.
>
>Terry Simons
>Network and Laptop Support
>Marriott Library, University of Utah
>
>On Jun 1, 2004, at 9:17 AM, Dunster, Jon wrote:
>
>  
>
>>Anyone any experience of using these with VLANs from Radiator ?
>>
>>Thanks,
>>
>>Jon
>>
>>
>>
>>-----
>>This e-mail and any attachments contain information which is 
>>confidential
>>and privileged.  The information is intended only for the use of the
>>individual or entity to whom it is addressed.  If you are not the 
>>intended
>>recipient you are hereby notified that any disclosure, copying, 
>>distribution
>>or the taking of any action in reliance on the contents of this e-mail 
>>is
>>strictly prohibited.
>>
>>--
>>Archive at http://www.open.com.au/archives/radiator/
>>Announcements on radiator-announce at open.com.au
>>To unsubscribe, email 'majordomo at open.com.au' with
>>'unsubscribe radiator' in the body of the message.
>>    
>>
>
>
>
>----- 
>This e-mail and any attachments contain information which is confidential
>and privileged.  The information is intended only for the use of the
>individual or entity to whom it is addressed.  If you are not the intended
>recipient you are hereby notified that any disclosure, copying, distribution
>or the taking of any action in reliance on the contents of this e-mail is
>strictly prohibited.
>
>--
>Archive at http://www.open.com.au/archives/radiator/
>Announcements on radiator-announce at open.com.au
>To unsubscribe, email 'majordomo at open.com.au' with
>'unsubscribe radiator' in the body of the message.
>
>  
>

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bret Jordan                       Dean's Office
Director of Networking   College of Engineering
801.585.3765                 University of Utah
            jordan at coe.utah.edu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.