In fact I have no realms in "users" file, just users. users can be : "test.dom.dslnet.fr" (for establishing the L2TP tunnel) : this user is un "users" file like this : test.dom.dslnet.fr Auth-Type := Accept Service-Type = Outbound-User, Tunnel-Type = L2TP, Tunnel-Medium-Type = IP, Tunnel-Server-Endpoint = 185.x.x.x, Tunnel-Assignment-ID = 185.x.x.x, Tunnel-Preference= 10, Tunnel-Client-Auth-Id = LAC, Tunnel-Server-Auth-Id = LNS, Tunnel-Password = password, Fall-Through = No but users can also be : user@test.celya.dslnet.fr (for establishing l2tp session) : this user is in a database (filled by daloradius). I continue trying to solve it on my own and will come back with a full radiusd -X (for both users) if I'm not able to. Anyway thanks for your support :) Cédric 2018-01-24 12:45 GMT+01:00 Matthew Newton <mcn@freeradius.org>:
On Wed, 2018-01-24 at 12:15 +0100, BASSAGET Cédric wrote:
I'm still having the same message : (11) suffix: Checking for suffix after "@" (11) suffix: Looking up realm "test.dom.dslnet.fr" for User-Name = " testradius@test.dom.dslnet.fr" (11) suffix: No such realm "test.dom.dslnet.fr"
That's a noop. So shouldn't affect the outcome if you're not wanting to proxy.
this realm is defined in /etc/raddb/mods-config/files/authorize, which is included at radiusd startup.
You don't define realms in mods-config/files/authorize. Alan's already said that.
here is the radiusd -XC log :
And you've also been told to send radiusd -X.
It's impossible to know what's happening without seeing a packet go through the server. Bits of -Xx (or -X or whatever) doesn't give the whole context. -XC doesn't show a packet going through the server.
There's no way we can tell what's going on without full debug output.
-- Matthew
- List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html