Alex, I know it may seem hard to believe, but this is exactly what is happening to my customers. And in three of the four cases I guarantee you the customer is not changing the ESSID from logan-wt to the gibberish that I find when I arrive on site. And the fourth person, while I wouldn't bet my life on it, I'd bet a considerable amount of money he's not changing it either. (When I dropped into a DOS prompt he thought his monitor was going out since part of the screen turned black). So I am closer to 100% than 99% certain that he's not changing it.
One is using Windows 95 (I know...supposedly not supported but it does work. I have three customers using it, and the other two are fine, but going off a different AP. The simplemonitor software won't run on it, but the airbridge works with it.) So I know she's not changing the ESSID. I set it for her using my laptop. The firmware is 1.50. One is using Millenium. She doesn't have the SB software on her PC. So I know she isn't changing the ESSID. Again, I set this with my laptop, firmware 1.50. One is using Windows 98 SE. He has the software but doesn't have a clue how to open it or log into the AB. He also hae 1.50 firmware. And the last guy is using a Linksys router on a Macintosh network. He obvisouly doesn't have the software on there either. So he's not changing the ESSID. I had 1.50 firmware on him, but have backreved him to 1.43. We're monitoring that to see if that fixes it. (This guy is using and ABO. The other three are using airbridge indoor units. All four of these people are on the same access point. None of the people on my other access point have ever had this happen. All of these people have great LQ and RSSI. (People with far less LQ and RSSI are not seeing this.) If I have to roll back to any of these sites again I'll take the 1.43 firmware with me and backrev it to see if that's what's causing it. I doubt that it is however as their are customers on my other AP that are using 1.50 and not seeing this. I'm thinking it's got to be something inside the indoor airbridges that cause this. If the customers were to power off their airbridges each night, that shouldn't hurt anything, should it? Should I tell them to leave them on all the time? (Many of them might, but they aren't going to leave their PCs on. And i wouldn't think they'd need to leave the airbridges on either, but I thought I'd ask. Thanks Sam On Wed, 25 Jun 2003, sB Tech Support wrote: > We do not see the logic or any possibility that the ESSID could be > changed by itself without anybody changing its conifg, either possible > of hacking or the security being compromised. But still we will do a > research on this. > > About the inactivity for 5 minutes, after the client devices associated > with an access point, it monitors the signal strength and the traffic in > order to keeps the link going. When there is no traffic passed between > the client devices and the access point for more than 5 minutes, the > client device becomes idle but REMAIN associated. Once the traffic is > kicked in, it will "wake up" again and start talking to the access > point. > > During this re-initiation process with the access point if the RSSI and > Link Quality is not sufficient enough to establish the link it will > disassociate with the access point and search for a better signal, but > eventually will associate to the access point. > > Alex > sB Tech Support > > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of shoffman > Sent: Wednesday, June 25, 2003 12:29 AM > To: '[EMAIL PROTECTED]' > Subject: RE: RE: [smartBridges] Weird Characters in ESSID and > Lossofassociation > > > Alex, > > This is what we were told before. We monitored the association from the > > Cisco AP. As I stated, we did see it dis-associate, and y'all > (SmartBridge tech Support) confirmed that inactivity for a period of 5 > minutes will cause the unit to disassociate. > > The ESSIS was always hard-coded, and the BSSID was set both to 0000000 > (however many) and with Hard code of the BSSID for the AP. Issue > persisted in either case. So we implemented the pings, and that cleared > > up the problem. We are now doing SNMP monitoring of the untis and have > sinced turned off the pings (the SNMP gets are keeping the connection > alive...) > > Scott > > > -----Original Message----- > From: "Alex Wong" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Date: Tue, 24 Jun 2003 19:36:26 +0800 > Subject: RE: RE: [smartBridges] Weird Characters in ESSID and Loss > ofassociation > > > Scott, > > > > When client computer turned on, how do you tell the association is not > > > there? If the TXRX LED is solid, it is indicating associated. Can > > check them out of happen again? Also, do you hardcode the ESSID, or > > set as ANY? If it is any, the airBridge can associate to any AP. When > > the problem happen, does anybody does the restore to default causing > > the ESSID to ANY (unless you have used simpleDeploy for default > > config). > > > > If the problem persists, please let us know and I would like you to > > send > > to us directly for analysis. > > > > Alex > > sB Tech Support > > > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of shoffman > > Sent: Tuesday, June 24, 2003 12:49 AM > > To: '[EMAIL PROTECTED]' > > Subject: Fwd: RE: [smartBridges] Weird Characters in ESSID and Loss > > ofassociation > > > > > > > > Alex, > > > > Agreed on power supply, especially in light of the Onion report. We > > have 50 installed from that batch you guys are dealing with. We > > haven't had any "total" dead, but one may have a heat problem. > > (replacing it today... stays good for about 60 minutes, then looses > > association. > > Restart, nothing. Turn it down.. wait about 10 minutes.. turn-up, > > bang, > > back on air.. for about 1 hour or so... (some times shorter). We > > will > > do some in house checking before we attempt an RMA...) > > > > But back to the original, We have done our best (except putting a UPS > > or > > > > larger power supply on the power shot)to clean up the power, but given > > > it > > is a rural install, power may not be totally clean. But what leads > us > > to our theory is that this only happened when the client computer was > > turned off at night (or during the day). The AB was never pwoered > > off, > > > > but when clients computer turned on.. Association was not there. We > > go out and reset the jibberish in the ESSID, and walla, back up and > > happy. > > > > Again, another point leading us to believe our theory is that since we > > started the pining (3 weeks ago) we have never heard from client again > > > (i.e. its staying solid...) So... go figure. > > > > Scott > > > > > > -----Original Message----- > > From: "Alex Wong" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Date: Tue, 24 Jun 2003 00:17:51 +0800 > > Subject: RE: [smartBridges] Weird Characters in ESSID and Loss of > > association > > > > It could be the noisy power source or some spike that cause the memory > > > to corrupt. Check if there is proper grounding and clean power supply. > > > > Alex > > sB Tech Support > > > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Sam > > Sent: Monday, June 23, 2003 3:04 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: [smartBridges] Weird Characters in ESSID and Loss of > > association > > > > > > No, this isn't what happened. There is no software on these computers > > for the person to be able to log into the airbridge with. I have to > > take my laptop to them and login to the AB and reassociate it myself. > > > > Can anyone at SB shed light on this? > > > > Thanks > > Sam > > > > > > On Mon, 23 > > Jun 2003, phantam wrote: > > > > > I HAVE seen this whenever I do a remote essid change and it fails, > > > maybe the text isn't being sent properly but in this case it messes > > up > > > > > quite often. Once it messed up and I could swear it was screwed up > > but > > > > > they reset it and it associated properly I don't know if it just was > > > > sent properly but not associated or it's a messed up command that > > > the unit has to be rebooted after a essid change and it doesn't do > > > it properly. > > > > > > What could this be seeni? > > > > > > Chris > > > > > > -----Original Message----- > > > From: George [mailto:[EMAIL PROTECTED] > > > Sent: Monday, June 23, 2003 1:32 AM > > > To: [EMAIL PROTECTED] > > > > > > One thing I don't do, is install any utility that allows them to get > > > > involved in any way with the radio gear. The less they know the > > better > > > > > we all are. Of course we always retain ownership of the radio. I > > > even do that with the gateway router in most cases, even though they > > do > > > buy that from me. > > > In most cases all we have to do is tell them to reboot their pc, > > gateway > > > router, or radio when they stop working. > > > George > > > > > > ----- Original Message ----- > > > From: "Tom Andrews" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Sunday, June 22, 2003 9:28 PM > > > Subject: Re: [smartBridges] Weird Characters in ESSID and Loss of > > > association > > > > > > > > > > Have you seen an AP with the ESSID of ZUCimkXZ while doing any > > > > installs or war driving? Do these customers who had issues have > > > > access to > > > simpleMonitor > > > > and if so are they the type who might have played with the radio > > > > in an attempt to "fix" the connection? > > > > > > > > I have one who thinks they know more about our system than we do > > and > > > > > > they are always causing me issues by screwing around with all > > > > their settings. They are not using anything from smartBridge, but > > > > another radio I no > > > longer > > > > use. I guess I don't charge enough to go clean up their messes > > > > when they > > > get > > > > good and drunk. > > > > > > > > Tom > > > > ----- Original Message ----- > > > > From: "Sam" <[EMAIL PROTECTED]> > > > > To: <[EMAIL PROTECTED]> > > > > Sent: Sunday, June 22, 2003 23:28 > > > > Subject: [smartBridges] Weird Characters in ESSID and Loss of > > association > > > > > > > > > > > > > Tonight I went to two of my customer's homes to re-associate > > their > > > > > > > airbridges. When I got there the ESSID had changed from logan-wt > > > > > > to something like ZUCimkXZ and the BSSID was all zeros. Earlier > > > > > this > > > weekend > > > > > another customer with an airbridge outdoor had the same thing > > > > > happen. > > > His > > > > > ESSID changed from logan-wt to some jumble of letters. > > > > > > > > > > Got any idea what is causing this to happen? There are about 30 > > > > > people > > > on > > > > > that AP (logan-wt). All three of these people are on the > > > > > logan-wt AP. As far as I know they are the only three that lost > > > > > association, but this is the third time in a month or so that > > it's > > > > > > > happened. Are these defective Airbridges? Their RSSI is > 50% > > > > > and the Link quality is close to 80%. > > > They > > > > > are at most six miles from the AP, and one of them is only a > > > > > couple of miles away from the AP. > > > > > > > > > > Should I get an rma for these or do you think there is something > > > > > > else causing this? They are all using 1.50 of the firmware, > > though > > > > > > > I did have the man with the outdoor airbridge backrev to 1.43 to > > > > > > see if that will help. > > > > > > > > > > Thanks > > > > > Sam Morris, Owner > > > > > Loganet Internet Service > > > > > Logan IA > > > > > > > > > > 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://198.63.203.6 > > > > > > > > > > > > > > > > > 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://198.63.203.6 > > > > > > > > > > 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://198.63.203.6 > > > > > > > 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://198.63.203.6 > > > > 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://198.63.203.6 > > > > 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://198.63.203.6 > > > > 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://198.63.203.6 > > 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://198.63.203.6 > > 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://198.63.203.6 > 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://198.63.203.6
