You are correct. In Bridge mode there is no protocol handshake so you get the maximum throughput.
The downside is that because there is no handshake, there is no information available for monitoring and management. The radios basically just blast the data over the air, with the assumption that the other side will catch it. Nish -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Moreno Sent: Saturday, July 26, 2003 1:27 PM To: '[EMAIL PROTECTED]' Subject: Re: [smartBridges] beta firmware for aPP series I do have one link for a remote access point set up that way and it seems to work fine but I think bridge to bridge mode is more efficient and the radios are always talking so there is no wait for other radios or any real delays etc Someone correct me if I am wrong.. Quoting Roger Hartley <[EMAIL PROTECTED]>: > I tried at first to set up a backhaul using aBOs. The advice I got when > it didn't work was use one aPPO in access point mode, another in > client/bridge. I did and it has worked fine since then. > > Martin Moreno wrote: > > > Roger, > > > > I think he is trying to setthem both into "bridge mode" as a point to point > for > > a backhaul I tried this once about a couple months ago and I too had > problems > > and could not figure it out I ended up using Motorola canopy for my > backhaul > > instead. > > When he tries it in AP client bridge mode it works fine but will not work > in > > the bridge to bridge mode like it is supposed to. > > > > Quoting Roger Hartley <[EMAIL PROTECTED]>: > > > > > >>You say you set them up as the aPPO in access point mode, the other in > >>client/bridge, then you change them. When you change them, it doesn't > >>work afer a while. Why are you changing them? It should be aPPO in > >>access point mode -> aPPO in client bridge mode. Or am I missing > >>something simple here? > >> > >>Boris Tillett wrote: > >> > >> > >>>Thank you for the beta release it was a life saver. We were in the > >>>middle of 2 deploys each with approximately 40 aPPOs. We had multiple > >>>units (about 20% or more) that were exhibiting the symptoms described in > >>>your customer advisory. Since the units were mixed in with the working > >>>units and we could not be sure which ones were in need of the fix. We > >>>upgraded all 80+ units with the new beta firmware (1.4j.8) release. It > >>>did not make sense to stand around in the hot sun rebooting them hoping, > >>>the ones that needed the fix would fail, and all that did not fail on > >>>rebooting could then be considered good, and hence be reliable for our > >>>grand opening of these networks. Anyway all 80+ upgrades went off > >>>without a hitch. The units that were obviously bad started working > >>>reliably (only been able to test for a few days) and the ones that > >>>seemed to be working fine continued to work fine. > >>> > >>>------ > >>>Again, I ask if anyone has any ideas why the point to point connections > >>>I try with the aPPOs fail with in days or sometimes hours. The units > >>>are not more then 500 feet apart, and they each have a new maxrad yagi > >>>pointing at their partner. The settings were correct or the link would > >>>not have worked at all. When I set the upstream unit to AP mode and the > >>>down stream unit to act as a client bridge the connection signal > >>>strength (~100%) could not have been better. But when I set them back > >>>to Point to Point, wireless bridge mode, the link fails with in hours. > >>>By fails I mean one side stops transmitting packets to the other side. I > >>>could initiate a successful ping only from the upstream side. This would > >>>alternate with complete failure, where I could not ping the units or > >>>through them to the units behind them in either direction. Because the > >>>units (in Wireless Bridge mode) work for a while (until they get hot), I > >>>tried the new firmware on them as well. It did not help. I have been > >>>trying to get my system administrator, who is in charge of lab testing > >>>our new equipment to set one of these links up in the lab, but he never > >>>seems to have the time. This is the third time I have tried this and > >>>after a full day of frustration in the field, have resorted to other > >>>equipment for the point to point connection. I do not need another > >>>e-mail from support asking what my setting were, if there are any > >>>setting that would work for a while and then fail please tell me. If > >>>there is a phone number for support, so we could talk while I was out in > >>>the field with the point to point failed units and try your suggestion > >>>please send it to me. The setting for this procedure, seem obvious in > >>>the documentation, and do not seem to be the problem. Any suggestion > >>>would be appreciated. > >>> > >>> > >>>Thank you, > >>> > >>>Boris Tillett > >>>Capitol Broadband > >>>(919) 674-0036 > >>> > >>> > >>>-----Original Message----- > >>>From: [EMAIL PROTECTED] > >>>[mailto:[EMAIL PROTECTED] On Behalf Of Blazen Wireless > >>>Sent: Saturday, July 26, 2003 2:45 AM > >>>To: '[EMAIL PROTECTED]' > >>>Subject: Re: [smartBridges] beta firmware for aPP series > >>> > >>> > >>>Is that for the APPO or the ABO stuff? > >>> > >>>----- Original Message ----- > >>>From: "sB Tech Support" <[EMAIL PROTECTED]> > >>>To: <[EMAIL PROTECTED]> > >>>Sent: Friday, July 25, 2003 10:04 AM > >>>Subject: RE: [smartBridges] beta firmware for aPP series > >>> > >>> > >>>Currently the firmware is for beta testing. And we are gathering > >>>feedback from users who are testing it on the field. So far we have > >>>identified a minor bug (When device in DHCP client, the Gateway is > >>>0.0.0.0 if DHCP server is not present). So please be aware that you may > >>>require upgrading again after the final version is released. > >>> > >>>Alex > >>>sB Tech Support > >>> > >>> > >>> > >>> > >>>-----Original Message----- > >>>From: [EMAIL PROTECTED] > >>>[mailto:[EMAIL PROTECTED] On Behalf Of John Banes > >>>Sent: Saturday, July 26, 2003 12:38 AM > >>>To: '[EMAIL PROTECTED]' > >>>Subject: Re: [smartBridges] beta firmware for aPP series > >>> > >>> > >>>Is this a temporary beta fix or is this an actual real release? > >>> > >>>John > >>> > >>> > >>>>Hi All, > >>>> > >>>>For all users having airPointPRO series units and which display the > >>>>symptoms described in the customer advisory we have a firmware version > >>> > >>> > >>>>1.4j.8. For those in need of it please read through carefully the > >>>>information given in the below link > >>>>http://www.smartbridges.com/new/support/beta.php. > >>>> > >>>>With Best Regards, > >>>> > >>>>Vasu > >>>>(sB Support Team) > >> > >> > >>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 > >> > > > > > > > > Martin Moreno > > Blazen Wireless > > 909-907-4106 > > www.blazenwireless.com > > 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 > Martin Moreno Blazen Wireless 909-907-4106 www.blazenwireless.com 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
