From: Patrick McHardy <kaber@trash.net>
To: linux@arcoscom.com
Cc: lartc@mailman.ds9a.nl, netfilter-devel@lists.netfilter.org
Subject: [LARTC] Re: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues
Date: Wed, 13 Dec 2006 09:17:02 +0000 [thread overview]
Message-ID: <457FC50E.70009@trash.net> (raw)
In-Reply-To: <44824.195.55.244.106.1166001170.squirrel@www.arcoscom.com>
ArcosCom Linux User wrote:
> Then, the actual and updated and maintained substitute for ROUTE is using
> CONNMARK and/or MARK and then add filters/rules to routes table with ip.
> Am I in the truth?
That has always been the better way. The route target is a hack, I'm
don't know why it exists at all.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-12-13 9:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 19:44 [LARTC] iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues ArcosCom Linux User
2006-12-12 8:24 ` [LARTC] " ArcosCom Linux User
2006-12-12 8:34 ` Patrick McHardy
2006-12-13 8:31 ` ArcosCom Linux User
2006-12-13 8:38 ` Patrick McHardy
2006-12-13 9:12 ` ArcosCom Linux User
2006-12-13 9:17 ` Patrick McHardy [this message]
[not found] ` <Pine.LNX.4.64.0612282158360.16672@bizon.gios.gov.pl>
2007-01-10 5:58 ` Patrick McHardy
[not found] ` <Pine.LNX.4.61.0701101233080.3029@yvahk01.tjqt.qr>
2007-01-10 12:53 ` Patrick McHardy
2007-01-10 13:15 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, ArcosCom Linux User
2007-01-10 13:21 ` ArcosCom Linux User
2007-01-25 17:41 ` Andrew Beverley
[not found] ` <45C005EB.1040704@netfilter.org>
2007-02-09 13:37 ` Andrew Beverley
[not found] ` <Pine.LNX.4.64.0702091741250.9884@bizon.gios.gov.pl>
2007-02-09 17:03 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel Patrick McHardy
2007-02-09 17:30 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
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=457FC50E.70009@trash.net \
--to=kaber@trash.net \
--cc=lartc@mailman.ds9a.nl \
--cc=linux@arcoscom.com \
--cc=netfilter-devel@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