[strongSwan] Specifying RADIUS attributes per-connection?

[Tobias Brunner]

Hi Brent,

> 1.) The named connection that listens (and serves as a tunneled gateway)
> on 203.0.113.1 should route through 203.0.113.1 to the RADIUS server,
> and 203.0.113.2 should route through 203.0.113.2 to the RADIUS server,
> so they get detected as unique NAS addresses. 203.0.113.2 should not
> route through 203.0.113.1 to the RADIUS server, and vice versa. This is
> to ensure that the correct NAS (and therefore the correct set of
> authentications) can be detected by RADIUS.

Can't you just use the appropriate attribute(s) in the requests from
strongSwan to make that distinction?

Regards,
Tobias