Running radsecproxy service on Windows
| Warning |
|---|
| (community |
...
| note: |
...
| this |
...
| page |
...
| is |
...
| still |
...
| under |
...
| construction |
...
| and |
...
| subject |
...
| to |
...
| changes) |
Currently, when deploying eduroam, you require a RADIUS (or RADIUS/TLS) server. Traditionally, deploying a Linux or BSD server has been the standard option. This gives you access to a variety of products that speak RADIUS (and RADIUS/TLS).
...
Running instructions (basics)
- Unzip zip file into
C:\radsecproxy - Copy
C:\radsecproxy\radsecproxy.conf-exampletoradsecproxy.conf - Edit configuration in
radsecproxy.conf - Run
cmd.exe(as user or admin) cd C:\radsecproxy- Execute
c:\radsecproxy\radsecproxy.exe -c ./radsecproxy.confIt'll take a little while to start, but then should return to command-line. You might see two warnings about secret length if you used short secrets (like 'testing' or 'testing123'). - Close cmd.
- Open your Task Manager, search for radsecproxy... it should be there
Windows Firewall
Windows servers come with an application firewall. On Windows 2019 in particular, a bug prevents NPS from properly accepting (and sending) packets over RADIUS (see Meraki Community and Microsoft topics on this). You should probably define four new policies (two inbound, two outbound) in the Windows Firewall:
...
To see how to set up a heartbeat for Windows, look at the Jisc topic here: https://communitysupport.jisceduroam.ac.uk/community/library/network-and-technology-service-docs/configuring-eduroam-heartbeat-your-visitor-network