From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: netfilter-devel@lists.netfilter.org, "Artūras Šlajus" <x11@arturaz.net>
Subject: Re: Need an iptables module for hiding NAT.
Date: Mon, 5 Feb 2007 23:16:06 +0200 [thread overview]
Message-ID: <200702052316.14477@auguste.remlab.net> (raw)
In-Reply-To: <45C75479.3090605@arturaz.net>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Le lundi 5 février 2007 17:59, Artūras Šlajus a écrit :
> I need iptables module which would hide NAT. It means that all
> traffic being routed through the machine which is running netfilter
> and doing routing should be seen as originating from that host.
(...)
I think QEMU already does that when using the "userland" driver on the
host side for the guest NIC. As far as I understand, this is done using
an antique piece of BSD code known as slirp. It should not be very
complicated to reuse modify slirp to use a network card (the
internal-side NIC of the stealth NAT box) instead of a PPP interface
(as slirp originally did) or a virtual NE2000 (as QEMU does). A small
extra tweak will probably be needed to steal packets from Linux IP
stack.
Of course, it's not exactly hiding the NAT, since there is no more real
NAT.
> I hope somebody can help me, any shared thoughts about difficulty of
> doing such task and time involved would be appreciated (i'm a
> programmer myself, just not C and kernel ;-))
--
Rémi Denis-Courmont
http://www.remlab.net/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2007-02-05 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 15:59 Need an iptables module for hiding NAT Artūras Šlajus
2007-02-05 16:09 ` Carl-Daniel Hailfinger
2007-02-05 16:11 ` Artūras Šlajus
2007-02-05 21:04 ` Henrik Nordstrom
2007-02-05 21:35 ` Artūras Šlajus
2007-02-05 21:16 ` Rémi Denis-Courmont [this message]
2007-02-05 22:41 ` Henrik Nordstrom
2007-02-06 14:39 ` Artūras Šlajus
2007-02-09 2:53 ` Henrik Nordstrom
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=200702052316.14477@auguste.remlab.net \
--to=rdenis@simphalempin.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=x11@arturaz.net \
/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.