Home page › Forums › Technical Support, Bugs and Fixes › MikroWizard Radius Authentication

Currently, there are 0 users and 1 guest visiting this topic .
Viewing 2 reply threads
  • Author
    Posts
    • March 5, 2026 at 6:48 am #8728
      Ghufran AbbasiGhufran Abbasi
      Participant

        I’m getting an error while using RADIUS authentication with MikroWizard. Below are the MikroTik debug logs. However, the MikroWizard portal shows an error indicating an incorrect password.

        2026-03-03 12:00:19 radius,debug new request code=Access-Request service=login
        2026-03-03 12:00:19 radius,debug tx to 172.17.15.47:1812 code=Access-Request id=13 service=login
        2026-03-03 12:00:19 radius,debug,packet tx Access-Request with id 13 to 172.17.15.47:1812
        2026-03-03 12:00:19 radius,debug,packet Signature = 0xc05a6c76acbcb5fe4cfac5b21bed9124
        2026-03-03 12:00:19 radius,debug,packet Service-Type = 1
        2026-03-03 12:00:19 radius,debug,packet User-Name = “noc”
        2026-03-03 12:00:19 radius,debug,packet MS-CHAP-Challenge = 0xa59847f6783580aa6a17d28be65f9d5f
        2026-03-03 12:00:19 radius,debug,packet MS-CHAP2-Response = 0x00004fd812afa914687a2ab0ac028d40
        2026-03-03 12:00:19 radius,debug,packet 4a8400000000000000006c2990a7f2e0
        2026-03-03 12:00:19 radius,debug,packet 291c04aceccb088294ef7575eb96d804
        2026-03-03 12:00:19 radius,debug,packet 8ac8
        2026-03-03 12:00:19 radius,debug,packet Calling-Station-Id = “192.168.88.40”
        lines omitted……….
        2026-03-03 12:00:19 radius,debug,packet Message-Authenticator = 0x00fd078930bc21765df490db17bde4cd
        2026-03-03 12:00:19 radius,debug rx reply code=Access-Reject service=login
        2026-03-03 12:00:19 radius,debug,packet rx Access-Reject with id 13 from 172.17.15.45:1812
        2026-03-03 12:00:19 radius,debug,packet Signature = 0x4d56cda23c9a081e637c3bdce74aa165
        2026-03-03 12:00:19 system,error,critical login failure for user noc from 192.168.88.40 via winbox

      • March 5, 2026 at 7:08 am #8730
        Sepehr HashtroudilarSepehr
        Keymaster

          Hi
          assuming 172.17.15.45 is MikroWizard server ip the following line indicates that the mikrowizard responded to auth request :

           2026-03-03 12:00:19 radius,debug,packet rx Access-Reject with id 13 from 172.17.15.45:1812

          So the problem is one of the following:
          1. Radius secret mismatch . if you changed radius secret later in MikroWizard please restart mikroman container and then remove the radius client automatically crated in Mikrotik device to trigger automatic add again or change radius secret in Mikrotik radius client.
          2. You are using wrong username/password combination
          3. You didn’t grant this Mikrotik device access for user noc, you can check Auth log in MikroWizard panel to see why it is rejected

          let me know if this helped or not.

        • March 6, 2026 at 5:43 am #8732
          Mubashir SohailMubashir Sohail
          Participant

            Hi,
            This seems to be an issue in the source code. I was able to diagnose it and fixed it using Claude. I have also created a GitHub issue on this bug.
            Kindly refer to this issue on the official mikroman repository:
            https://github.com/MikroWizard/mikroman/issues/11

            I request the developer to look into this issue and fix it .

            Thank you,
            Mubashir Sohail

            1 user thanked author for this post.
            Sepehr Hashtroudilar Sepehr
        • Author
          Posts
        Viewing 2 reply threads
        • You must be logged in to reply to this topic.