All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Leon Bene <leon@benesconsulting.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Looking for IPtables developers - Need help at core of iptables (not configuration)
Date: Sun, 1 Aug 2004 18:59:29 +0200	[thread overview]
Message-ID: <20040801165929.GB14539@sunbeam2> (raw)
In-Reply-To: <5.2.0.9.2.20040727115216.00aa0a30@pop.benesconsulting.com>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

On Tue, Jul 27, 2004 at 11:59:38AM -0700, Leon Bene wrote:
> I am using iptables in Redhats' release (ES) of Linux. In version 7.1 of 
> Redhat (iptables 1.2.1a) it forwarded packets just fine. Now with iptables 
> 1.2.8 the outbound traffic hangs for about 5 seconds on rapid small packet 
> transmissions.

iptables-1.2.1a/1.2.8 are the userspace programs only, they never see or
touch a single packet - all happens in the kernel.

Please describe more detailed what particular problem you seem to be
encountering.

-- 
- 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 --]

  reply	other threads:[~2004-08-01 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 18:59 Looking for IPtables developers - Need help at core of iptables (not configuration) Leon Bene
2004-08-01 16:59 ` Harald Welte [this message]
     [not found] ` <5.2.0.9.2.20040802161432.00aac218@pop.benesconsulting.com>
2004-08-03 14:45   ` Harald Welte
2004-08-03 17:37     ` Chris Brenton

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=20040801165929.GB14539@sunbeam2 \
    --to=laforge@netfilter.org \
    --cc=leon@benesconsulting.com \
    --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 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.