Means checkup?
[root@PacketFence-ZEN bin]# ./pfcmd checkup
Array found where operator expected at
/usr/local/pf/lib/pf/services/manager/radiusd_child.pm line 570, at end of
line
(Do you need to predeclare uniq?)
"my" variable $cluster_ip masks earlier declaration in same scope at
Hello Stephen,
it looks that there an issue to connect to the OMAPI socket.
Does the dhcp server is running ?
Also try to disable OMAPI in the admin gui and restart pfqueue.
Regards
Fabrice
Le 2017-11-02 à 10:20, Stephen Appleby via PacketFence-users a écrit :
>
> I've setup radius and
I've setup radius and MAC auth on an Entarasys/Extreme B5K125 switch.
Everything seems to be working correctly, but I'm seeing the following error
in the packetfence log whenever someone
connects a device.
Nov 2 09:15:28 PacketFence-ZEN pfqueue: pfqueue(6190) WARN:
[mac:34:64:a9:d1:a9:0a]
Hello James,
cool it works, i will add the support of 802.1x for the Mserie in the
main code.
Regards
Fabrice
Le 2017-11-02 à 09:15, James Garcellano via PacketFence-users a écrit :
> Hello Fabrice,
>
> Adding the line "sub supportsWiredDot1x { return $TRUE; }" to
>
What are the errors ?
Le 2017-11-02 à 09:18, Alessandro Canella a écrit :
>
> Something went wrong…
>
>
>
>
>
> [root@PacketFence-ZEN pf]# patch -p1 < pat.diff
>
> (Stripping trailing CRs from patch; use --binary to disable.)
>
> patching file lib/pf/services/manager/radiusd_child.pm
>
>
Hello Fabrice,
Adding the line "sub supportsWiredDot1x { return $TRUE; }" to
/usr/local/pf/lib/pf/Switch/Netgear/MSeries.pm and then rebooting PacketFence
has worked.
Here are the latest entries from the /usr/local/pf/logs/packetfence.log file:
Nov 2 12:46:30 packetfence-zen
Something went wrong...
[root@PacketFence-ZEN pf]# patch -p1 < pat.diff
(Stripping trailing CRs from patch; use --binary to disable.)
patching file lib/pf/services/manager/radiusd_child.pm
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 567 with fuzz 1 (offset -23 lines).
A)
