From owner-freebsd-bugs@FreeBSD.ORG  Tue Feb 10 10:55:52 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E56427C8
 for <freebsd-bugs@FreeBSD.org>; Tue, 10 Feb 2015 10:55:52 +0000 (UTC)
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 CC76FA22
 for <freebsd-bugs@FreeBSD.org>; Tue, 10 Feb 2015 10:55:52 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1AAtq8p084351
 for <freebsd-bugs@FreeBSD.org>; Tue, 10 Feb 2015 10:55:52 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 197511] BPF --> Interactions with Dhclient, Tcpdump, and
 Network Connections (Ping)
Date: Tue, 10 Feb 2015 10:55:52 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.1-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: garytivey512@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
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
Message-ID: <bug-197511-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 10:55:53 -0000

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

            Bug ID: 197511
           Summary: BPF --> Interactions with Dhclient, Tcpdump, and
                    Network Connections (Ping)
           Product: Base System
           Version: 10.1-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: garytivey512@gmail.com

Have noticed on a recent install of FreeBSD 10.1 network firewall (pf) ,by
accident, that if I enable tcpdump on the external interface, I can easily
obtain an IP address via Dhclient on a Comcast cable network. If I close the
Tcpdump program, I can no longer ping external ip's such as google dns, or the
IPV6 endpoint of a 6-4 tunnel. Once I restart the Tcpdump program, all
connectivity is restored. I believe the code in common is the bpf (Berkley
Packet Filter). 

Have observed the same behavior using FreeBSD 9.3 on the same hardware.
Seems rather odd that I need to have tcpdump running all the time on this
firewall. Condition is persistant through reboots. Devices noted in /dev are
bpf, and bpf0. Should there be more bpf devices? I remember a while back the
kernel options allowed a number option... is that still the case?

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