[strongSwan] [strongSwan-dev] Support for Routing rule modification via IKE informational requests after IKE tunnel is setup with gateway

[Andreas Steffen]

Hi Ravi,

could you guide my to an RFC or Internet draft describing this dynamic
update of traffic selectors? Or are you referring to the IKEv2 Mobility
and Multihoming Protocol (RFC 4555 MOBIKE) which strongSwan has enabled
by default:

   https://www.strongswan.org/testing/testresults/ikev2/mobike/

Regards

Andreas

On 01.06.2016 17:02, Ravi Kanth Vanapalli wrote:
> Hi,
>     I wanted to know if Strongswan supports routing rule modification
> through means of IKE Informational requests after the IKE tunnel has
> been setup.
>
> eg scenario is
> i) UE completed IKE_SA_INIT exchange with gateway.
> ii) UE completed IKE_AUTH exchange with gateway.
>   iii) IKE tunnel is setup with some traffic selector range TSi and TSr
> iv) UE wants to modify the TSi and TSr.
> v) UE sends IKE Informational exchange with updated TSi and TSr to gateway..
>
> Does Strongswan support sending the line (v) listed above ?
> In other words is routing rule modification via IKE informational
> exchange supported in Strongswan  ?
>
> --
> Regards,
> RaviKanth
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.strongswan.org
> https://lists.strongswan.org/mailman/listinfo/dev
>

-- 
======================================================================
Andreas Steffen                         andreas.steffen at strongswan.org
strongSwan - the Open Source VPN Solution!          www.strongswan.org
Institute for Internet Technologies and Applications
University of Applied Sciences Rapperswil
CH-8640 Rapperswil (Switzerland)
===========================================================[ITA-HSR]==

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4275 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.strongswan.org/pipermail/users/attachments/20160602/c729936f/attachment.bin>