Closed drook closed 8 years ago
Just to prove that it's not my configs/unlang statements are broken, I've installed a freeradius 3.0.11 on a separated server, plugged it into the same database as the production one, configured it's files and this issue was reproduced. Seems like for some reason it affects only EAP exchange, at least I got this impression.
1) you are testing with md5 - dont, its not what the client is doing, use eg eapol_test (part of wpa_supplicant) to do an PEAP test like your client.
2) the AVPair SSID is being set in inner-tunnel.... the reply the AP sees is the outer tunnel (inner tunnel goes back to client) - so you need to copy the inner-tunnel SSID attribute to the outer tunnel. read the inner-tunnel config and you will clearly see the 2 parts of the config that you need to enable for this - in the old server this was copy_request_to_outer or somesuch...thats old/dead, use the new method now.,
On 9 November 2016 at 09:07, drook notifications@github.com wrote:
Just to prove that it's not my configs/unlang statements are broken, I've installed a freeradius 3.0.11 on a separated server, plugged it into the same database as the production one, configured it's files and this issue was reproduced. Seems like for some reason it affects only EAP exchange, at least I got this impression.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/FreeRADIUS/freeradius-server/issues/1833#issuecomment-259365168, or mute the thread https://github.com/notifications/unsubscribe-auth/ACE-VfgESx4woAXyRIHxoFzzCmNLb5LMks5q8Y1AgaJpZM4KtL_S .
@alanbuxey Google finds 0 (zero) occurences of _copy_request_toouter, and I don't see anything appropriate neither in inner-tunnel configuration, nor in default. Could you please demystify your comment and explicitly point me at the configuration directive that does the copying ?
Found it. It's _use_tunneledreply, and it's in the eap module, not in the _innertunnel, or default site configuration. Thanks, but ... nah, nevermind. Just thanks.
if you read the files (virtual server and eap module config) its all quite clear. you dont pay me for support so you get not 100% perfect replies.
in peap, you have copy_request_to_tunnel (to get things from outer to inner), and use_tunneled_reply (to copy from outer to inner). however, as noted, in 3.0.x you dont do this, instead, read inner-tunnel and enable these lines
#
#
#
#
#
On 10 November 2016 at 04:59, drook notifications@github.com wrote:
Found it. It's _use_tunneledreply, and it's in the eap module, not in the _innertunnel, or default site configuration. Thanks, but there's something wrong with your memory. Like really. :)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/FreeRADIUS/freeradius-server/issues/1833#issuecomment-259601961, or mute the thread https://github.com/notifications/unsubscribe-auth/ACE-VQ_0atCfYCvSU5ezL1ye7z6bHkk9ks5q8qSygaJpZM4KtL_S .
@alanbuxey
It also says, that
If you need to send a reply attribute in the outer session, the ONLY safe way is to set "use_tunneled_reply = yes", and then update the inner-tunnel reply.
depends on what you want to do - the basic rule in the new method copies ALL the stuff from inner to outer....which is exactly what the old code does..... but anyone caring about security/safety would ensure that they are using the attribute filter anyway to strip out all but the required :)
On 11 November 2016 at 11:40, drook notifications@github.com wrote:
@alanbuxey https://github.com/alanbuxey
It also says, that
If you need to send a reply attribute in the outer session, the ONLY safe way is to set "use_tunneled_reply = yes", and then update the inner-tunnel reply.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/FreeRADIUS/freeradius-server/issues/1833#issuecomment-259940188, or mute the thread https://github.com/notifications/unsubscribe-auth/ACE-VYXt9vKUAmKVfxXTq4nmrYXzVq5bks5q9FQ0gaJpZM4KtL_S .
Issue type
Defect/Feature description
I'm trying to restrict a wireless user to a specific SSID. I have a freeradius 3.0.11 server that was configured some time ago when it was running a 2.x version, and this feature was working, then I ported the configs. Now it doesn't work for some reason, and I'm desperately trying to figure out why. It has an PgSQL backend configured and pretty much all of my tweaks are saved there.
So, now about what do I see. Seems like when using radtest sequence everything is working as intended:
Everything is in place: Cisco-AVPair = "ssid=vivat" is present in Access-Accept message. But when it comes to the actual exchange with Cisco AP, it is present only in some messages, but not in the last Access-Accept message.
How to reproduce issue
Configure freeradius according to the https://wiki.freeradius.org/guide/SQL-HOWTO article. Add some users and groups. Try to restrict the user to join the specific SSID by setting the VSA cisco-avpair. Get the actual result: user is able to join just any SSID.
Output of
[radiusd|freeradius] -X
showing issue occurringFinal lines of the output below show that default site strips out the Cisco-AVPair message from a reply. It is unclear to me why. I asked in the mailing list but received no answer, so I think nobody know why this is happeningh, thus I am dealing with unexpected behaviour.