All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Problem accessing https://my.procurve.com/profile/index.aspx (ACK is over the upper bound)
Date: Mon, 02 Jul 2007 20:20:06 +0200	[thread overview]
Message-ID: <468941D6.7090306@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707022005200.25153@bizon.gios.gov.pl>

Krzysztof Oledzki wrote:
> On Mon, 2 Jul 2007, Patrick McHardy wrote:
> 
>> We should really document that with window tracking and NAT you
>> must drop INVALID packets to avoid them getting delivered locally
>> and causing a RST.
> 
> 
> Indeed. There should be a big, fat warning about dropping in INPUT (and
> probably FORWARD). The question is where: Kconfig (NAT)? man iptables?
> both? ;)


The manpage I guess. Kconfig is not really the place for this IMO.

>>> make no more RSTs, only retransmisions from the 216.34.143.7. And yes, I
>>> have a patched kernel so I'm able to filter packets in a PREROUTING
>>> chain.
>>
>>
>> Dropping works without any patches.
> 
> 
> Yes, in INPUT. I discovered that such packets goes to INPUT shortly
> after I had written this mail. Before that I had put this in PREROUTING,
> which is not possible by default.


You can drop in PREROUTING/mangle for example. In the filter table
its not possible of course since there is no PREROUTING chain :)

  reply	other threads:[~2007-07-02 18:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01  0:42 Problem accessing https://my.procurve.com/profile/index.aspx (ACK is over the upper bound) Krzysztof Oledzki
2007-07-01  1:04 ` Krzysztof Oledzki
2007-07-01  1:09   ` Krzysztof Oledzki
2007-07-01  3:01   ` Krzysztof Oledzki
2007-07-01 13:51     ` Jan Engelhardt
2007-07-01 15:03       ` Krzysztof Oledzki
2007-07-01 15:49         ` Jan Engelhardt
2007-07-02 13:26     ` Patrick McHardy
2007-07-02 18:55       ` Krzysztof Oledzki
2007-07-02 18:57         ` Patrick McHardy
2007-07-02 13:23   ` Patrick McHardy
2007-07-02 13:42     ` Jozsef Kadlecsik
2007-07-02 14:14       ` Patrick McHardy
2007-07-02 14:40         ` Jozsef Kadlecsik
2007-07-02 14:46           ` Patrick McHardy
2007-07-02 14:58             ` Jozsef Kadlecsik
2007-07-02 19:06         ` Krzysztof Oledzki
2007-07-03 11:06           ` Patrick McHardy
2007-07-02 18:17     ` Krzysztof Oledzki
2007-07-02 18:20       ` Patrick McHardy [this message]
2007-07-02 19:11         ` Krzysztof Oledzki
2007-07-03 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=468941D6.7090306@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=ole@ans.pl \
    /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.