The 2 clients that were transmitting garbage could not be reached through the
wireless interface (oddly enough). From the base station, we could not see the
client in Configurator's "Turbocell Station Entries" or "Wireless Link Test".
We could only communicate with the RG & KN directly through the ethernet
interface. Is this the same with you?
I'm still trying to figure out what it is that sets these things off in the
first place by looking at what is common to both incidents. One other common
point that I should have mentioned:
The equipment started transmitting garbage while the customer was away on
vacation.
This leads me to believe that these incidents could be quite common and that
the only reason we haven't noticed it more often is because someone who is home
and notices that they don't have internet is going to power cycle their
equipment to see if it comes back.
*********** REPLY SEPARATOR ***********
On 2004-07-08 at 8:42 PM martin@belairinternet.com wrote:
>Hi there,
>
>We are seeing the same thing... quite often. The units locks up somehow
>and starts transmitting garbage. I have asked Karlnet a number of times if
>this was something they were aware of, and so far nothing has happend. We
>are running 4.44 on RG-1100 and KN-100's as clients. MY solution has been,
>so far to create a .bat and reboot all clients on the base (we do not
>loose all connectivity, of course dependend on the signal strength of the
>client that is locked up). It seems when we reboot the base all clients
>come up for 5-10 sec. So the client must notice that the base is gone. But
>it pickes up the bad behaviour after 5-10 sec. Let me know what Reggie
>tells u.
>
>Martin Madsen
>
>>
>> *********** REPLY SEPARATOR ***********
>>
>> On 2004-07-08 at 4:16 PM Bob Hrbek wrote:
>>
>>>So...you are saying that in high noise conditions the KN-100 will blast
>>>out
>>>enough power/traffic to take out the whole network?
>>
>> I don't know if other 2.4GHz devices could cause this behaviour or not.
>> I've just made a note that in both cases, there were other 2.4GHz devices
>> present.
>>
>>>Could you have been any luckier to find that customer 10 miles from your
>>> AP
>>>with a spectrum analyzer? Was that just a guess or do you have an UBER
>>>DUPER analyzer there? I'd like to get one of those babies!
>>
>> It doesn't take rocket science to track down a signal. you just need a
>> narrow beam antenna with good F/B descrimination.
>>
>>>
>>>-bob
>>>
>>>----- Original Message -----
>>>From: "Caleb Carroll" <karlnet@pathcom.ca>
>>>To: <karlnet@WISPNotes.com>
>>>Cc: <support@karlnet.com>
>>>Sent: Thursday, July 08, 2004 4:12 PM
>>>Subject: [Karlnet] CRITICAL problem w/ Karlnet firmware?
>>>
>>>
>>>
>>>About 2 months ago (when we first upgraded our customer base to firmware
>>>v4.44-02) we had a problem at one of our base stations (KN-200) where we
>>>lost the ability to communicate with any of our customers (KN-100's &
>>>RG-1100's). After our technicians spent 4 frantic hours of trying to
>>>determine what the problem was, I decided to investigate the problem
>>>myself.
>>>Our technicians could see what looked like a CW on their spectrum
>>> analyzer.
>>>I spent the next 2 hours driving around trying to pinpoint where the
>>> signal
>>>was coming from (we assumed that it was something very nearby). I
>>> finally
>>>found the source of the interference... It was from 10 miles away and ...
>>>It
>>>was one of our customers! No one was home at the time so we disconnected
>>>the antenna and suddenly all of the other customers came back online.
>>>
>>>Later on, we returned to this customers house and made the following
>>> notes
>>>PRIOR to turning off the customer's KN-100:
>>>
>>>1) the same signal was still being transmitted from the KN-100.
>>>2) we could use configurator to login to the KN-100.
>>>3) because the profile of the spectrum use on the spectrum analyzer
>>> looked
>>>similar to what you would see if you used the "Antenna Alignment, Full
>>>Speed" function, we decided to enter 0 seconds to run the test (0=Stop).
>>>the signal did not stop.
>>>4) the customer owned a multi-handset 2.4GHz phone system with 4 phones.
>>>5) the customer had a 2.4GHz Linksys router sitting on top of the KN-100
>>>(channel overlap was 14MHz, KN-100 on ch3 and Linksys on ch6 - of course,
>>>we
>>>didn't install it).
>>>
>>>
>>>TODAY, WE HAD A REPEAT OF THIS INCIDENT.
>>>
>>>Notes from today:
>>>
>>>1) the customer had an RG-1100
>>>2) we could login with configurator (we saved the config file this time).
>>>3) the customer owns a 2.4GHz telephone.
>>>
>>>I'm going to send the configuration file to Karlnet and I'm going to post
>>>an
>>>.mpg file of the spectrum analyzer output later on today.
>>>
>>>
>>>
>>>_______________________________________________
>>>Karlnet mailing list
>>>Karlnet@WISPNotes.com
>>>http://lists.wispnotes.com/mailman/listinfo/karlnet
>>>
>>>_______________________________________________
>>>Karlnet mailing list
>>>Karlnet@WISPNotes.com
>>>http://lists.wispnotes.com/mailman/listinfo/karlnet
>>
>>
>>
>> _______________________________________________
>> Karlnet mailing list
>> Karlnet@WISPNotes.com
>> http://lists.wispnotes.com/mailman/listinfo/karlnet
>>
>
>_______________________________________________
>Karlnet mailing list
>Karlnet@WISPNotes.com
>http://lists.wispnotes.com/mailman/listinfo/karlnet
_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet
|