Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Dec 2016 15:15:15 +0300
From:      Slawa Olhovchenkov <slw@zxy.spb.ru>
To:        "Andrey V. Elsukov" <ae@FreeBSD.org>
Cc:        freebsd-net@FreeBSD.org, Eugene Grosbein <eugen@grosbein.net>
Subject:   Re: [RFC/RFT] projects/ipsec
Message-ID:  <20161211121515.GE31311@zxy.spb.ru>
In-Reply-To: <4f8ad6e3-8028-8656-d286-caa391960632@FreeBSD.org>
References:  <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> <584D18D1.8090400@grosbein.net> <36fa749c-f284-1d96-704c-b7118a574dd0@FreeBSD.org> <20161211115802.GD31311@zxy.spb.ru> <4f8ad6e3-8028-8656-d286-caa391960632@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 11, 2016 at 03:09:28PM +0300, Andrey V. Elsukov wrote:

> On 11.12.2016 14:58, Slawa Olhovchenkov wrote:
> >> No. An encapsulated by gif(4) packet is considered as own packet. The
> >> described change is related to transport mode policies, that are match
> >> forwarded packets, i.e. when source and destination addresses are not
> >> our own. In this case we can't handle the returned packets.
> > 
> > What difference with source packets?
> > Whu you can handle sourced and can't handle returned packets?
> 
> IPsec is a set of protocol handlers - ESP/AH/IPcomp. Inbound packets are
> handled by security association with given destination address and SPI.
> If returned packets aren't destined to your address, protocol handlers
> will not handle them.

SA can't contains not may address? Surpised to me.
Or I missunderstund you.

> Outbound packets are handled by matching security policy. A needed
> security association are looking using the address selector from
> security policy. If security association that matches to a packet is
> found, a packet will be handled by protocol handler.
> 
> -- 
> WBR, Andrey V. Elsukov
> 






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161211121515.GE31311>