linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 and route nat. Who know what is going on?
Date: Fri, 19 Nov 2004 19:31:34 +0300	[thread overview]
Message-ID: <pan.2004.11.19.16.31.34.51328@altlinux.ru> (raw)
In-Reply-To: 200411191720.13423.pvolkov@mics.msu.su

On Fri, 19 Nov 2004 17:20:13 +0300, Peter Volkov Alexandrovich wrote:

> Short question: Must "route nat", mentioned in ip-cref documentation coming 
> with iproute2 package, work with 2.6.9 kernel?

Support for CONFIG_IP_ROUTE_NAT was removed from the kernel - it has been
broken by some networking changes, and nobody bothered to fix it.

See this thread in linux-netdev:

http://marc.theaimsgroup.com/?l=linux-netdev&m=109582576330019&w=2

You can use netfilter (iptables etc.) for NAT and more, but probably it
will consume more resources than the old "route nat" code.


  reply	other threads:[~2004-11-19 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 14:20 2.6 and route nat. Who know what is going on? Peter Volkov Alexandrovich
2004-11-19 16:31 ` Sergey Vlasov [this message]
2004-11-20  6:17   ` 2.6 and route nat. Now I know. It's dead Peter Volkov Alexandrovich

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=pan.2004.11.19.16.31.34.51328@altlinux.ru \
    --to=vsu@altlinux.ru \
    --cc=linux-kernel@vger.kernel.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).