From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: "Zane C. B." <zanecb@midwest-connections.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: How would I go about doing this?
Date: Mon, 17 Oct 2005 15:33:20 -0400 [thread overview]
Message-ID: <1129577600.2583.62.camel@localhost> (raw)
In-Reply-To: <20051017133705.00001114@mwc-acomputer>
On Mon, 2005-10-17 at 13:37 -0500, Zane C. B. wrote:
> I have two routers. The main router than everything goes through and a
> second router that I want to route some traffic through depending on the
> originating IP#.
>
> The second router has filtering and the like running on it.
>
> For traffic coming from a specific IP# and hitting the main router, I
> want it then to be routed out through the second router.
>
> Currently I got it working for port 80, using iptables, since squid is
> setup transparently on the filtering router. The command I am using is
> this... iptables -t nat -A PREROUTING -s <machine to filter for> -p tcp
> --destination-port 80 -j DNAT --to-destination <filtering router>. This
> works, but only for like web or the like which has a transparent squid
> setup to take care of it.
>
> That works for right now, but what I want to accomplish is to have the
> main router kick packets, from specified IP#, out to the secondary
> router.
>
If I understand you correctly, iproute2 is your friend. You can
probably find the documentation on it in a file in your distribution
named ip-cref.ps. You can also find a training slide show in the
training section of the ISCS open source network security management web
page (http://iscs.sourceforge.net). Hope this helps - John
--
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@opensourcedevel.com
Financially sustainable open source development
http://www.opensourcedevel.com
prev parent reply other threads:[~2005-10-17 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 18:37 How would I go about doing this? Zane C. B.
2005-10-17 19:33 ` John A. Sullivan III [this message]
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=1129577600.2583.62.camel@localhost \
--to=jsullivan@opensourcedevel.com \
--cc=netfilter@lists.netfilter.org \
--cc=zanecb@midwest-connections.com \
/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.