Re: [Karlnet] Problem COR --help!

["Bob Hrbek" <bhrbek@jagwireless.com>]

We also picked up an unknown AP on this new tower... (it wasn't named anything other than Wavepoint(something or other))  It certainly isn't ours but was sitting on our channel (grr).   Do you think they will cause this reboot issue at the new tower as well?

 

thanks,

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?