From owner-freebsd-bugs@freebsd.org  Tue Mar  7 09:36:01 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-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 6E965D00DCF
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  7 Mar 2017 09:36:01 +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 5E85D13AB
 for <freebsd-bugs@FreeBSD.org>; Tue,  7 Mar 2017 09:36:01 +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 v279a1mc086223
 for <freebsd-bugs@FreeBSD.org>; Tue, 7 Mar 2017 09:36:01 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 217607] ng_cisco flow control messages and IPv6
Date: Tue, 07 Mar 2017 09:36:01 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: lukasz.wojcik@zoho.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 attachments.created
Message-ID: <bug-217607-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 09:36:01 -0000

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

            Bug ID: 217607
           Summary: ng_cisco flow control messages and IPv6
           Product: Base System
           Version: 11.0-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: lukasz.wojcik@zoho.com

Created attachment 180593
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180593&action=
=3Dedit
sketch of a patch fixing the issue

ng_cisco's cisco_notify() routine only sends flow control messages to nodes
connected via 'inet' hook, completely ignoring those connected via 'inet6'.
This poses some problem if peer node relies on link status information pass=
ed
from ng_cisco. I'd therefore like to suggest a patch (perhaps something sim=
ilar
to what I attached). All it does is to make ng_cisco node pass flow control
messages to *both* 'inet' and 'inet6' peers. It seems to me that it is both
possible and sensible to expect both mentioned hooks to be connected at the
same time.

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