From: "Thhoep" <thhoep@gmx.de>
To: netfilter@lists.netfilter.org
Subject: Re: Iproute2 and fwmark usage
Date: Sun, 11 Jan 2004 22:50:46 +0100 [thread overview]
Message-ID: <000a01c3d88c$f8d07d20$1684188d@Kiste> (raw)
In-Reply-To: 200401112107.09764.Antony@Soft-Solutions.co.uk
> What version of iptables is that? Is it as up to date as the netfilter
> version you've got in your shiny new kernel?
it is v1.2.6a
i'm not sure which kernels it accepts, theres written
"This version requires kernel >= 2.4.4
This version recommends kernel >= 2.4.18"
> This sounds a little bit dodgy to me....
everything's fine with my tunneling. thats the only thing i'm sure of. and
never the less the underlaying protocol of ppp is of no interest for the
routing/firewalling.
concerning the issue with MASQUERADE in my previous mail, maybe it has
something to do with the "MASQUERADE oops" written in the changelog of
kernel v2.4.24
as 2.4.24 was not working on my router (maybe because of the outdated
iptables, but wasnt in the mood for analysis) i just step back to 2.4.22
and retry with that. i think fresh versions of iptables and iproute2 cant
hurt either.
next prev parent reply other threads:[~2004-01-11 21:50 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 [this message]
2004-01-11 23:12 ` Thhoep
2004-01-11 23:22 ` Antony Stone
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='000a01c3d88c$f8d07d20$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.