From: "David S. Miller" <davem@redhat.com>
To: solt@dns.toxicfilms.tv
Cc: laforge@gnumonks.org, netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] netfilter unclean match extension
Date: Wed, 23 Oct 2002 04:25:04 -0700 (PDT) [thread overview]
Message-ID: <20021023.042504.24890238.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210231323200.20094-100000@dns.toxicfilms.tv>
From: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Date: Wed, 23 Oct 2002 13:26:05 +0200 (CEST)
> Just to be clear, if a future RFC or ietf working draft defines
> meaning for this field, will we remove this new test from the
> unclean module?
Then, we should update the match to remove the test as it may render some
routers inoperational for some data streams, vide the ECN issue.
I read rfc 791 and 793 some more.
The difference here is that for the ECN bits it says
"reserved for future use", whereas for this one flag bit
it says just "reserved".
Ok, I'm convinced :-)
prev parent reply other threads:[~2002-10-23 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 14:40 [PATCH] netfilter unclean match extension Harald Welte
2002-10-22 21:57 ` David S. Miller
2002-10-23 11:03 ` David S. Miller
2002-10-23 11:22 ` Harald Welte
2002-10-23 11:21 ` David S. Miller
2002-10-23 11:26 ` Maciej Soltysiak
2002-10-23 11:25 ` David S. Miller [this message]
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=20021023.042504.24890238.davem@redhat.com \
--to=davem@redhat.com \
--cc=laforge@gnumonks.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=solt@dns.toxicfilms.tv \
/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.