building stateless nat with iptools

Hi!

I'm struggling building a simple stateless NAT with iptools with a
2.6.39
I've read on some forum that the feature is now removed, hence I
should use netfilter.
Is that true?

PS:
For DNAT, when I'm trying to input
ip route add nat 10.0.55.2 via 192.168.44.2
it says: RNETLINK answers: invalid argument

Thanks.

On May 23, 12:21*pm, jprudent <jprud...@gmail.com> wrote:
> Hi!
>
> I'm struggling building a simple stateless NAT with iptools with a
> 2.6.39
> I've read on some forum that the feature is now removed, hence I
> should use netfilter.
> Is that true?
>
> PS:
> For DNAT, when I'm trying to input
> ip route add nat 10.0.55.2 via 192.168.44.2
> it says: RNETLINK answers: invalid argument
>
> Thanks.

oh yes it's true, rtfm.

Hi,

> I'm struggling building a simple stateless NAT with iptools with a
> 2.6.39
> I've read on some forum that the feature is now removed, hence I
> should use netfilter.
> Is that true?

Yes, pretty much everything is done nowadays with iptables, the command for netfilter.
It has an ipv4 command (iptables) and an ipv6 command (ip6tables).

Read the docs at http://www.netfilter.org/documentation/index.html

Bonno

Hello,

jprudent a écrit :
>
> I'm struggling building a simple stateless NAT with iptools with a
> 2.6.39
> I've read on some forum that the feature is now removed, hence I
> should use netfilter.
> Is that true?

The best place to ask is the netfilter list. However I'll write a quick
answer.

As others said, the old stateless NAT controlled by the 'ip' tool, was
removed a long time ago. Since 2.6.24 it was replaced by a new stateless
NAT controlled by the 'nat' action of the 'tc' tool.

There is no stateless NAT support by iptables/netfilter in the mainline
kernel. However raw NAT targets RAWSNAT and RAWDNAT are available from
xtables-addons (which replaced the old patch-o-matic).