siteadmin:radius_troubleshooting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| siteadmin:radius_troubleshooting [2017/10/10 10:10] – admin | siteadmin:radius_troubleshooting [2019/08/28 13:32] (current) – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ======General Troubleshooting====== | ||
| + | |||
| + | =====Common Problems==== | ||
| + | |||
| + | * The govroam monitoring system should be sending ICMP and RADIUS requests to your servers quite frequently (several times every five minutes). So you should be able to see these in your firewall logs or using Wireshark on your server. If you can't then check your firewall settings to allow ICMP echo/ | ||
| + | |||
| + | * A log message similar to: " | ||
| ====Rejected authentication requests==== | ====Rejected authentication requests==== | ||
| Line 33: | Line 40: | ||
| NAS-Port | NAS-Port | ||
| NAS-Port-Type | NAS-Port-Type | ||
| + | Service-Type | ||
| < | < | ||
| Line 77: | Line 85: | ||
| </ | </ | ||
| + | |||
| + | So the solution to the problem of failed authentications is to NOT filter out certain attributes and the spec says that they ought to be. Which is correct? The best advice is to filter out these attributes when proxing outwards but if there are any authentication issues with remote sites that you're struggling to fix then consider removing the filter to see what happens. | ||
| + | |||
| + | At the same time ensure that your RADIUS is NOT configured to expect these extra attributes. It WILL be possible to run a service with just the key attributes mentioned in the spec. | ||
siteadmin/radius_troubleshooting.1507630240.txt.gz · Last modified: 2017/10/10 10:10 by admin
