eastcom
06-18-05, 07:32 AM
Have a problem with a fake AP on my network.
Fake AP is named the same as my station's SSID, but on Channel 1, regardless of where I set my AP (Cisco 350). Has WEP enabled. Does not appear to pass traffic, just interferes with the signal from my real AP.
Fake AP has MAC of all 0's (000000000000).
Fake AP sends a beacon signal about every three minutes, of sufficient strength to degrade, and bump off users of the legitimate AP. When the "beacon" turns on, the signal is degraded on my legitimate AP, and causes stations to drop off. They reattach, only to repeat the scenario again in a few minutes.
I have two access points in different locations, and this happens in both scenarios. This leads me to believe that this is not a hacker or "actual" AP, but something like malware or a virus affecting my AP, router or PC.
Have deleted profile in NS, and restarted with same results.
Ideas, anyone?
--eastcom
Post 2:
Results of reinstalling on same machine, same. Profile erased (meaning uninstalled, reinstalled) and discovery of my access point immediate. The fake ap (000000000000) shows up in under three minutes, meaning it's strobing the network on a 3-minute cron. It definitely degrades and cancels the signal from the real AP, when it comes on, for maybe two or three seconds.
Results of installing on new machine, fake ap does not exist.
Therefore, it exists ONLY on the machine running Netstumber 0.4.0.
If the fake AP is erased from the discovered networks, it STILL exists, and the strobe is still noticable. Again, ONLY on the machine it's installed on.
A new install on another machine is OK. The condition does not exist.
So, software bug?? Netstumber guys, it's in your court.
--eastcom
Fake AP is named the same as my station's SSID, but on Channel 1, regardless of where I set my AP (Cisco 350). Has WEP enabled. Does not appear to pass traffic, just interferes with the signal from my real AP.
Fake AP has MAC of all 0's (000000000000).
Fake AP sends a beacon signal about every three minutes, of sufficient strength to degrade, and bump off users of the legitimate AP. When the "beacon" turns on, the signal is degraded on my legitimate AP, and causes stations to drop off. They reattach, only to repeat the scenario again in a few minutes.
I have two access points in different locations, and this happens in both scenarios. This leads me to believe that this is not a hacker or "actual" AP, but something like malware or a virus affecting my AP, router or PC.
Have deleted profile in NS, and restarted with same results.
Ideas, anyone?
--eastcom
Post 2:
Results of reinstalling on same machine, same. Profile erased (meaning uninstalled, reinstalled) and discovery of my access point immediate. The fake ap (000000000000) shows up in under three minutes, meaning it's strobing the network on a 3-minute cron. It definitely degrades and cancels the signal from the real AP, when it comes on, for maybe two or three seconds.
Results of installing on new machine, fake ap does not exist.
Therefore, it exists ONLY on the machine running Netstumber 0.4.0.
If the fake AP is erased from the discovered networks, it STILL exists, and the strobe is still noticable. Again, ONLY on the machine it's installed on.
A new install on another machine is OK. The condition does not exist.
So, software bug?? Netstumber guys, it's in your court.
--eastcom