From: "John A. Sullivan III" <jsullivan@opensourcedevelopmentcorp.com>
To: Security Support Center <ssc@earth.com.br>
Cc: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: choose interface based on port
Date: Sat, 18 Dec 2004 23:18:55 -0500 [thread overview]
Message-ID: <1103429935.2031.61.camel@localhost> (raw)
In-Reply-To: <200412190132.52221.ssc@earth.com.br>
On Sat, 2004-12-18 at 22:32, Security Support Center wrote:
> Hello All,
>
>
> I'm having some problems on creating something that I thought, would not be so
> dificult.
>
> I have a firewall that holds 4 interfaces, and 2 of them are links to the
> internet.
>
> I want use link 1 for navigation (80 port) and link 2 for all the rest. But I
> can't get it done.
>
> I already tried lots of rule types, search internet, googled, etc but got
> nothing.
>
> Can anybody give me a light on this
>
>
> Tank you all in advance...
>
>
> Alberto
Hi, Alberto. I'm afraid I don't have time to look up the details but I
think you will be able to do what you want to do with iproute2 and
packet marking. The details will be in a file named ip-cref.ps in the
rules section. On my RedHat 9.0 distribution it is
/usr/share/doc/iproute-2.4.7/ip-cref.ps. You can also find a brief
slide show on using it with iptables and *swan in the training section
of the ISCS network security management web page at
http://iscs.sourceforge.net
Good luck - John
--
John A. Sullivan III
Open Source Development Corporation
Financially sustainable open source development
http://www.opensourcedevel.com
next prev parent reply other threads:[~2004-12-19 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 3:32 choose interface based on port Security Support Center
2004-12-19 4:18 ` John A. Sullivan III [this message]
2004-12-19 9:08 ` Frank Gruellich
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=1103429935.2031.61.camel@localhost \
--to=jsullivan@opensourcedevelopmentcorp.com \
--cc=netfilter@lists.netfilter.org \
--cc=ssc@earth.com.br \
/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