From owner-freebsd-net@FreeBSD.ORG Sun Dec 8 15:45:11 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E8052ED for ; Sun, 8 Dec 2013 15:45:11 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F02361B48 for ; Sun, 8 Dec 2013 15:45:10 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id rB8Fitdb027041 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 8 Dec 2013 07:44:58 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <52A493F1.6040700@freebsd.org> Date: Sun, 08 Dec 2013 23:44:49 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Sami Halabi , Victor Gamov Subject: Re: Netgraph ng_patch and ng_input: where to find packets? References: <5293E3E7.6090604@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Dec 2013 15:45:11 -0000 On 12/8/13, 6:43 PM, Sami Halabi wrote: > Hi Gamov, > Have got this to work? > If so would share configurations? > > Thanks in advance, > Sami > בתאריך 29 בנוב 2013 19:28, "Victor Gamov" כתב: > > if not then the way to track it it to put a breakpoint on the netgraph node that handles the packet and just single step through until you see where the packet goes.. kdb would give you a decent idea but a second machine (or a virtual machine) with kgdb would really show you what's going on.