There are several types of filtering that can be done.

• Syntax
• Known bad realms
• Typos

This is the easiest and captures the most problematic Username string. Simple types such as @@, .. or illegal characters such as commas or underscores.

Use a regex to match a good realm.

• In the Service which proxies unknown requests to the NRPS
• Enter 'RADIUS:IETF' for the Type
• User-Name for the Name
• MATCHES_REGEX for the Operator
• ^[^@]*@([a-zA-Z0-9-]+\.)+[a-zA-Z]{2,6}$ for the Value

We keep a list of known bad realms in the Govroam FAQ.

• In the Service which proxies unknown requests to the NRPS
• Select <em>Matches ALL of the Following Conditions</em>
• Add lines for each Realm where
  • Type is 'RADIUS:IETF'
  • Name is 'User-Name'
  • Operator is 'CONTAINS'
  • Value is the realm e.g. '@hotmail.com'.

These are harder to do as they require spotting and adding each in turn. You can use your logs to see which realms are being sent up to the NRPS and then decide which are typos for the realm(s) you look after locally. This is also a good way to help users who are having problems.

• In the Service which proxies unknown requests to the NRPS
• Select <em>Matches ALL of the Following Conditions</em>
• Add lines for each Realm where
  • Type is 'RADIUS:IETF'
  • Name is 'User-Name'
  • Operator is 'CONTAINS'
  • Value is the realm e.g. '@halby.nit'.