From owner-freebsd-pf@freebsd.org  Fri Nov  6 10:08:53 2015
Return-Path: <owner-freebsd-pf@freebsd.org>
Delivered-To: freebsd-pf@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 D1D74A270C7
 for <freebsd-pf@mailman.ysv.freebsd.org>; Fri,  6 Nov 2015 10:08:53 +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 BEF4014C1
 for <freebsd-pf@FreeBSD.org>; Fri,  6 Nov 2015 10:08:53 +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 tA6A8rUU010242
 for <freebsd-pf@FreeBSD.org>; Fri, 6 Nov 2015 10:08:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-pf@FreeBSD.org
Subject: [Bug 204248] PF Does not work nat in FreeBSD 10.2
Date: Fri, 06 Nov 2015 10:08:53 +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: 10.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kp@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-204248-17777-aZwZkLpMZn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204248-17777@https.bugs.freebsd.org/bugzilla/>
References: <bug-204248-17777@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-pf@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
 \(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pf/>
List-Post: <mailto:freebsd-pf@freebsd.org>
List-Help: <mailto:freebsd-pf-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 10:08:53 -0000

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

--- Comment #3 from Kristof Provost <kp@freebsd.org> ---
It looks like you did that right.

Can you attach network captures, made on the host machine on both hn0 and hn1
interfaces? I'd like to try to figure out what's happening (or not happening)
to break the NAT.

This should do the trick:
tcpdump -n -i hn0 -s0 -w hn0.pcap &
tcpdump -n -i hn1 -s0 -w -hn1.pcap &

Then try to run a ping to 8.8.8.8 on the windows 7 machine.

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