All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matin Tamizi <mtamizi@gmail.com>
To: NetFilter <netfilter@lists.netfilter.org>
Subject: Re: Stateless NAT
Date: Thu, 9 Jun 2005 09:43:18 -0400	[thread overview]
Message-ID: <f68a416050609064333bebd9f@mail.gmail.com> (raw)
In-Reply-To: <9D532201-8173-474B-8281-1FA274AFC243@cuseeme.de>

Why can't we create a new target module to support stateless NAT for
NetFilter like the following link suggests?
https://lists.netfilter.org/pipermail/netfilter/2005-February/058950.html

I tried writing a target module, but I'm a bit baffled by how the
target modules work.  The existing target modules don't seem to have
any source to modify the packets.   If this is possible then the
NETMAP module should already do the job.  Assuming the NETMAP target
module does what its description states.

We should also be able to write a stateless NAT program using libipq. 
Even FreeBSD uses a user space program for NAT by using the divert
socket api.  However, I don't how to define any order in the programs
grabbing packets from the QUEUE.  In FreeBSD, instead of queueing the
packet is rerouted to an internal "divert" port which can be binded to
using the standard socket API, but divert socket are more expensive
than the NetFilter QUEUE solution.

I've found another solution to my problem without having to use NAT,
but it would have been nice if I could have used NAT since my solution
is rather contrived.

-Matin

On 6/8/05, codewarrior@cuseeme.de <codewarrior@cuseeme.de> wrote:
> 
> On Jun 8, 2005, at 8:56 AM, Guenter.Sprakties@team4.de wrote:
> >> You don't use netfilter. You use iproute2.
> >>
> >> http://linux-ip.net/html/nat-stateless.html
> > First your right, iproute2 is the best tool managing simple 1:1 NAT.
> > Second, is doesn't work because some guys decided to remove the
> > necessary
> > code out of the kernel.
> > So you HAVE to use netfolter, and I tell you:
> > First again, it didn't work. Second, no one of the guys out there
> > helps
> > you. I tried to get help, but nothing happend.
> > I think, natting is against their religion or something like this.
> > Take an old kernel and use iproute2, the most genial tool in all
> > the net
> > stuff.
> 
> 
> hello guenter,
> 
> thanks you for your answer , so i heard that it is
> not possible to run iproute2 under osx right ?
> 
> i got a script from my ISP
> http://www.xaranet.de/dl/xaranet-tunnel.sh
> 
> but you need iproute2  so there is no way  ?
> 
> 
> regards
> 
> marc
> 
> 
> ********************************************************
> opencuseeme /  peer2peer multiparty conferencing
> ********************************************************
> Marc Manthey
> D - 50672 Cologne
> West Europe
> office: 0049.221.355.80.32
> mobile: 0049.177.341.54.81
> www.let.de
> www.applehelpers.com
> aim://macfreak2004
> macfreak@jabber.org
> 
> 
> 
> 
> 
>


  reply	other threads:[~2005-06-09 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 15:27 Stateless NAT Matin Tamizi
2005-06-08  1:40 ` Feizhou
2005-06-08  6:56   ` Guenter.Sprakties
2005-06-08  7:20     ` codewarrior
2005-06-09 13:43       ` Matin Tamizi [this message]
2005-07-28 20:54         ` Matin Tamizi
  -- strict thread matches above, loose matches on Subject: below --
2005-02-24 11:11 John A. Sullivan III
2005-02-24 16:43 ` Jozsef Kadlecsik
2005-02-24 16:56   ` Sven Schuster
2005-02-24 19:08     ` Jozsef Kadlecsik

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=f68a416050609064333bebd9f@mail.gmail.com \
    --to=mtamizi@gmail.com \
    --cc=netfilter@lists.netfilter.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.