Menu

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Sign In Register

Advanced IDP goes... rogue

MacDaemonMacDaemon Newbie ✭
in SonicWave

When I enable advanced IDP all my wireless devices are listed as Rogue including the Sonicwall gateway ports for those networks. Additionally every device is also listed as a Rogue access point including the Sonicwaves. I previously had this issue in SonicOS 6, but it appears to be back in SonicOS7. Other issues include logging all found wireless networks as "Rogue or MitM Access Point" Regardless of the name, or the fact the it is someone elses wifi network. Has anyone has any success with advanced IDP as it appears to be broken to me.

Category: SonicWave
Reply

Answers

  • MacDaemonMacDaemon Newbie ✭
    Environment: SonicOS 7.1 on TZ470 with Sonicwave 432 access points
  • AlanZhouAlanZhou Newbie ✭
    edited November 22

    Hi,

    Is your SonicWave432e running sw_spw_eng_9.1.4.7_7.bin.sig at present ? If yes, could you please try sw_spw_eng_9.1.5.0_9.bin.sig by manually setting firmware version from https://x.x.x.x/sonicui/7/m/diag page.

    image.png

    thanks

  • MacDaemonMacDaemon Newbie ✭

    Brought this up with Sonicwall Support. Apparently this is still an issue in SonicOS7. The Patch that ALANZHOU suggested is the fix. Interesting that nothing has been changed in production. Guessing not many people are using advanced IDP.

  • MacDaemonMacDaemon Newbie ✭

    Update: Not fully fixed.

    Local wireless devices are still being tagged as rogue. Something also happens with the Sonicwaves as the RSSI for all devices goes to -95. There are other issues. Bottom Line: Enabling Advanced IDP as I have may not give desired / expected results. I do not enable Disassociate rogue AP as that blocks authorized wireless clients.

    Will continue working with Sonicwall support on this issue.

    Screenshot 2024-12-08 at 4.23.58 PM.png

  • AlanZhouAlanZhou Newbie ✭

    Hi , The issue is due to there is a bug when your one vap ssid is the substring of another vap ssid (eg. "my ssid" and "my ssid 5G" ). You can disable "Add evil twin into Rogue AP list" to avoid this to work around.


    By the way, you can also modify vap ssid to avoid this.

    https://community.sonicwall.com/technology-and-support/discussion/comment/22759#Comment_22759

  • MacDaemonMacDaemon Newbie ✭
    https://community.sonicwall.com/technology-and-support/discussion/comment/22812#Comment_22812

    Interesting, as I have an issue with Sonicwall not being able to offer "my 2.4 ssid" and "my ssid with Steering" (both 2.4 & 5) as IOT devices require 2.4 only. Requiring the scenerio you just mentioned. Currently I am running 2 SSIDs both with steering so there is no "my ssid" and "my ssid 5g" but thanks for the heads up on this.

Sign In or Register to comment.