Hummmm.... Sounds just like the reason I'm sending back over half a dozen AP's directly to SB... I've been having this issue for the last month on several AP's.
Bad thing is, two of the AP's I replaced I have to now go and replace again (today). The problem with the brand new ones that I have up there now is everything starts off fine... then the LQ drops to 0% over a few hours... then it goes back to 100%... then over a few hours more it drops to 0%... The expected temp today... 100*F and humidity is already at 48%.. lovely.. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sam Sent: Thursday, August 21, 2003 11:33 To: [EMAIL PROTECTED] Subject: [smartBridges] New Problem - Not Passing Packets All the Way Here's a strange one. I've seen this with four ABI all running the new firmware. This takes a little understanding of the network layout. It's simple though. I have two access points (identified here by the last octet of their ip), .253 and .250. We'll look at .253 for simplicity. .253 connectes through a wireless link (APPOs) through a Cisco 3550, (.131) then across another wireless link (APPOs) to another 3550 (.129), then out to the Internet. .250 is also plugged into the .131 Cisco switch, then across the same link to .129 then out to the Internet. These clients (using these four ABI I'm talking about) that associate to .253, can ping .253, .131, and .250, and even other clients associated to the .253 and .250 APs. But they will not ping across the wireless link to .129. I changed the ABIs out with another one and they worked. This same behavior has happened on the .250 AP as well. Customers can associate to it and ping any ip on "their side" of the wireless link, but do not make it across to .129 to get out to the Internet. The really odd thing is that they initally do get across to .129 and beyond to .75 (the dhcp server) and get assigned an ip address. Even after they fail to travese the link, I can do an ipconfig /release then ipconfig /renew and they drop and regain an ip from the dhcp server. So they initally *can* get across the bridge. I would think it was a network issue were it not for the following two facts: 1) changing the ABI to another one fixes it, and 2) 80 other clients are working fine across the same bridge. This doesn't happen at all with any of the Teletronics clients. Thanks for any suggestions, Sam 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
