From owner-freebsd-net@freebsd.org  Tue Jan 17 19:34:35 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A93EBCB45FF
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue, 17 Jan 2017 19:34:35 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 972D412A9
 for <freebsd-net@FreeBSD.org>; Tue, 17 Jan 2017 19:34:35 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0HJYZPp079627
 for <freebsd-net@FreeBSD.org>; Tue, 17 Jan 2017 19:34:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 213869] when setting an ipsec policy with spdadd src[port],
 outbound traffic from 2049/tcp is not encrypted
Date: Tue, 17 Jan 2017 19:34:35 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jasonmader@gmail.com
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-213869-2472-GHrOFS5F4u@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213869-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-213869-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2017 19:34:35 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213869

--- Comment #12 from Jason Mader <jasonmader@gmail.com> ---
There might still be a bug even after the patch. I'm using the patch on an
NFSv4 server, and encountered a new NFSv4 mount that did not work. So I
reverted to [any] on the source in the policy and got the mount to succeed.

19:23:21.702627 IP6 coconut > safe: ESP(spi=3D0xb04a3109,seq=3D0x7), length=
 76
19:23:21.702666 IP6 safe.nfsd > coconut.849: Flags [S.], seq 3009240135, ack
1156380226, win 65535, options [mss 1440,nop,wscale 9,sackOK,TS val 1829320=
15
ecr 615648], length 0

--=20
You are receiving this mail because:
You are the assignee for the bug.=