From: "Thhoep" <thhoep@gmx.de>
To: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Wed, 14 Jan 2004 00:46:37 +0100 [thread overview]
Message-ID: <000e01c3da2f$7cc83700$1684188d@Kiste> (raw)
In-Reply-To: 001701c3d898$70c170e0$1684188d@Kiste
> ok, just solved my problem.
sorry, i was mistaking. i found some bugfixes, thats right, but they didnt
fix this bug BUT brought several other bugs into my kernel.
i still have the problem that usage of firewall marks as routing key doesnt
work.
kernel: 2.4.20-22 (all tried)
iptables: 1.2.9
iproute: ss010824
in addition with kernels 2.4.23 and 2.4.24 routing table selection doesnt
seem to work at all for me.
if you have ANY hints, i would be really grateful. maybe you can name me a
configuration of kernel, kernelpatches, iptables and iproute with which
advanced routing, firewalling and QoS are working fine. to be more precise,
i need a full functional netfilter with the usual matching rules and
targets, esp. marks and masquerading, advanced routing that allows routing
selection upon netfilter marks and qos with the htb queueing disciplin.
thank you.
next prev parent reply other threads:[~2004-01-13 23:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 23:05 Iproute2 and fwmark usage Thhoep
2004-01-09 16:47 ` Ramin Dousti
2004-01-09 16:17 ` Thhoep
2004-01-09 17:35 ` Ramin Dousti
2004-01-09 16:50 ` Thhoep
2004-01-09 19:42 ` Ramin Dousti
2004-01-09 19:06 ` Thhoep
2004-01-09 20:47 ` Ramin Dousti
2004-01-09 20:09 ` Thhoep
2004-01-09 21:22 ` Ramin Dousti
2004-01-09 21:30 ` Thhoep
2004-01-09 22:02 ` Thhoep
2004-01-11 20:57 ` Thhoep
2004-01-11 21:07 ` Antony Stone
2004-01-11 21:50 ` Thhoep
2004-01-11 23:12 ` Thhoep
2004-01-11 23:22 ` Antony Stone
2004-01-13 23:46 ` Thhoep [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 14:20 Filter out broadcast messages Gabby James
2004-01-08 14:31 ` iproute2 and fwmark usage Thhoep
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='000e01c3da2f$7cc83700$1684188d@Kiste' \
--to=thhoep@gmx.de \
--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 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.