From: Ray Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: IPTABLES + IPROUTE2
Date: Fri, 30 Jan 2004 12:50:48 +0200 [thread overview]
Message-ID: <1075459848.2000.123.camel@raylinux.internal> (raw)
In-Reply-To: <EHENIKBEJAMHPLPJOJBPMEFKDIAA.lucho@galix.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Fri, 2004-01-30 at 11:39, L.Malinov wrote:
> Hi Antony,
>
> According to the iproute2 manual, I can't do routing based on a destination
> port but based on the fwmark. So that's why I think I can achieve that alone
> with iproute2 only and I need iptables to put the mark as well. But in this
> case I'm not sure that this can be achieved on a box with one network card
> only or for traffic generated lacaly from the box. Any suggestions?
<<snip>>
What about the ROUTE patch in POM? You can basically route based on any
criteria possible with iptables.
--
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD 00EE 8757 EE47 F06F FB28
--
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-30 10:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 9:39 IPTABLES + IPROUTE2 L.Malinov
2004-01-30 10:50 ` Ray Leach [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 12:57 L.Malinov
2004-01-24 14:54 ` Antony Stone
2004-01-23 11:44 L.Malinov
2004-01-23 23:51 ` Antony Stone
2004-01-24 1:04 ` Ramin Dousti
2004-01-24 12:05 ` L.Malinov
2004-01-26 7:53 ` Klemen Kecman
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=1075459848.2000.123.camel@raylinux.internal \
--to=raymondl@knowledgefactory.co.za \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox