From owner-freebsd-net@freebsd.org  Tue May 10 11:34:19 2016
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 D603BB35C0F
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue, 10 May 2016 11:34:19 +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 C67FA1236
 for <freebsd-net@FreeBSD.org>; Tue, 10 May 2016 11:34:19 +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 u4ABYI1V036493
 for <freebsd-net@FreeBSD.org>; Tue, 10 May 2016 11:34:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 166255] [net] [patch] It should be possible to disable
 "promiscuous mode enabled" messages
Date: Tue, 10 May 2016 11:34:18 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 8.3-PRERELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: eugen@grosbein.net
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-166255-2472-k2l0DT8d11@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-166255-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-166255-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.22
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, 10 May 2016 11:34:19 -0000

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

--- Comment #10 from eugen@grosbein.net ---
(In reply to elofu17 from comment #9)

AFAIK, there is no such thing as "vlan promiscuous mode" in FreeBSD and only
parent interface can be placed to such mode. Not all vlans should get traff=
ic
promiscuously. In fact, none should as I need to send/receive DHCP traffic =
only
for selected vlans and promiscuous mode should not be needed for that, is i=
t?

OTOH, I have another applications utilizing BPF to send/receive traffic. It
should be possible to filter unneeded kernel logs. I can rewrite my patch to
make configuration loader tunnable and read-only at run time.

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