From owner-freebsd-net@FreeBSD.ORG Tue Feb 8 16:48:16 2011 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16A1C1065673; Tue, 8 Feb 2011 16:48:16 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from sunner.semmy.ru (sunner.semmy.ru [IPv6:2a00:14d0:0:20::3]) by mx1.freebsd.org (Postfix) with ESMTP id 79CC68FC14; Tue, 8 Feb 2011 16:48:15 +0000 (UTC) Received: from dhcp170-205-red.yandex.net ([95.108.170.205]) by sunner.semmy.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.74 (FreeBSD)) (envelope-from ) id 1Pmqjd-00056l-BU; Tue, 08 Feb 2011 19:48:13 +0300 Message-ID: <4D5173CD.3040808@FreeBSD.org> Date: Tue, 08 Feb 2011 19:48:13 +0300 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Julian Elischer References: <4D4DCD1E.1050906@freebsd.org> <4D4DFC95.9010804@freebsd.org> <4D501198.6090901@FreeBSD.org> In-Reply-To: <4D501198.6090901@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Ivo Vachkov , FreeBSD Net Subject: Re: divert rewrite X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2011 16:48:16 -0000 07.02.2011 18:36, Sergey Matveychuk wrote: > 06.02.2011 4:42, Julian Elischer wrote: >> On 2/5/11 4:09 PM, Ivo Vachkov wrote: >>> Hello, >>> >>> How can I help? >> >> if you have ipv6 connectivity and experience, I have no experience or >> connectivity, with it so >> I'll be coding blind and will need a tester. >> If you have an application for IPV6 testing that would be even better. >> Divert is often used for NAT but that doesn't seem very useful for >> IPv6 and >> natd doesn't support it anyhow. > > Object :) > Divert is really useful way to get packets from firewall to userspace, > analyse or process them some way and put them back. Really I see no > other way for this for IPv6. I've tried ng_socket+ng_nat but there is no > easy way to put a packet back in firewall. Oops, I meant ng_socket+ng_ipfw here.