RE: [Karlnet] Problem COR --help!

["Charles Chia Sheng Wu" <cwu@cwlab.net>]

larry (who runs 11b) might be talking about 802.11b w/ similar pass phrases - it can be a huge problem, especially in SEC bridges on AP-Plus - not really an issue in TurboCell

-----Original Message-----
From: karlnet-admin@WISPNotes.com [mailto:karlnet-admin@WISPNotes.com]On Behalf Of Bob Hrbek
Sent: Wednesday, December 11, 2002 9:25 AM
To: karlnet@WISPNotes.com
Subject: Re: [Karlnet] Problem COR --help!

The towers are 5 miles apart and the channel plan was changed due to interference.  The new tower has our gear at 475' and things changed since we did the survey at the site.  The SNR between the APs was between 2 - 10 so they weren't hearing each other well and occasionally they didn't even show up in the link analysis.

 

 

BUT....you are saying that if the AP's hear each other...they will go nuts?  Whats up with that?  They are on different NET ID's...same passphrase but yes...they were on the same channel.  We let the AP's run this way for about a day and didn't see any adverse RF problems then this AP just started rebooting all the time.

 

 

-bob 

----- Original Message -----

From: Larry Yunker - Cyber Broadcasting

To: karlnet@WISPNotes.com

Sent: Wednesday, December 11, 2002 9:22 AM

Subject: Re: [Karlnet] Problem COR --help!

Are both towers running on the same or close to the same channel?  You should have proper channel separation between those towers or else your AP will "commit-suicide" (reboot) every time it gets confused.

 

----- Original Message -----

From: Bob Hrbek

To: karlnet@WISPNotes.com

Sent: Wednesday, December 11, 2002 9:13 AM

Subject: [Karlnet] Problem COR --help!

I have a COR running v4.15 with one interface set as a sattelite for backhaul and the other as ISPbase w/ protocol filtering.  The device is powered across about 150' of cat5. 

 

 

The device is rebooting all the time.  I think it may be a power issue but the device is getting about 4.79v...even under HEAVY load.  There are 9 clients on this AP now and the problems really started after I added that last client.  I am working to get a different DC injector to get the power up but it really seems like there is something else going on.   The device will reboot under the following conditions:

 

1) if I send it a ping flood

2) if I ping 3 or more clients and open up most any of the monitoring screens on the config app.  (link test, remote monitor, etc.)

 

 

I did just turn up another tower about 5 miles away and this site can "hear" the other tower just a bit.  The problem seemed to get exponentially worse once the new tower came up.  However, it was also about the same time that we added the additional client.

 

The FW on both radios is 8.x as I believe they are loaded with this FW when the COR boots. 

 

There are not to many people doing stuff on the network this morning but I just change freq's at the new tower (so this site can't hear it anymore) and things seem to be working fine now.

 

 Anybody have any ideas?