There seems to be some rumors floating around that stateless NAT exists in linux in a non-depreciated form (unlike iproute2) as of 2.6.24:

http://www.mail-archive.com/[email protected]/msg53070.html ...

However, I can't find any documentation on how this might work. Anyone have an idea of how this works?

  • 1
    Zow, the documentation for tc looks sparse! The tc action nat egress (assuming is the private IP and is the public IP) will do what you want, but getting the packets classified to allow the nat action to apply looks like more than I can glean from reading. W/o having the tools at hand I think that's the best I can say. Commented Jul 27, 2010 at 15:54
  • Ya, I think I am just going to go with the NO nat for the important stuff. It just didn't cross my mind that I could still NAT address even if they were assigned to an interface since the NAT is pre routing. Commented Jul 27, 2010 at 16:00

2 Answers 2


Are you sure iproute2 has been deprecated?

See this doc.

  • Yes I should have linked to that in my question. I was using that and the ip command shoots back a depreciation warning. Commented Jul 27, 2010 at 15:38
  • That doc also links to how to emulate stateless NAT with netfilter ... from what I can tell the author just made that up :-) Commented Jul 27, 2010 at 15:39
  • The Guide to IP Layer Network Administration with Linux is outdated. No more route NAT in Linux 2.6 onward.
    – hillu
    Commented Sep 6, 2012 at 19:16

I just implemented stateless NAT on a Debian/squeeze system based on a 2.6.32 kernel, I did not get it running with built-in features, but the xtables-addons-* packages that provide the RAWSNAT and RAWDNAT features were useful.

The ip-route(8) manpage contains a notice about route NAT no longer being supported in Linux 2.6.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .