[strongSwan] solution to kernel_libipsec no local address found problem

Hi List, - strongswan version 5.5.3 - I have to use kernel_libipsec (because of Openssl FIPS validated crypto). - Must support local traffic selector does not include any local IP addr. Expand on the last bullet: - Peer's IP addr is 192.168.0.2, remote traffic selector 172.16.0.0/24 - My node

Re: [strongSwan] Should each StrongSwan have its own FreeRadius or should they share one?

Hello Michael, You brought up some very good points. I'm currently only using the authentication in RADIUS by utilising the username/password in the Radcheck table. I also make use of Radacct table to see for how long a user was connected, from which location the connection was made and to which

Re: [strongSwan] Should each StrongSwan have its own FreeRadius or should they share one?

Am 21.08.19 um 08:20 schrieb Houman: > Hello, > > I have multiple StrongSwan VPN servers setup and each of them has its own > FreeRadius server. Each of the freeradius servers then points to the > central database in a separate location. This works without any problem. > But I wonder if this is

[strongSwan] Should each StrongSwan have its own FreeRadius or should they share one?

Hello, I have multiple StrongSwan VPN servers setup and each of them has its own FreeRadius server. Each of the freeradius servers then points to the central database in a separate location. This works without any problem. But I wonder if this is the right approach after all. Maybe I should have