From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Route packets by source IP
Date: Wed, 19 Mar 2008 16:19:40 -0500 [thread overview]
Message-ID: <47E1836C.7050707@riverviewtech.net> (raw)
In-Reply-To: <43cba8b55bae94158c0580f06e368ea4@localhost>
On 03/19/08 13:21, Franck JONCOURT wrote:
> This is perhaps not a good way to do, but I was thinking about using
> the __ip route__ command.
>
> ip route add 192.168.2.0/24 via 192.168.0.2
>
> where 192.168.2.0/24 would be the B1 network and 192.168.0.2 would be
> the B2 ip address.
>
> Is that wrong ?
"ip route" routes traffic based on destination IP address not
necessarily the network that it would pass through to get there. So if
you have traffic headed to my web server, you can not use "ip route" to
get it there with out specifying my servers IP address / subnet in the
ip route command.
Grant. . . .
next prev parent reply other threads:[~2008-03-19 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 12:01 Route packets by source IP Steffen Heil
2008-03-18 14:18 ` Grant Taylor
2008-03-19 18:21 ` Franck JONCOURT
2008-03-19 21:19 ` Grant Taylor [this message]
2008-03-19 22:03 ` Steffen Heil
2008-03-20 0:02 ` Grant Taylor
2008-03-20 0:30 ` Steffen Heil
2008-03-20 14:42 ` Grant Taylor
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=47E1836C.7050707@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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