siteadmin:freeradius_realm_filtering
Differences
This shows you the differences between two versions of the page.
siteadmin:freeradius_realm_filtering [2022/12/07 08:13] – created admin | siteadmin:freeradius_realm_filtering [2025/02/13 09:24] (current) – admin | ||
---|---|---|---|
Line 16: | Line 16: | ||
</ | </ | ||
+ | =====How to stop proxying your own realm when handling both eduroam and govroam on the same server===== | ||
+ | |||
+ | There' | ||
+ | |||
+ | Stepping back a bit: if a RADIUS server that just handles eduroam then the rules are easy: | ||
+ | |||
+ | - If realm matches our own, authenticate locally. | ||
+ | - Proxy all other valid realms to Jisc. | ||
+ | - Reject the rest. | ||
+ | |||
+ | When you add govroam then you need to keep the traffic separate so that eduroam traffic goes to the Jisc eduroam NRPS and the govroam traffic goes to the Jisc govroam NRPS/ | ||
+ | |||
+ | - If realm matches our own and SSID is ' | ||
+ | - If realm is valid and SSID is ' | ||
+ | - If realm is valid and SSID is ' | ||
+ | - Reject the rest. | ||
+ | |||
+ | However, here you can see a case that's inappropriate: | ||
+ | |||
+ | If the RADIUS server is capable of doing explicit rejects then a rule can be added that says: | ||
+ | |||
+ | * If the SSID is ' | ||
+ | |||
+ | otherwise the third rule becomes: | ||
+ | |||
+ | * If realm is valid, is not our own and the SSID is ' | ||
+ | |||
+ | which means that, in the above case, inappropriate auths are now rejected by default. | ||
siteadmin/freeradius_realm_filtering.txt · Last modified: 2025/02/13 09:24 by admin