From: Harald Welte <laforge@netfilter.org>
To: Thhoep <thhoep@gmx.de>
Cc: netfilter@lists.netfilter.org, netdev@oss.sgi.com,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: Problem using fwmarks as routing key: "MASQUERADE: Route sent us somewhere else."
Date: Tue, 27 Jan 2004 02:51:52 +0100 [thread overview]
Message-ID: <20040127015152.GP19250@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <001c01c3e043$93583cd0$1684188d@Kiste>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On Wed, Jan 21, 2004 at 06:25:22PM +0100, Thhoep wrote:
> hi,
>
> my aim: to divide 100 hosts upon 6 masqueraded adsl connections to the
> internet using a linux router runnig a debian woody.
>
> the problem: really strange behaviour of the routing/masquerading combo,
> that changes with every tried kernel version. (described below)
>
> presumption: some version mismatch or a bug in the kernel routing code,
> which needs a bugfix that till now is unknown to me
Please read the recent archives of the netdev list with regard to
"Rusty's brain broke". Also see
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=144
Alexey heavily argued against us reverting that change, however :(
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-27 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 17:25 Problem using fwmarks as routing key: "MASQUERADE: Route sent us somewhere else." Thhoep
2004-01-23 16:06 ` Ramin Dousti
2004-01-23 19:13 ` Rodrigo Severo
2004-01-27 1:51 ` Harald Welte [this message]
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=20040127015152.GP19250@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=thhoep@gmx.de \
/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.