schilling wrote:
Here is my radiusd -X output of a assumed successful login with peap. Would you please see whether this is working? Yes, the default with one ldap line commented out in site-enabled/inner-tunnel works. But it will not work once I have a virtual server in the radiusd.conf.
I don't think it's quite that simple.
The debug is done with default radius.configuration with only the following addition: I could add all the uncommented lines in site-enabled/default to this virtual server instance, I just want to see what exactly is my previous issue, so I reduced to minimum "working" configure I thought. Well, may be not.
Exactly. It's not about "commenting or uncomment lines". It's about understanding how the server works. If you don't understand it, you will remain confused, and you will not be able to solve the issue. ...
Sending Access-Accept of id 205 to 128.186.252.11 port 32858 MS-MPPE-Recv-Key = 0x22e1319dea63f4410fe3ad33363dcca198536b1464c72ec70b83a73a1e1b0fab MS-MPPE-Send-Key = 0x9656612e871bcba6fe5057864962efd2fd0653971462962d4583b94a0216d3b8 EAP-Message = 0x031d0004 Message-Authenticator = 0x00000000000000000000000000000000 User-Name = "sding"
So... it works. If the user doesn't get online, blame the AP. Alan DeKok.