I have multiple connection profiles defined for matching different connection types AND Switch groups, Ethernet-EAP and Wireless-802-11-EAP match perfectly and return the expected behaviour.
A profile using the same switch group but this time using connection types "Ethernet-NoEAP" or "Wireless-802-11-EAP" initially matches to the profile (http.aaa log below) then 5 seconds later the httpd.portal log shows a reassignment of the connection profile to the default captive portal, giving me the default captive portal rather than the one specified in the initial matched connection profile. pulse packetfence_httpd.aaa: httpd.aaa(10217) INFO: [mac:b8:2a:72:c2:5a:d3] Instantiate profile mab-wired (pf::Connection::ProfileFactory::_from_profile) pulse packetfence_httpd.portal: httpd.portal(11157) INFO: [mac:b8:2a:72:c2:5a:d3] Instantiate profile default (pf::Connection::ProfileFactory::_from_profile) I have tested different nodes and multiple variants of the connection profile and still get the same behaviour. Is this a bug? Packetfence Version 10.2.0 Damon
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
