From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 15 16:11:25 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF5971065672 for ; Fri, 15 Jan 2010 16:11:25 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id 42BEB8FC17 for ; Fri, 15 Jan 2010 16:11:25 +0000 (UTC) Received: from vampire.homelinux.org (dslb-088-066-000-110.pools.arcor-ip.net [88.66.0.110]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MNQ45-1NTspO2cEj-006nw0; Fri, 15 Jan 2010 17:11:23 +0100 Received: (qmail 50931 invoked from network); 15 Jan 2010 16:11:23 -0000 Received: from f8x64.laiers.local (192.168.4.188) by laiers.local with SMTP; 15 Jan 2010 16:11:23 -0000 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Fri, 15 Jan 2010 17:11:23 +0100 User-Agent: KMail/1.12.4 (FreeBSD/8.0-RELEASE-p2; KDE/4.3.4; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201001151711.23061.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19QaoOPXI7t97XGn3Mqoi4PP1JPzmvK+5uXAmF AozbusFIY4TfOQ+bADkx1aeAG4KeW5WPh/jlgyWZuLhtXUIgAh RNP0Bi0wbm5cj+e3O5mUQ== Cc: q q Subject: Re: Q:possibility PFIL+mbuf use for packet spawning X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2010 16:11:25 -0000 On Friday 15 January 2010 12:26:06 q q wrote: > I'm using pfil as packet filter for packet modifications. > > Is it possible to spawn new packets to network from pfil using mbuf? You can call into ip_output with a new mbuf to send a new packet. See for example pf_send_tcp in contrib/pf/net/pf.c > Another question: im using m_append to change packet length and add > data(its working, at least server got longer message) but when i wireshark > clients packets(win machine) i see that i got acknoledge on older length > not on new one. Am i missunderstanding something? Assuming you are talking about tcp packets (otherwise there wouldn't be an ack), you have to alter the tcp header, checksums, etc. as well. Just adding data doesn't work. Regards, -- Max