Freeradius - Remote Syslog not possible since 20.1 ?

[rcmcronny]

Hi,

update from 19.7 to 20.1 worked great, as every time Good Job !

No critical issue, but it seems ,that i can not get the freeradius logs to my syslog server on the network. I included all targets (except configd and filter) to my syslog remote target. Radius Logs (Login OK, Rejected etc) are local vissible in the backend log but not get not send to the remote target.

Did I miss a configuration here, to make it possible, or is this simply missing atm ?

Thanks,
Ronny

[mimugmail]

Did this really work with 19.7?

[rcmcronny]

Hi,

i do not have any old syslogs. It worked before 20.1 for sure, i did a regex matching on radius failed events.
But some days ago, i connected a new device unknown to radius, which should generate rejected log lines, that did not trigger. So i searched the remotesyslog server and found nothing, then search the opnsense log and found in the "general" log (not in the backend.log mentioned in my first post, sorry).

Checked my test graylog instance, and yes this worked (graylog is feed by my remote syslog)
I have redacted the systemname, and client and the mac /user/pass

Code: [Select]

2020-01-31 09:45:34.000
OPNsense.home.srv.local
OPNsense.home.srv.local radiusd[59566]: (4605) Login OK: [cc-50-xx-xx-xx-xx] (from client clientxxx port 0 cli CC-50-xx-xx-xx-xx)

Ronny

[mimugmail]

Can you try facility system daemons in Logging / Targets?

[rcmcronny]

Hi,

i have all applications on except filter and configd (tried, but does not make a difference),  levels all on and  Facilities all on. 
In the applications there is no radius or similar object.

Thats why i opened a thread here, as i am clueless now

Thanks,
Ronny