Captive Portal with Radius authentication memory size error during log in



  • Hi,

    I tried to enable the Captive Portal on my pfSense machine with Radius based authentication. The Radius server is on zeroshell machine and runs on a different local subnet.

    Anyway, every time I try to log in and see if the setup works, I get an error message that says something like

    Didn't get a proper response…

    . Then every second time I try to log in, the following error occurs:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4294967295 bytes) in /etc/inc/radius.inc on line 446

    The same error occurs on subsequent tries. Until I connect to a different network, disconnect, connect to pfSense Lan once again and repeat the whole process. The same thing happens. I read this thread https://forum.pfsense.org/index.php?topic=79139.msg431558#msg431558 discussing a somewhat similar problem but the "solution" given there did not solve the issue.

    Any idea what might be causing this? Thanks!



  • Hello,

    This:
    @jultra:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4294967295 bytes) in /etc/inc/radius.inc on line 446

    Here -  in /etc/inc/radius.inc on line 446:

            while ($attrib = radius_get_attr($this->res)) {
    

    The PHP function radius_get_attr($this->res) 'explodes' when parsing the result send back by the Radius server.
    This is a original PHP function.

    What pfSEnse version are you using ?
    Can you use the same Radius software as in the other thread ?



  • Hi Gertjan,

    The first error I mentioned was caused by a misconfiguration of the client's authorization (NAS) within the freeradius server that I was using. After I realized my mistake and fixed it, the setup worked as expected and I did not encounter the same problem again.

    Anyway, the freeradius server I was using is the one included on zeroshell 2.0.RC.

    Cheers,

    John



  • What was the configuration issue?  Can you post the resolution?  I am also having a problem with 2.1.5


Log in to reply