Closed JeGoi closed 1 year ago
id created_at mac ip computer_name user_name stripped_user_name realm event_type switch_id switch_mac switch_ip_address radius_source_ip_address
called_station_id calling_station_id nas_port_type ssid nas_port_id ifindex nas_port connection_type nas_ip_address nas_identifier auth_status reason auth_type eap
_type role node_status profile source auto_reg is_phone pf_domain uuid radius_request radius_reply request_time radius_ip
1 2023-07-21 01:48:21 00:03:00:11:11:01 N/A N/A 000300111101 000300111101 null Radius-Access-Request 44:38:39:00:00:12 44:38:39:00:00:12 172.18.120.201 N/A
44-38-39-00-00-12: 00:03:00:11:11:01 Ethernet swp12 8 8 Ethernet-NoEAP 172.18.120.201 localhost Accept Accept headless_device reg
catch_wired_mac_authentication N/A 0 Acct-Session-Id = "FD64D8F24D789AE5",\nCalled-Station-Id = "44-38-39-00-00-12:",\nCalling-Station-Id = "00:03:00:11:11:01",
\nEvent-Timestamp = "Jul 21 2023 01:48:09 UTC",\nFramed-MTU = "1400",\nFreeRADIUS-Client-IP-Address = "172.18.120.201",\nMessage-Authenticator = "0x9f58af697b7bcf16629c57b564c7bc81",\nNAS-IP-Address = "1
72.18.120.201",\nNAS-Identifier = "localhost",\nNAS-Port = "8",\nNAS-Port-Id = "swp12",\nNAS-Port-Type = "Ethernet",\nPacketFence-KeyBalanced = "d0765eaba49810c0c2578385bc6272b2",\nPacketFence-Radius-Ip
= "172.18.120.15",\nRealm = "null",\nService-Type = "Call-Check",\nStripped-User-Name = "000300111101",\nUser-Name = "000300111101",\nUser-Password = "******" REST-HTTP-Status-Code = "200",\nTunnel-Medi
um-Type = "IEEE-802",\nTunnel-Private-Group-Id = "100",\nTunnel-Type = "VLAN" 0 172.18.120.15
Looks fine in the db.
Also noticed that on the Web UI, the radius files are empty (as seen in the screenshot) Git Commit ID: 738349976ae76f04720c6e24a30561080faf03aa
root@pfv13-abhi:/usr/local/pf# apt-cache madison packetfence
packetfence | 13.0.0+20230720171010+939623635+0011+devel+bullseye1 | http://inverse.ca/downloads/PacketFence/debian/13.0 bullseye/bullseye amd64 Packages
root@pfv13-abhi:/usr/local/pf#
Pic1::
Pic2::
Check with @jrouzierinverse and @JeGoi It's due to an urldecode we applied at the API call. We'll do the encoding on piping the logs into redis / mariadb as what we did before to keep maximum capability.
fixed by c93b80c7cc9843ff86e2f6dedb14f0e68eb7fefe
Describe the problem
Mandatory informations
Symptoms How the problem can be identified if it appears again ? Rerun the script