From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Slirp reverse UDP firewall
Date: Thu, 14 Apr 2011 15:33:38 -0400 [thread overview]
Message-ID: <4DA74C12.4010502@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTikaXZHbkEsdqLepQdWqBxLQZr5=-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On 04/12/2011 12:19 PM, Daisuke Nojiri wrote:
> This patch adds: -drop-udp, -allow-udp ADDR:PORT, -drop-log FILE
>
> e.g.) $ qemu -net user -drop-log qemu.drop -drop-udp -allow-udp
> 10.0.2.3:53 <http://10.0.2.3:53>
>
> -drop-udp enables usermode firewall for out-going UDP packats from a
> guest.
> All UDP packets except ones allowed by -allow-udp will be dropped. Dropped
> packets are logged in the file specified by FILE. PORT can be a single
> number
> (e.g. 53) or a range (e.g. [80-81]). If ADDR is ommitted, all
> addresses match
> the rule.
If you want to end up providing functionality like ebtables/iptables
does then you'll need to think of user-defined tables or 'labeled rules'
along with gotos/jumps -- not just for efficiency reasons but also
because strictly linear evaluation of rules doesn't cover all the cases.
Besides that you'd probably want a connection tracking system so that
you can for example enable only a few [UDP] ports of the VM to be
reachable yet can initiate any kind of traffic... A bigger undertaking
to say the least.
My $.02,
Stefan
[-- Attachment #2: Type: text/html, Size: 1996 bytes --]
prev parent reply other threads:[~2011-04-14 19:34 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
2011-04-13 20:52 ` Blue Swirl
2011-04-14 19:14 ` Daisuke Nojiri
2011-04-14 19:33 ` Stefan Berger [this message]
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=4DA74C12.4010502@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.