On Jun 22, 2022, at 10:01 AM, 网络时代 via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
In the actual test, freeradius sends Access-Accept,See the last output section below. The router log shows that the authentication fails. MikroTik tech support can't find a reason so far.
Then blame Mikrotik. If FreeRADIUS sends an Access-Accept, and the router log shows failure, then the problem is the router.
All certificates are created in freeradius and imported into ROS.
[e_zhangiso@myradius ~]$ su Password: [root@myradius e_zhangiso]# radtest vtest1 zsl123 localhost 18120 testing123 Sent Access-Request Id 19 from 0.0.0.0:38185 to 127.0.0.1:1812 length 76 User-Name = "vtest1" User-Password = "zsl123" NAS-IP-Address = 93.191.168.52 NAS-Port = 18120 Message-Authenticator = 0x00 Cleartext-Password = "zsl123" Received Access-Accept Id 19 from 127.0.0.1:1812 to 127.0.0.1:38185 length 20 [root@myradius e_zhangiso]# cd /usr/local/bin/ [root@myradius bin]# ls dbus-cleanup-sockets radattr dbus-daemon radclient dbus-launch radcrypt dbus-monitor radeapclient dbus-run-session radlast dbus-send radsqlrelay dbus-test-tool radtest dbus-update-activation-environment radwho dbus-uuidgen radzap dhcpclient smbencrypt eapol_test ttls-eap-mschapv2.conf map_unit x86_64-unknown-linux-gnu-pkg-config peap-mschapv2.conf xmlwf pkg-config
That is completely unreadable. But... if eapol_test works, and FreeRADIUS sends Access-Accept, then the problem isn't FreeRADIUS. Alan DeKok.