qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] netfilter
Date: Sat, 02 Jul 2005 12:51:13 -0700	[thread overview]
Message-ID: <1120333873.25189.44.camel@aragorn> (raw)

I was fiddling with getting FTP to work across user-net, and it seems to
me that there are some NAT issues with FTP, and DNS.

These specific issues can be fixed in slirp tcp_subr.c and elsewhere for
udp based DNS, but I'm wondering if this is the right way to go about
it. Perhaps the netfilter code should be shoehorned into slirp.
Netfilter already has several application level gateways and complete
configurability.

I'm sure having a full firewall between qemu and the guest/host OSes has
other applications as a sandbox for security analysis, besides just
making user-net work properly.

-- John.

             reply	other threads:[~2005-07-02 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02 19:51 John R. Hogerhuis [this message]
2005-07-02 21:26 ` [Qemu-devel] netfilter Henrik Nordstrom
2005-07-02 23:04   ` Henrik Nordstrom
2005-07-02 23:41   ` John R. Hogerhuis
2005-07-03  1:11     ` Paul Brook

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=1120333873.25189.44.camel@aragorn \
    --to=jhoger@pobox.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).