Clients are varied, I've tried with android (running lineageos, relatively recent update) and windows 10 (yeah, I kinda expect that to be fucky). I also have some users using various mac hardware. The only thing that tests correctly is radtest and manual curl's.
On Saturday, November 17, 2018 at 3:54:25 PM UTC-6, 2stacks wrote: > > Apologies if Im asking things you've already answered but what is the > client that should be sending the password? Have you tried capturing the > traffic to see if the password is being sent? Did you say if testing with > radtest works? Perhaps its not a freeradius config issue but something > wonky with the client. > > On Sat, Nov 17, 2018, 4:33 PM Marty Plummer <[email protected] > <javascript:> wrote: > >> Even with using exactly and only what you have in the authorize...etc >> sections of >> sites-available/default, %{User-Password} still expands to empty. There >> has been >> no change to that regardless of what suggested changes I've made. >> >> On Saturday, November 17, 2018 at 1:42:08 PM UTC-6, Federico Capoano >> wrote: >>> >>> PS: >>> >>> On Saturday, November 17, 2018 at 8:28:29 PM UTC+1, Marty Plummer wrote: >>>> >>>> So is that authorize section the entire thing? as in, comment >>>> out/delete the defaults and >>>> replace it with that? >>>> >>> >>> Yes >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "OpenWISP" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
