From: "Nels Lindquist" <nlindq@maei.ca>
To: lartc@vger.kernel.org
Subject: [LARTC] iproute2 and kernel 2.2.x NAT
Date: Tue, 12 Apr 2005 17:55:58 +0000 [thread overview]
Message-ID: <425BB74C.15884.553F0D2@localhost> (raw)
Hi there.
I'm trying to implement NAT on a 2.2 kernel using iproute2 according
to Appendix C of the IP Command Reference that comes with iproute2.
We're also moving to a multiple uplink configuration which
complicates things a bit.
The kernel is 2.2.27-rc2, built with the various advanced routing
options (except for large routing tables) turned on. It seems to be
working with the multiple path stuff; I've created lookup tables for
each external interface and the routing is working properly.
I've tried adding a NAT host with "ip route add nat [external ip] via
[internal ip]" and "ip r sh table local" indicates that the command
was accepted:
nat [external ip] via [internal ip] scope host
If I try and ping the NAT ip from the router, I get:
connect: Invalid argument
Not sure if that's expected behavour or not. The next part is
tricky; with the multipath routing set up, I want packets from one
particular internal server to only be NATted if they go out via one
of the interfaces, but not NATted if they go out via the other.
The "ip rule" syntax allows for a source interface and ip address,
but not a destination interface. Is there any way to set this up the
way I want?
Am I barking up the wrong tree entirely?
----
Nels Lindquist <*>
Information Systems Manager
Morningstar Air Express Inc.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-04-12 17:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=425BB74C.15884.553F0D2@localhost \
--to=nlindq@maei.ca \
--cc=lartc@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 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.