From: Marian Jancar <marian.jancar@infonet.cz>
To: linux-kernel@vger.kernel.org
Subject: Problems with NAT
Date: Wed, 13 Dec 2000 17:23:39 +0100 [thread overview]
Message-ID: <3A37A28B.7AC31112@infonet.cz> (raw)
There is a problem with nat in at least 2.2.16 and 2.2.18. If you
specify routing first and nat second,
ip route add nat x.x.x.x via y.y.y.y
ip rule add from y.y.y.y nat x.x.x.x
the rule doesnt have an effect, ping to x.x.x.x says it got response
from y.y.y.y. With turned order of commands,
ip rule ...
ip route ...
it works.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-13 16:54 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=3A37A28B.7AC31112@infonet.cz \
--to=marian.jancar@infonet.cz \
--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
all inboxes | Powered by JetHome®