Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    MSCHAPv2: How a shared key is used in auth request

    Scheduled Pinned Locked Moved Captive Portal
    4 Posts 2 Posters 999 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      reb.mike
      last edited by

      I am new to MSCHAPv2, looking for pointers on:
      When Radius Protocol is chosen as MSCHAPv2: how a shared key is used and verified between CP and radius server? Could someone help me with pointers.

      1 Reply Last reply Reply Quote 0
      • E Offline
        EMWEE
        last edited by

        The shared secret between a NAS (CP in this case) and the RADIUS server can be configured in clients.conf or in your NAS table of your SQL database.

        When u configure SQL in your FreeRADIUS package you have the option read clients from NAS table.

        1 Reply Last reply Reply Quote 0
        • R Offline
          reb.mike
          last edited by

          Thank you for the reply. What i am exactly looking for is:
          In PAP, user password + sharedkey combination is used and the generated hash is sent to radius server for authentication. What is the equivalent in MSCHAPv2, how a shared key is used between radius server and radius client for authentication OR how is the shared key configured in the radius client is conveyed to the radius server.

          1 Reply Last reply Reply Quote 0
          • E Offline
            EMWEE
            last edited by

            MSCHAPv2 uses a server side digital certificate. With this certificate it creates a secure tunnel. Inside this tunnel it uses CHAP or even PAP authentication.

            Hopes this helps. Otherwise google RADIUS + MSCHAPv2. There is alot of information about it.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.