From owner-freebsd-standards@freebsd.org  Thu Jun  1 04:36:49 2017
Return-Path: <owner-freebsd-standards@freebsd.org>
Delivered-To: freebsd-standards@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 2DA45BF4FD2
 for <freebsd-standards@mailman.ysv.freebsd.org>;
 Thu,  1 Jun 2017 04:36:49 +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 1C15F7A3C0
 for <freebsd-standards@FreeBSD.org>; Thu,  1 Jun 2017 04:36:49 +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 v514am4a072553
 for <freebsd-standards@FreeBSD.org>; Thu, 1 Jun 2017 04:36:48 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-standards@FreeBSD.org
Subject: [Bug 219699] Issue with IPv6 and neighbor notification
Date: Thu, 01 Jun 2017 04:36:49 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: standards
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: paul@tmp.group
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-standards@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-219699-15-DiyPdg58EF@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219699-15@https.bugs.freebsd.org/bugzilla/>
References: <bug-219699-15@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-standards@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Standards compliance <freebsd-standards.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-standards>, 
 <mailto:freebsd-standards-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-standards/>
List-Post: <mailto:freebsd-standards@freebsd.org>
List-Help: <mailto:freebsd-standards-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-standards>, 
 <mailto:freebsd-standards-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jun 2017 04:36:49 -0000

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

--- Comment #1 from Paul G Webster <paul@tmp.group> ---
Just a clarification;=20

'because obviously, my assigned /64 could not reach there gateway, from wha=
t I
understand from the IPv6 folks I should be able to simply set the gateway to
the interface without such a hack, but once again realistically; no idea.'

If I do attempt to set the gateway on the interface, it cannot 'find' the
gateway almost like it was having trouble looking it up.

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