From: kuznet@ms2.inr.ac.ru
To: gmaxwell@Martin.FL.US (Greg Maxwell)
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: NAT and 2.2?
Date: Thu, 25 Mar 1999 18:06:06 +0300 (MSK) [thread overview]
Message-ID: <199903251506.SAA32185@ms2.inr.ac.ru> (raw)
In-Reply-To: <Pine.GSO.3.96.990325081514.5266A-100000@da1server> from "Greg Maxwell" at Mar 25, 99 05:13:09 pm
Hello!
> Can the new IP ROUTE stuff in 2.2 do ONE-ONE NAT insted of the standard
> good ole MASQ (MANY-ONE)? I got hit with having to set up a nat solution
> by Saturday AM, and it looks like Linux is the only thing that could hit
> that deadline within budget.
ONE-ONE is the only thing, which ROUTE_NAT is able. It is supposed to be
used for site renumbering and to facilitate policy routing, rather
then to compress ip address space or to split load.
The setup is very easy: micro-howto may be found
at http://www.compendium.com.ar/policy-routing.txt
It is very small, but contains basic hints.
Also: ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.txt
> I'll also need it to pass through port numbers unmolested. :( (stupid
> state security).
I failed to parse it, but try to continue 8)
- it is stateless to be scalable. -> no dynamic nat, no load splitting.
- it does not touch packet payload to be fast and does not check
it to be not ambigous. -> no active ftp in one direction and no passive
in backward.
- it is not intended to remap only range of ports, though
it is possible with fwmark.
Alexey Kuznetsov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~1999-03-25 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.3.96.990325081514.5266A-100000@da1server>
1999-03-25 13:40 ` Michael Hasenstein
1999-03-25 15:06 ` kuznet [this message]
1999-03-25 17:38 ` lf
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=199903251506.SAA32185@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=gmaxwell@Martin.FL.US \
--cc=linux-kernel@vger.rutgers.edu \
/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
all inboxes | Powered by JetHome®