From owner-freebsd-net@freebsd.org  Mon May  9 14:07:40 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 E0224B3445F
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon,  9 May 2016 14:07:40 +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 D0BC81B7A
 for <freebsd-net@FreeBSD.org>; Mon,  9 May 2016 14:07:40 +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 u49E7e2n018431
 for <freebsd-net@FreeBSD.org>; Mon, 9 May 2016 14:07:40 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: Mon, 09 May 2016 14:07:41 +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: borjam@sarenet.es
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: cc
Message-ID: <bug-166255-2472-p0XgzQeaAg@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: Mon, 09 May 2016 14:07:41 -0000

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

borjam@sarenet.es changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |borjam@sarenet.es

--- Comment #8 from borjam@sarenet.es ---
Note that I'not comfortable at all with a mechanism to disable such an
important error message.

If I were in this situation I would either log to a remote location or inst=
all
a syslog version with more filtering capabilities (syslog-ng, for instance)
rather than pushing a potentially risky change to the base system.

My suggestion to at least make it a tunable is a last resort one ;)

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