From: Taylor Grant <gtaylor@riverviewtech.net>
To: Stephen Beck <becks@marietta.edu>
Cc: netfilter@lists.netfilter.org
Subject: Re: help with fast nat
Date: Wed, 13 Apr 2005 19:25:26 -0500 [thread overview]
Message-ID: <425DB876.2050903@riverviewtech.net> (raw)
In-Reply-To: <Pine.GSO.4.58.0504131520420.25950@mcnet.marietta.edu>
What system is doing the pinging (IP / subnet) and what is it pining (IP / subnet)?
> [root@dorm-test ~]# ip route add 10.0.31.5/32 via 10.0.30.5
If you were pinging 10.0.31.5 passing through this router where 10.0.31.x/24 was on a different subnet and you told this router that 10.0.31.5 was accessible via 10.0.30.5 (the system doing the ping) you just told the router to loop the traffic back on the system doing the pinging.
> [root@dorm-test ~]# ip rule add from 10.0.30.5 nat 10.0.31.5
I'm not sure what you are hoping to accomplish by doing this. This will make any traffic coming from 10.0.30.5 (the system doing the pinging?) appear as if it is coming from 10.0.31.5 which would cause the router to send the traffic back to the 10.0.31.x/24 network.
I have a feeling what you might have done (if I understand what you have written here correctly) is effectively do a double loop back as in the 10.0.30.5 system's traffic loops back on it's self at the router as does the 10.0.31.5 system's traffic loop back on it's self at the router too.
There really is not enough information to try to help you, but based on what I have seen this is what I deduce. I hope that will help you in some way.
Grant. . . .
next prev parent reply other threads:[~2005-04-14 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 19:45 help with fast nat Stephen Beck
2005-04-14 0:25 ` Taylor Grant [this message]
2005-04-14 7:42 ` Filip Sneppe
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=425DB876.2050903@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=becks@marietta.edu \
--cc=netfilter@lists.netfilter.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.