From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QASlp-0005Dr-JB for qemu-devel@nongnu.org; Thu, 14 Apr 2011 16:04:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QASlo-00004v-R4 for qemu-devel@nongnu.org; Thu, 14 Apr 2011 16:04:05 -0400 Received: from smtp-out.google.com ([216.239.44.51]:6900) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QASlo-0008WU-Ki for qemu-devel@nongnu.org; Thu, 14 Apr 2011 16:04:04 -0400 Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p3EK43rB003258 for ; Thu, 14 Apr 2011 13:04:03 -0700 Received: from yxl31 (yxl31.prod.google.com [10.190.3.223]) by wpaz13.hot.corp.google.com with ESMTP id p3EK2xes021872 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Thu, 14 Apr 2011 13:04:02 -0700 Received: by yxl31 with SMTP id 31so1169053yxl.41 for ; Thu, 14 Apr 2011 13:04:02 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4DA6FFE9.6010100@redhat.com> References: <4DA47FEB.5070402@siemens.com> <4DA6FB44.3020208@redhat.com> <4DA6FFE9.6010100@redhat.com> Date: Thu, 14 Apr 2011 13:04:02 -0700 Message-ID: From: Daisuke Nojiri Content-Type: multipart/alternative; boundary=000e0cd4c18c38173f04a0e66d02 Subject: Re: [Qemu-devel] [PATCH] Slirp reverse UDP firewall List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Jan Kiszka , qemu-devel@nongnu.org --000e0cd4c18c38173f04a0e66d02 Content-Type: text/plain; charset=ISO-8859-1 Hi, Avi, Complex and complete firewalling is probably out of my focus for now. I'm trying to introduce a simple reverse firewall functionality which filters outgoing patckets based on only destination address and port. Since Qemu doesn't have any reverse firewall currently, I believe this is a good addition and start. Dai On Thu, Apr 14, 2011 at 7:08 AM, Avi Kivity wrote: > On 04/14/2011 04:48 PM, Avi Kivity wrote: > >> Will we see a TCP firewall as well? Can we prepare for a more generic >>> infrastructure, or what makes UDP special? >>> >> >> >> If some generic firewall like BPF is available as a user library, perhaps >> we can integrate one instead of writing a new one from scratch. >> >> > Heck, you could even write a tcg backend for bpf instructions and run the > jit the firewall filter set. > > > -- > error compiling committee.c: too many arguments to function > > --000e0cd4c18c38173f04a0e66d02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Avi,

Complex and complete firewalling is probably ou= t of my focus for now. I'm trying to introduce a simple reverse firewal= l functionality which filters outgoing patckets based on only destination a= ddress and port. Since Qemu doesn't have any reverse firewall currently= , I believe this is a good addition and start.

Dai

On Thu, Apr 14, 2= 011 at 7:08 AM, Avi Kivity <avi@redhat.com> wrote:
On 04/14/2011 04:48 PM, Avi Kivity wrote:
Will we see a TCP firewall as well? Can we prepare for a more generic
infrastructure, or what makes UDP special?


If some generic firewall like BPF is available as a user library, perhaps w= e can integrate one instead of writing a new one from scratch.


Heck, you could even write a tcg backend for bpf instructions and run the j= it the firewall filter set.


--
error compiling committee.c: too many arguments to function


--000e0cd4c18c38173f04a0e66d02--