[strongSwan] Traffic selectors routing issue for IPv6 TS with 128 prefix

[Ts, Sachin (Nokia - IN)]

Hi Tobias,

Thanks for the response, will try them.
For more info, actually ours is a multi tunnel setup. We have three tunnels. 
For the first time when all three tunnel comes up, its working fine.
But when one of the tunnel bounces(down and up), the problem triggers. We 
observed that the route of previous tunnel is overwritten by the bounced 
tunnel route.

Please let me know your comments on this. Meanwhile I will test again and try 
to get more logs.

Thanks,
Sachin



-----Original Message-----
From: Tobias Brunner [mailto:tobias at strongswan.org]
Sent: Thursday, March 16, 2017 4:44 PM
To: Ts, Sachin (Nokia - IN) <sachin.ts at nokia.com>; users at lists.strongswan.org
Subject: Re: [strongSwan] Traffic selectors routing issue for IPv6 TS with 128 
prefix

Hi Sachin,

> We are facing problem in reaching traffic selectors when we use IPv6
> TS(Single host IP) with /128 prefix BUT whereas when we use subnets,
> its working fine.

Since the determining factor for the source IP is the local traffic selector, 
i.e. fc01:eab:xx::xx/128 (which I suppose is
fc01:eab:xx:z::92/128 in both cases), and the availability of a matching IP 
address, the source IP should be the same.

Try increasing the log level for the KNL subsystem to 2 (see [1]) and compare 
the output during the two scenarios.

Regards,
Tobias

[1] https://wiki.strongswan.org/projects/strongswan/wiki/LoggerConfiguration
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5338 bytes
Desc: not available
URL: <http://lists.strongswan.org/pipermail/users/attachments/20170316/1f5f6901/attachment.bin>