Thanks David. Didn't have time to look into this.
On Thu, Nov 29, 2018 at 06:44:52PM -0500, David Hill wrote:
> On Wed, Nov 28, 2018 at 07:12:56PM -0200, Martin Pieuchot wrote:
> > On 25/11/18(Sun) 10:52, David Hill wrote:
> > > On Sat, Oct 27, 2018 at 05:35:16PM +0200, Mark Patruck wrote:
> > > >
On Wed, Nov 28, 2018 at 07:12:56PM -0200, Martin Pieuchot wrote:
> On 25/11/18(Sun) 10:52, David Hill wrote:
> > On Sat, Oct 27, 2018 at 05:35:16PM +0200, Mark Patruck wrote:
> > > I've found the reason for the error message
> > >
> > > iked[24455]: pfkey_write: writev failed: Invalid argument
> >
On 25/11/18(Sun) 10:52, David Hill wrote:
> On Sat, Oct 27, 2018 at 05:35:16PM +0200, Mark Patruck wrote:
> > I've found the reason for the error message
> >
> > iked[24455]: pfkey_write: writev failed: Invalid argument
> > iked[24455]: pfkey_write: writev failed: Invalid argument
> >
> > that co
On Sat, Oct 27, 2018 at 05:35:16PM +0200, Mark Patruck wrote:
> I've found the reason for the error message
>
> iked[24455]: pfkey_write: writev failed: Invalid argument
> iked[24455]: pfkey_write: writev failed: Invalid argument
>
> that comes up when the Child SA expires. (this affects 6.4 and
I've found the reason for the error message
iked[24455]: pfkey_write: writev failed: Invalid argument
iked[24455]: pfkey_write: writev failed: Invalid argument
that comes up when the Child SA expires. (this affects 6.4 and -current)
It appears when using a tap interface != default enc0 (for exam
