From: "David S. Miller" <davem@redhat.com>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4] fix ipt_REJECT when used in OUTPUT
Date: Sun, 21 Sep 2003 18:16:11 -0700 [thread overview]
Message-ID: <20030921181611.4e48af79.davem@redhat.com> (raw)
In-Reply-To: <20030921144013.GA22223@sunbeam.de.gnumonks.org>
On Sun, 21 Sep 2003 16:40:13 +0200
Harald Welte <laforge@netfilter.org> wrote:
> Some people use REJECT in the OUTPUT chain (rejecting locally generated
> packets). This didn't work anymore starting with some fixes we did in 2.4.22.
> A dst_entry for a local source doesn't contain pmtu information - and
> thus the newly-created packet would instantly be dropped again.
Applied to 2.4.x, thanks Harald.
next prev parent reply other threads:[~2003-09-22 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 14:40 [PATCH 2.4] fix ipt_REJECT when used in OUTPUT Harald Welte
2003-09-22 1:16 ` David S. Miller [this message]
2003-09-22 8:16 ` Diadon
2003-09-22 8:53 ` Harald Welte
2003-09-22 9:02 ` David S. Miller
2003-09-22 11:13 ` Diadon
2003-09-22 12:21 ` Harald Welte
2003-09-23 19:43 ` David S. Miller
2003-09-22 11:08 ` Patrick McHardy
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=20030921181611.4e48af79.davem@redhat.com \
--to=davem@redhat.com \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox