rlm_raw in 3.1.x
paul at freedomwifi.com.au
Mon Jul 6 14:37:03 CEST 2015
Thanks, yeah I had found that post. I guess it's not really of much help
though. Why is it wrong and what is a valid alternative? Seems as though
the dynamic clients module is a bit "cut off at the knees" in a public wifi
service provider scenario if all it can access is the src IP address.
One alternative is to set the dynamic network to all of the internet so the
nas devices don't get blocked and then handle rejections later in the
normal policies, but seems like wasted resources to have to process them
that far in when they could just be dropped here if they aren't registered
devices that could be checked by comparing other fields like nas name or
On Mon, Jul 6, 2015 at 8:30 PM, Matthew Newton <mcn4 at leicester.ac.uk> wrote:
> On Mon, Jul 06, 2015 at 07:56:28PM +0800, Paul Trappitt wrote:
> > Thanks for taking the time to reply, much appreciated. Sorry just to
> > confirm, do you mean rlm_raw works with 3.0.x?
> In case you've missed any previous discussion (this comes up every
> now and then), you're unlikely to get much support for rlm_raw...
> Matthew Newton, Ph.D. <mcn4 at le.ac.uk>
> Systems Specialist, Infrastructure Services,
> I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
> For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>
> List info/subscribe/unsubscribe? See
More information about the Freeradius-Devel