From: Jan Kiszka <jan.kiszka@siemens.com>
To: Daisuke Nojiri <dnojiri@google.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Slirp reverse UDP firewall
Date: Tue, 12 Apr 2011 18:38:03 +0200 [thread overview]
Message-ID: <4DA47FEB.5070402@siemens.com> (raw)
In-Reply-To: <BANLkTikaXZHbkEsdqLepQdWqBxLQZr5=-w@mail.gmail.com>
On 2011-04-12 18:19, 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
No more stand-alone slirp arguments please. That syntax breaks when
instantiating >1 back-ends.
>
> -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.
Will we see a TCP firewall as well? Can we prepare for a more generic
infrastructure, or what makes UDP special?
Also, please break up in smaller bits (example: logging would be a
separate topic). And make sure that your patches aren't line-wrapped.
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-04-12 16:38 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 [this message]
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
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=4DA47FEB.5070402@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=dnojiri@google.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).