Re: [strongSwan] INTERNAL_ADDRESS_FAILURE on StrongSwan Windows Server

2019-01-17 Thread Tobias Brunner
Hi, This is probably the more serious issue: > 03[KNL] setting WFP SA SPI failed: 0x80320035 > 03[IKE] unable to install IPsec policies (SPD) in kernel See [1]. Regards, Tobias [1] https://wiki.strongswan.org/issues/2750

Re: [strongSwan] INTERNAL_ADDRESS_FAILURE on StrongSwan Windows Server

2018-12-22 Thread Ling Wyh
That takes me one step further, thank you. The IPv4 address pool loads. The client authenticates okay. Then an error occurs, "installing route for policy 0.0.0.0/0 === 10.9.0.1/32 failed." The intention in this scenario is that the client should connect to the entire Internet via the

Re: [strongSwan] INTERNAL_ADDRESS_FAILURE on StrongSwan Windows Server

2018-12-21 Thread Tobias Brunner
Hi, > This produce an error INTERNAL_ADDRESS_FAILURE (identities anonymized): > ... > Do you know what I need to correct to prevent this error? Did you load the address pool with swanctl --load-pools? (Using --load-all also works.) Check with --list-pools if the pool is loaded. Regards,

[strongSwan] INTERNAL_ADDRESS_FAILURE on StrongSwan Windows Server

2018-12-20 Thread Ling Wyh
Greetings, I am working on installing StrongSwan 5.7.1 on Windows Server, based on the instructions at https://wiki.strongswan.org/projects/strongswan/wiki/Windows. My swanctl.conf is as follows (identities anonymized): connections { rw-eap { local { auth = pubkey certs = server.crt id =