From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Sun, 11 Jan 2004 23:22:27 +0000 [thread overview]
Message-ID: <200401112322.27307.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <001701c3d898$70c170e0$1684188d@Kiste>
On Sunday 11 January 2004 11:12 pm, Thhoep wrote:
> ok, just solved my problem. was just a misunderstanding of mine. i thought
> "stable" means "proved and working". didn't know that i had to patch and
> bugfix stable kernels till they work in normal order.
Normally, you don't. However if you mix versions of the kernelspace system
and the userspace utilities, results are not guaranteed.
The general rule is that if you update one you should update the other to
match.
> found the necassary bugfixes for all my problems as a patch-o-matic on the
> netfilter main page.
>
> never the less thanks for helping.
Glad you've got things working okay now.
Antony.
--
Behind the counter a boy with a shaven head stared vacantly into space,
a dozen spikes of microsoft protruding from the socket behind his ear.
- William Gibson, Neuromancer (1984)
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-01-11 23:22 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 [this message]
2004-01-13 23:46 ` Thhoep
-- 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=200401112322.27307.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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.