I am trying to get our existing packetfence server working with new
Meraki cloud-managed APs. I added all the AP management subnets using
CIDR notation, like 192.168.198.0/24. These were added to a new Switch
Group, and the shared secret from that Switch Group was added to the
Meraki dashboard. When I do a test from the dashboard, I get log lines
that look like:
May 26 10:50:51 packetfence auth[1554]: Adding client 192.168.198.32/32
May 26 10:50:51 packetfence auth[1554]: (2032332) rest: ERROR: Server
returned:
May 26 10:50:51 packetfence auth[1554]: (2032332) rest: ERROR:
{"control:PacketFence-Authorization-Status":"allow","control:PacketFence-Request-Time":1685112651,"Reply-Message":"Switch
is not managed by PacketFence"}
May 26 10:50:51 packetfence auth[1554]: (2032332) Rejected in post-auth:
[spfister] (from client 192.168.198.32/32 port 0 cli 02:00:00:00:00:01
via TLS tunnel)
May 26 10:50:51 packetfence auth[1554]: (2032332) Login incorrect
(Config item "realm[null].oauth2.cache_password" does not exist):
[spfister] (from client 192.168.198.32/32 port 0 cli 02:00:00:00:00:01
via TLS tunnel)
May 26 10:50:51 packetfence auth[1554]: [mac:02:00:00:00:00:01] Rejected
user: spfister
May 26 10:50:51 packetfence auth[1554]: (2032333) Login incorrect
(eap_peap: The users session was previously rejected: returning reject
(again.)): [spfister] (from client 192.168.198.32/32 port 0 cli
02:00:00:00:00:01)
Why does it say "Switch is not managed by Packetfence"?
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
