On Thu, Sep 27, 2018 at 5:27 PM, Onur GURSOY <onurgursoygyte@gmail.com> wrote:
Hello Matthew,
Yeah you right someond ( I also don't know who is) compile freeradious older version and don't go on devolopment,
So you mean you decide to use freeradious as a radius server , you should use docker ?
It depends. Judging from your questions, I assume you're not familiar with docker, including the fact that you need to rebuild the docker image for each configuration change (i.e. https://hub.docker.com/r/freeradius/freeradius-server/). Plus the fact that on windows docker would still use a linux VM, I'd suggest you not to use it. If, however, you're already familiar with docker, that's a different story.
Or you choose windows specific solution ?
That would probably be your best option, if you're using it for production environment and you only have windows machines. VM is also a good choice, assuming you'll put the database backend (I assume you'll be using this) on windows (not on the VM) as the backend would need much more resource compared to freeradius itself. The most resource-efficient way to run freeradius on windows for testing purposes now is probably using WSL (e.g. ubuntu on windows). Starting freeradius daemon on WSL requires some workarounds (i.e. you can't use 'service' or 'systemctl', need to create your own startup script or run the daemon manually on terminal), but it should be enough for testing purposes. And since you ask about cygwin, this is probably as close as you can get to it. -- Fajar