09-03-2012 05:16 AM - edited 07-03-2021 10:36 PM
Hi all, I'm having an issue with these printer as about every hour the printer goes off from the wireless network.
On the WLC log I see:
Impersonation of AP with Base Radio MAC 00:23:33:18:7f:21 using source address of 00:19:88:01:d5:5f has been detected by the AP with MAC Address: 00:23:33:18:7f:20 on its 802.11b/g radio whose slot ID is 0
I don't understand what is the cause of the issue and how to disable this WLC check (maybe from IDS).
Anyone have suggestion?
Thanks
09-08-2012 06:37 AM
Sorry for the delay!
Let's get this troubleshooting started.
Perhaps your hitting a bug?
https://supportforums.cisco.com/docs/DOC-3666
09-08-2012 04:23 PM
I have no idea what firmware is your controller ...
Does the printer have a static IP address? If it does, did you enable "Passive Client" on the SSID setting?
09-10-2012 12:10 AM
My software: 7.0.235.0 so I don't think I hit the bug.
Now I'm trying with passive client.
Enrico.
09-11-2012 09:12 AM
if you're not hitting a bug, I would take a look at the AP boxes 'load profiles, noise..etc make sure they are all passed. Let us know if there any profile failed status.
do you know if the printer goes down when it's processing data or it will still go down when no one is sending any jobs to it ?
how many printers are in total ? do they connect to the same AP or this happens through the whole deployment?
how did the passive client test went ? did it help ?
thanks!
10-18-2012 05:10 PM
Neither the trigger due to AP authentication nor due to wIDS. It is due to a bad driver on wi2wi. update to good known driver.
Your Wi2Wi client spoofing AP's mac and sending packet to WLC infrastrucuture.
To mitigate this, use security WPA with mfp set to mandatory.
Root cause the issue through Wireless packet capture between the client and ap should prove the issue.
10-18-2012 11:51 PM
I'll try to change the security setting of the WLAN next time I go to the customer and let you know.
Thanks.
10-19-2012 10:57 AM
When mfp set to mandatory on WLC, make sure the wireless client supports CCXv5 otherwise it doesn't work. If none of the driver versions support ccx5 then hope for latest driver solve this issue. Remember, stations must support CCXv5 and must negotiate either TKIP or AES-CCMP to use client MFP.
07-27-2018 10:41 PM
Hi,
I'm seeing the same issue at my site and I was wondering if you resolved the issue.
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide