[strongSwan] received TS_UNACCEPTABLE notify, no CHILD_SA built

[Noel Kuntze]

Hi,

Check the logs of the remote side.
It means the remote peer did not like the proposed traffic selector. It was probably outside of the network range that its own configuration allows, meaning narrowing failed.

Kind regards

Noel


On 16.01.2018 07:25, Sujoy wrote:
> Hi Noel,
> 
> Same strongswan 5.3.3 configuration working in my VM(client) to desktop server. But not working from my OpenWRT to Global IP used nated Linux server. Can you help me to solve this. 
> 
> what means "received TS_UNACCEPTABLE notify, no CHILD_SA built"
> 
> Server config file.
> 
> 
> 
> 
> Thanks & Regards
> 
> Sujoy
> 
> On Thursday 04 January 2018 03:38 AM, Noel Kuntze wrote:
>> Hi,
>>
>> Only on the responder.
>> If you use dpd and enforce UDP encapsulation, you do not need to open any ports on the initiator side.
>> Refer to the UsableExamples wiki page[1] for example configurations that are usable in the real world.
>>
>> Kind regards
>>
>> Noel
>>
>> [1] https://wiki.strongswan.org/projects/strongswan/wiki/UsableExamples
>>
>> On 28.12.2017 08:51, Sujoy wrote:
>>> Hi All,
>>>
>>>
>>> We want to implement StrongSwan,with IPsec in OpenWRT. IPSec server will be running in CentOS and the OpenWRt router will connect to it using VPN. I have configured the server part, struggling to configure the client part. Do we need to open port 4500 for this first.
>>>
>>> Anyone can suggest any solution for this.
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.strongswan.org/pipermail/users/attachments/20180116/38050d1e/attachment.sig>