home_server_pool Example

In v3, we have:

This translates to a load-balance section with name pool1, and the following contents.

home1, home2, and home3 should be instances of the radius module.

If you are using a Load-Balance-Key in v3, that can be translated to a v4 configuration by simply specifying an option to the load-balance section. For example, to load balance on Calling-Station-Id, the above pool1 configuration can be modified with one addition:

See the load-balance keyword documentation for more information.

In this configuration, pool1 is a virtual module. That is, it can be referred to by name as a module: pool1. This name can be used anywhere that a module name is allowed.

The need to use the pool as a module is the one major difference in proxying between v3 and v4. In v3, proxying was an automatic thing that happened when a special attribute got set. e.g. Proxy-To-Realm = …​, or Home-Server = …​.

In v4, proxying happens only when you explicitly configure the server to run the radius module. The simplest way to do this is to add a section:

And then set Auth-Type := proxy. See the sites-available/proxy example for more information.

In v3, we have:

This translates to the radius module, with name home1, and the following contents.

See the radius module for more information about its full configuration.

You can add home2, home3, etc. here. They do not need to be in separate files.