From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: netdev@oss.sgi.com, laforge@gnumonks.org
Subject: Re: [2.6 PATCH] ipchains masquerade must select maddr correctly
Date: Tue, 2 Dec 2003 16:22:08 -0800 [thread overview]
Message-ID: <20031202162208.04629dab.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312030150080.1237-200000@u.domain.uli>
On Wed, 3 Dec 2003 01:55:28 +0200 (EET)
Julian Anastasov <ja@ssi.bg> wrote:
> The attached patch fixes ipchains masquerade to use
> correctly the routing. This bug-to-bug compatibility with 2.2
> is not valid from long time. Also, a missing unlock is added.
Slow down.
I don't think it's always desirable to specify a specific TOS when
we're working with an input packet. In fact, what you're doing all
over the tree is going to cause the routing cache size to explode in
some very real usage.
next prev parent reply other threads:[~2003-12-03 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 23:55 [2.6 PATCH] ipchains masquerade must select maddr correctly Julian Anastasov
2003-12-03 0:22 ` David S. Miller [this message]
2003-12-03 0:50 ` Julian Anastasov
2003-12-03 0:58 ` David S. Miller
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=20031202162208.04629dab.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=laforge@gnumonks.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).