RE: [smartBridges] Strange

[Seeni Mohamed]

Hi Scott,   If you set the aBT with static IP, there is no way can get the DHCP IP (where clients supposed to receive) even if disassociates and re associates again. We have not observed or encountered this symptom before, because it works very well with fixed IP address. Did you see this symptom with one particular unit or any other ABTs?  How old is the aBT unit?   If this is the case, please use the simpleDeploy or recovery utility to re calibrate the device to the factory default parameters.  Using simpledeploy or recovery utility will RESET the device to default configuration and you need to re configure the unit again. Then configure the unit as before and please monitor the symptom whether it behaves as same or not.   In order to establish better link, you have to bring up the RSSI and LQ level about 75%.   Please test it and update us the status.   Best regards, Seeni sB Tech support [EMAIL PROTECTED]   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of shoffman Sent: Thursday, October 09, 2003 11:26 PM To: [EMAIL PROTECTED] Subject: [smartBridges] Strange   Forgot to take pics so I could attach, but here is a problem I am seeing (one of many with this equipment).   Have a Cisco AP352 with power amp on towers, using ABTotals as clients.  The AB sees the Cisco fine (-55 dbm) and the Cisco sees the AB ok (Signal Quality is 35%-40% yes we have some interference...., but still this is about a -70 to -77 dbm)  and besides, that isn't what I am here to discuss....   We have patched with new firmware all of our equipment.  And I double checked this one.  We gave the SBTotal a static IP (192.168.101.14)...  subnet 255.255.255.0, default gateway 0.0.0.0.  Everything was honky dorey, till I changed it from hard coded ESSI and BSSI codes to a roaming ESSI only (no BSSI)....  it disassociated, and re-associated (saw on Cisco logs).  But when it re-associated, it came back with a public IP address that only my clients PC's should be receiving (I have a DHCP server dishing those out).  And now I am going to have to create a new tunnel through my front end on that subnet so I can talk to the device (pain in the ars..), also all my monitoring and keep alive systems for the device has just gone to sqwuat.    I have noticed public IP's on associated devices before, but I had always thought, oh...  my tech forgot to set it, or forgot to upgrade, or somehow the Cisco is seeing the IP of the clients PC.. but now I am sure that the frickin' Airbridge device ignored the static IP and pulled a DHCP lease (checked the logs.,. tada there is its MAC address).  This could explain ALLOT of my customer issues since we all know these devices disassociate unless you keep them alive, and all my keep alives are based on private IP's....   I haven't heard anything from SBTech on this forum lately, but their input (or flat out denial) would be of interest...   Scott   ----------ANNOUNCEMENT---------- Don't forget to register for WISPCON IV http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm   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