Ok so try that first:
https://github.com/inverse-inc/packetfence/blob/packetfence-7.3.0/lib/pf/Switch/Cisco/WLC.pm#L608
From:
return unless ($uri =~ /.*sid(.*[^\/])/);
to:
return unless ($uri =~ /.*sid(.*[^\/&])/);
then restart httpd.portal
and let me know if it's ok.
Regards
Fabrice
Hi Fabrice,
Thank you so much for your reply.
I can confirm that the registration url on the switch is -
http://172.16.207.67/Cisco::WLC
I can then confirm that the Radius Attributes are:
Cisco-AVPair = "url-redirect-acl=Pre-Auth-For-WebRedirect"
Cisco-AVPair =
Hello Nicolas,
thanks for your feedback. I've had a look to the guide, but it seems that
Clustering works well for vlan enforcement.
Does clustering fit well also for inline enforcement?
Thanks
Pasquale
Il giorno lun 2 dic 2019 alle ore 12:03 Nicolas Quiniou-Briand via
PacketFence-users ha
Hello Adrian,
can you check in the radius audit log (check the radius tab in the audit
log entry.) what is the value of the cisco-vsa url-redirect attribute ?
Regards
Fabrice
Le 19-12-02 à 10 h 07, Day, Adrian via PacketFence-users a écrit :
Hello,
I was wondering if somebody could
Hello Pasquale,
On 03/12/2019 14:47, Pasquale Lo Bello wrote:
Does clustering fit well also for inline enforcement?
Yes !
--
Nicolas Quiniou-Briand
n...@inverse.ca :: +1.514.447.4918 *140 :: https://inverse.ca
Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence