I am sure “something” is happening somewhere.
What do the radius logs show?
What does tcpdump indicate?
Is there any radius request coming in from that controller when you connect
something to it?
If not then the issue is with the controller’s configuration.
If there is anything coming from
Andi,
Quick question, maybe not related at all but still.
Is this happening on “busy” AP ? Do you know if there’s a lot of clients
connected at the same time on the AP / radios of the AP ?
Do you have any sort of Maximum Allowed Clients configurations ? (Advanced
section of the WLAN) ?
Cheers!
What I mean by request is the HTTP call.
The stash is being initialized when the HTTP call comes in and then is
“destroyed” once the page is loaded on the client side. You can’t then use the
stash to pass values from call to call…
Is that better ? :P
Cheers!
dw.
—
Derek Wuelfrath
Also,
As i can see, included log snippet only shows relevant radius authz requests.
Is there anyway you can check in that same log just to make sure PacketFence
does not send a COA or anything else that can lead the client to reauthz ?
Cheers!
dw.
—
Derek Wuelfrath
dwuelfr...@inverse.ca ::
Hi Jonathan,
based on the log i thing that extendedKeyUsage is not correctly defined.
Can you check that ?
Regards
Fabrice
Le 2015-11-09 20:45, Jonathan Mahady a écrit :
Hi,
I'm having an issue with the assignment of certificates using the
packetfence PKI plugin. The plugin resides on the
Hello Ismael,
you created a user in radius but it probably doesn't exist on
packetfence side. (check packetfence.log)
So remove what you did in /usr/local/pf/raddb/users and follow this
documentation:
Hi,
We have packetfence 3.5.1 on debian, running with both
- 802.1x auth on our wired chassis (hp 5400)
- inline on our wifi network
On the HP 5412 chassis, I have one module to packetfence inline, with
untagged VLAN6 on all ports (packetfence_inline) plus tagged VLAN1 (the
802.1x 'main'
