mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony Gale <gale@syntax.dera.gov.uk>
To: Jussi Hamalainen <count@theblah.org>
Cc: linux-kernel@vger.kernel.org
Subject: IP defrag (was RE: ipchains blocking port 65535)
Date: Wed, 17 Jan 2001 17:15:54 -0000 (GMT)	[thread overview]
Message-ID: <XFMail.20010117171554.gale@syntax.dera.gov.uk> (raw)
In-Reply-To: <Pine.LNX.4.30.0101171911010.21865-100000@shodan.irccrew.org>


On 17-Jan-2001 Jussi Hamalainen wrote:
> On Wed, 17 Jan 2001, Tony Gale wrote:
> 
>> It looks like this is due to the odd way in which ipchains handles
>> fragments. Try:
>>
>> echo 1 > /proc/sys/net/ipv4/ip_always_defrag
> 
> Thanks, this seems to do the trick. Does this oddity still exist
> in 2.4?
> 

Well, I haven't found it, but there is
/proc/sys/net/ipv4/ipfrag_high_thresh
/proc/sys/net/ipv4/ipfrag_low_thresh
/proc/sys/net/ipv4/ipfrag_time

Perhaps 2.4 always defrags packets by default. Anyone confirm? This
is pretty much needed for any kind of firewall/masquerading system.

-tony



---
E-Mail: Tony Gale <gale@syntax.dera.gov.uk>
The great merit of society is to make one appreciate solitude.
		-- Charles Chincholles, "Reflections on the Art of Life"

The views expressed above are entirely those of the writer
and do not represent the views, policy or understanding of
any other person or official body.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-17 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 13:40 ipchains blocking port 65535 Jussi Hamalainen
2001-01-17 14:50 ` Tony Gale
2001-01-17 17:12   ` Jussi Hamalainen
2001-01-17 17:15     ` Tony Gale [this message]
2001-01-17 17:35       ` IP defrag (was RE: ipchains blocking port 65535) Andi Kleen
2001-01-17 17:44         ` Tony Gale
2001-01-17 18:01           ` Andi Kleen

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=XFMail.20010117171554.gale@syntax.dera.gov.uk \
    --to=gale@syntax.dera.gov.uk \
    --cc=count@theblah.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®