General

Profile

Phillip Hernandez

  • Registered on: 04/07/2016
  • Last connection: 10/17/2017

Issues

Activity

10/17/2017

10:11 AM pfSense Packages Feature #7895: Add a script for CARP monitoring to NRPE
I agree that it would be very helpful if there was a way to monitor carp status via SNMP.
I ran your script on my ...

07/28/2016

11:28 AM pfSense Bug #5652: Radius IETF Class Group Assignment - Incorrect Standard
I disagree with using Cisco-AV:Pair and believe that using Filter-Id is a better option.
Thanks

04/07/2016

11:45 AM pfSense Bug #6088: RADIUS WebUI - Deny Config Write is not honored
I wanted to confirm that this works. I created a custom patch to apply to my pfsense boxes that are running 2.2.6 and...
11:34 AM pfSense Bug #6086: RADIUS WebUI login does not work with attribute class (25) when the server returns multiple attribute entries with different data
I wanted to confirm that this works. I created a custom patch to apply to my pfsense boxes that are running 2.2.6 and...
11:03 AM pfSense Bug #6086: RADIUS WebUI login does not work with attribute class (25) when the server returns multiple attribute entries with different data
Ok thanks for your help. I will investigate further and open a separate ticket for adding another AVP.
Thanks
10:27 AM pfSense Bug #6086: RADIUS WebUI login does not work with attribute class (25) when the server returns multiple attribute entries with different data
Can you please add support for another AVP as well? In working systems where the Class AVP is not a string changing i...
02:54 AM pfSense Bug #6088: RADIUS WebUI - Deny Config Write is not honored
For clarity, when the user is authenticated with RADIUS and the deny config write is set it is not enforced.
02:47 AM pfSense Bug #6088 (Resolved): RADIUS WebUI - Deny Config Write is not honored
After authenticating with a user that has been put into a group with "Deny Config Write" it is not enforced. If you c...
02:20 AM pfSense Bug #6086 (Resolved): RADIUS WebUI login does not work with attribute class (25) when the server returns multiple attribute entries with different data
After doing several packet capture and reviewing RFC 4372. It seems to be a normal operation to include the class 25 ...

Also available in: Atom