* [LARTC] iproute2 and kernel 2.2.x NAT
@ 2005-04-12 17:55 Nels Lindquist
0 siblings, 0 replies; only message in thread
From: Nels Lindquist @ 2005-04-12 17:55 UTC (permalink / raw)
To: lartc
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-04-12 17:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-12 17:55 [LARTC] iproute2 and kernel 2.2.x NAT Nels Lindquist
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.