If I recall, the cost of the Airpoint indoor and Outdoor are about the
same.

Scott

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Sent: Wednesday, August 13, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: [smartBridges] Question about new aP firmware coming out
soon.


They will be outdoor in a NEMA box.  That is why disabling of
communication between clients is needed.  As I mentioned, the cost of an
aPPO coupled with the un-availability of them, forces me to go this
route.  If the rated specs on the data sheet for the aP is correct, then
the climate where I live is within range for operating temps and this
approach will work just fine. That is my application.


----- Original Message ----- 
From: "Jason" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 13, 2003 12:29 PM
Subject: RE: [smartBridges] Question about new aP firmware coming out
soon.


I mean you no offense, but why would you need to disable communications
amongst clients at the same location? I assume you are using these as
indoor access points for businesses/homes. I have never heard of a
requirement like this. Maybe we are missing something here. What is your
application?

Jason

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Scott
> Sent: Wednesday, August 13, 2003 3:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [smartBridges] Question about new aP firmware coming out 
> soon.
>
>
> No, I am talking about the access point.  The aP will be used as an 
> access point that's why the ability should be there to disable 
> client-to-client communication.  Cost and availability of the aPPO 
> prevent me from using them (I'm small peanuts).
>
>
> ----- Original Message -----
> From: "Jason" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, August 13, 2003 12:08 PM
> Subject: RE: [smartBridges] Question about new aP firmware
> coming out soon.
>
>
> I think you only need to disable the client to client communications 
> from the access point. This setting does not make a difference on the 
> airPoint on the client end... Is this what you are talking about?
>
> Correct me if I am wrong.
>
> Jason
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On Behalf Of Scott
> > Sent: Wednesday, August 13, 2003 3:00 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [smartBridges] Question about new aP firmware
> coming out
> > soon.
> >
> >
> > I'm REALLY sorry to hear that.  May I ask why something so
> simple to
> > implement and widely requested/needed would not be added?
> Is it more
> > of an effort to force people to upgrade to the aPP or aPPO for that 
> > kind of capability?  Since the aPPOs are so hard to come by, I'm 
> > forced to use the aP to get customers up and running (if I want to 
> > stick with sB anyway). However, I will probably have to rethink my 
> > plan since something so simple to implement will not be
> added to the
> > FW.
> >
> > Dissappointed,
> > Scott
> >
> >
> > ----- Original Message -----
> > From: "sB Tech Support" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, August 13, 2003 11:45 AM
> > Subject: RE: [smartBridges] Question about new aP firmware coming 
> > out soon.
> >
> >
> > This must be everyone wish but unfortunately it won't have
> the feature
> > to disable client to client communication. There is no plan
> to have it
> > on airPoint Indoor. The new firmware that is going to
> release is for
> > resolving the thermal issue.
> >
> > Alex
> > sB Tech Support
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott
> >
> > Sent: Wednesday, August 13, 2003 10:54 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: [smartBridges] Question about new aP firmware coming out 
> > soon.
> >
> > Will the new firmware version support disabling client-to-client 
> > communication?  That's about the only thing I can think of that I 
> > would really like to see in the new aP firmware.
> >
> > The PART-15.ORG smartBridges Discussion List
> > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe 
> > smartBridges <yournickname> To Remove:
> mailto:[EMAIL PROTECTED] (in the body type unsubscribe
> smartBridges)
> Archives: http://archives.part-15.org
>
> The PART-15.ORG smartBridges Discussion List
> To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe 
> smartBridges <yournickname> To Remove:
mailto:[EMAIL PROTECTED] (in the body type unsubscribe
smartBridges)
Archives: http://archives.part-15.org



The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in
the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org

The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in
the body type unsubscribe
smartBridges)
Archives: http://archives.part-15.org



The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in
the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org

The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in
the body type unsubscribe
smartBridges)
Archives: http://archives.part-15.org



The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in
the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org  


The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges 
<yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org  

Reply via email to