addition to policy.conf

Alan Buxey A.L.M.Buxey at lboro.ac.uk
Wed Jun 6 13:25:30 CEST 2012


Each sites NAS should be configured to block EAP attacks or DoS or multitude of failures. But anyways, it doesn't matter for each END site what their LOCAL auth levels are - huge sites work 10k concurrent local campus users will have big numbers. The problem is the proxy packets as proxying is the Achilles heel where many bad things can happen. Remote sites not responding etc etc

Anyway, thus us just diversion. I saw no complaints when 'reject if not EAP' , for example, went into proxy.conf. noone is forced to use any of the existing policies (many dont!) However here we have a valid use case and many freeradius sites that will work better, out of the box, than other RADIUS solutions ;)

alan

--
This smartphone has free WiFi worldwide with eduroam, now that IS smart

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20120606/8db3922b/attachment.html>


More information about the Freeradius-Devel mailing list