Hi,
There is any way to pass (via variables) some of the radius reply’s values to the ‘login’ script of the Hotspot profile, once the user is authenticated via Radius?
Thanks.
Hi,
There is any way to pass (via variables) some of the radius reply’s values to the ‘login’ script of the Hotspot profile, once the user is authenticated via Radius?
Thanks.
No, not directly. Hotspot scripts do not support arguments.
However, you could create a radius log and parse it, storing it’s contents into variables, then script could evaluate those variables.
How can I archive this? can you give me an example of “create a radius log and parse it, storing it’s contents into variables”?
Unfortunately, I am still working on this myself. It’s not a permanent solution, but temporary. Also, I’m curious as to if it could be done, and how it might work in the end.
Basically I had the idea of turning on radius logging (/system logging …), then creating a parser via Scripts to read the logged data and evaluate it’s contents.
I will post back if I’ve made some progress. Also, if anyone else has some ideas on parsing, post them and we’ll see what we can come up with.
Unfortunately, I am still working on this myself. It’s not a permanent solution, but temporary. Also, I’m curious as to if it could be done, and how it might work in the end.
Basically I had the idea of turning on radius logging (/system logging …), then creating a parser via Scripts to read the logged data and evaluate it’s contents.
I will post back if I’ve made some progress. Also, if anyone else has some ideas on parsing, post them and we’ll see what we can come up with.
Have you asked Mikrotik Support to implement such feature: dynamic creation of variables that would contain values of parameters sent (Request) and received (Response) via Radius, which would be accessible via ‘onlogin’ Hotspot script?
No I haven’t. Personally, I haven’t felt it was a pressing issue. While a good feature, I think Mikrotik needs to focus on stabilizing some core functions first ![]()