From: Daisuke Nojiri <dnojiri@google.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Slirp reverse UDP firewall
Date: Tue, 19 Apr 2011 07:55:56 -0700 [thread overview]
Message-ID: <BANLkTinzNRwY7JUMm5vu=LQJBist5m-OdQ@mail.gmail.com> (raw)
In-Reply-To: <4DAADEBA.5070700@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
I'll take a look at libpcap and update the thread. Thanks, Avi.
Dai
On Sun, Apr 17, 2011 at 5:36 AM, Avi Kivity <avi@redhat.com> wrote:
> On 04/14/2011 11:04 PM, Daisuke Nojiri wrote:
>
>> 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.
>>
>>
> IMO this is the wrong direction. Integrating libpcap should be simple (a
> call to pcap_offline_filter()) and immediately satisfy all current and
> future firewalling needs.
>
>
> --
> error compiling committee.c: too many arguments to function
>
>
[-- Attachment #2: Type: text/html, Size: 1251 bytes --]
next prev parent reply other threads:[~2011-04-19 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 16:19 [Qemu-devel] [PATCH] Slirp reverse UDP firewall Daisuke Nojiri
2011-04-12 16:38 ` Jan Kiszka
2011-04-13 15:35 ` Daisuke Nojiri
2011-04-14 13:48 ` Avi Kivity
2011-04-14 14:08 ` Avi Kivity
2011-04-14 20:04 ` Daisuke Nojiri
2011-04-17 12:36 ` Avi Kivity
2011-04-19 14:55 ` Daisuke Nojiri [this message]
2011-04-13 20:52 ` Blue Swirl
2011-04-14 19:14 ` Daisuke Nojiri
2011-04-14 19:33 ` Stefan Berger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTinzNRwY7JUMm5vu=LQJBist5m-OdQ@mail.gmail.com' \
--to=dnojiri@google.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).