Captive Portal - FreeRadius Issue



  • I upgraded to the new 2.4 Love it BTW.  However having one issue.. that was not in 2.3 only showed up after upgrading..

    Captive portal is setup to use Radius / PAP clear text.

    When you put
    username: foobar
    password: test123

    it should pass the password to freeradius as PAP clear text.  I can see by dev tools that the form works fine, and its passing the proper form data.. However when FreeRadius gets it.. it gets this info

    Wed Aug  9 17:02:08 2017 : Debug: (1) Received Access-Request Id 11 from 192.168.1.1:65261 to 192.168.1.1:1812 length 136
    Wed Aug  9 17:02:08 2017 : Debug: (1)  NAS-IP-Address = REDACTED
    Wed Aug  9 17:02:08 2017 : Debug: (1)  NAS-Identifier = "REDACTED"
    Wed Aug  9 17:02:08 2017 : Debug: (1)  User-Name = "FooBar"
    Wed Aug  9 17:02:08 2017 : Debug: (1)  User-Password = "\007!u\201\014C\001\370\236\315#\026@\375Ø"
    Wed Aug  9 17:02:08 2017 : Debug: (1)  Service-Type = Login-User
    Wed Aug  9 17:02:08 2017 : Debug: (1)  NAS-Port-Type = Ethernet
    Wed Aug  9 17:02:08 2017 : Debug: (1)  NAS-Port = 12052

    As you can see… the password is not clear text, not even close.  I cannot figure out why this is happening. Only started after I updated to 2.4 and FreeRadius 3

    FYI I can run the username test from the CLI for FreeRadius and it works fine. Does not work when passed from Captive Portal.

    Thank you
    BreeOge


  • Rebel Alliance Developer Netgate

    It works here for me on 2.4 with Captive Portal and FreeRADIUS3.

    It works with Captive Portal set to PAP, or even MSCHAPv2. Doesn't really matter what I pick there, it all works so long as the user/pass is right.



  • I ended up reloading it from scratch.. and it fixed the issue.  Something about the upgrade it didnt like.


Log in to reply