From owner-freebsd-ports-bugs@freebsd.org  Thu Aug  3 11:02:41 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@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 8570ADAE899
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Thu,  3 Aug 2017 11:02:41 +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 6CC11727EC
 for <freebsd-ports-bugs@FreeBSD.org>; Thu,  3 Aug 2017 11:02:41 +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 v73B2fwV074425
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 3 Aug 2017 11:02:41 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 221091] security/ike: iked fails to run after FreeBSD 11.1
 upgrade (socket set udp-encap non-ike option failed)
Date: Thu, 03 Aug 2017 11:02:41 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: needs-qa
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ae@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback? merge-quarterly?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-221091-13-qYtEV7wupT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221091-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-221091-13@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-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Aug 2017 11:02:41 -0000

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

--- Comment #4 from Andrey V. Elsukov <ae@FreeBSD.org> ---
(In reply to Darryn Nicol from comment #3)
> When I establish a tunnel I'm picking up an IP address on the remote LAN =
via
> DHCP. I can confirm this by checking the assigned IP on my tap0 device. B=
ut
> any attempt to use a network resource over the tunnel times out. I've
> noticed that trying to display a route with 'route get <ip>', even to a
> local lan address, takes about 44 seconds while connected to the tunnel, =
but
> less than a second when the tunnel is not established.

Use '-n' flag to avoid name resolution.
There are several things that can help with further debugging:
1. Look at the output of `netstat -rn`
2. Look at the output of `setkey -D` and `setkey -DP`
3. Use tcpdump on if_enc(4) interface to see what is going trough IPsec.
4. Check your firewall rules.

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