qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] Slirp reverse UDP firewall


From: Avi Kivity
Subject: Re: [Qemu-devel] [PATCH] Slirp reverse UDP firewall
Date: Thu, 14 Apr 2011 16:48:52 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.9

On 04/12/2011 07:38 PM, Jan Kiszka wrote:
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?

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.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]