Re: [PacketFence-users] All authentication failed with error"NoEAPsession matching state xxxx"

Hello Yan, it's very difficult to debug with just what you say ,what is your setup ? (running PacketFence on a raspberry pi is not the same thing than running on a 32 cpus server) rlm_perl is?0?2 just use to select the correct chroot based on the realm, so it's something really fast.

Re: [PacketFence-users] All authentication failed with error"NoEAPsession matching state xxxx"

Hi Fabrice, I mean rtml_perl module takes too much time processing requests and drags radius very slow. And I see, no need to login but only need to open mgmt_ip:9000. But which graphics can tell the issue cause ? Today we did a pressure test with 50 qps (pf+AD authentication) and found the

Re: [PacketFence-users] Unifi APs and CoA

David, Your understanding is correct. Currently the UniFi only supports deauthenticating a client using the controller API and not using CoA. It is possible to enable RADIUS CoA for a single SSID and frequency, but this may not be useful for you. This is because the UniFi runs a separate

Re: [PacketFence-users] Unifi APs and CoA

Hello David, the unifi AP is not yet correctly supported, there is some code about that but you have to do some custom config on the Unifi controller. Have a look at the mailing list archive about unifi. Regards Fabrice Le 2018-01-31 à 13:02, David Harvey via PacketFence-users a écrit : I

Re: [PacketFence-users] Unifi APs and CoA

I should also note. I've just changed our APs from switch type hostapd to ubiquity::unify, added the controller IP (a docker image in my case), and also attempted to add the webservices field as details in the documentation: wsTransport=HTTPS wsUser=admin wsPwd=admin On Wed, Jan 31, 2018 at

[PacketFence-users] Unifi APs and CoA

Hi packetfence users, I just wanted to confirm a feature (or my undertsnading of). I'm using unifi access points with great success for portal login paired with EAP-TLS. Unregistered clients with certs land on the registration VLAN, and then have their proper vlans assigned by the portal login.

[PacketFence-users] R: R: R: R: No client IP update in cluster

Ok Fabrice, I imagined it so I will wait for a fix in next release if it is possible. Thanks P.S: On next week we will go in production on my company's first site and we're going to buy the silver support. Luca Da: Fabrice Durand via PacketFence-users

Re: [PacketFence-users] R: R: R: No client IP update in cluster

Hello Luca, dhcp is udp traffic so it's not really easy to load balance. Btw there is a pull request on github for that: https://github.com/inverse-inc/packetfence/pull/2887 Regards Fabrice Le 2018-01-31 à 03:40, luca comes via PacketFence-users a écrit : > Hi Fabrice, > I checked and

Re: [PacketFence-users] packetfence 7.4 + Authentication Sources

Hello Will, yes i saw that on my setup and we will push a fix in the maintenance. Regards Fabrice Le 2018-01-31 à 08:00, Will Halsall via PacketFence-users a écrit : > > Hi Folks, > >   > > Adding an Associated Realms to any of my Authentication Sources causes > the test connection to fail

Re: [PacketFence-users] All authentication failed with error "No EAPsession matching state xxxx"

Hello Yan, Le 2018-01-31 ?? 00:28, Yan a ??crit?0?2: > > Hi dear users, > > After a whole night??s analysis, we found it??s pf that takes too much > time processing authentication request if the QPS is too high and > hangs all radius requests later and then Aruba AC meets the radius > timeout

[PacketFence-users] packetfence 7.4 + Authentication Sources

Hi Folks, Adding an Associated Realms to any of my Authentication Sources causes the test connection to fail with the following error Error! Unexpected error. See server-side logs for details. Without an Associated Realms everything works fine This is not causing me a problem but was just

Re: [PacketFence-users] All authentication failed with error "No EAPsession matching state xxxx"

Hi dear users, After a whole night??s analysis, we found it??s pf that takes too much time processing authentication request if the QPS is too high and hangs all radius requests later and then Aruba AC meets the radius timeout setting and re-sends the same radius access request to pf while pf