From: jamal <hadi@cyberus.ca>
To: Erik Hensema <erik@hensema.net>
Cc: Harald Welte <laforge@netfilter.org>, "" <netdev@oss.sgi.com>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: RFC: promote netfilter MARK value from IPv6 packets to sit packets
Date: Mon, 24 Feb 2003 08:41:10 -0500 (EST) [thread overview]
Message-ID: <20030224083946.H34066@shell.cyberus.ca> (raw)
In-Reply-To: <20030223234225.GA23556@hensema.net>
If this is to be a config option, it should not be restricted to
netfilter specifics but rather skb specifics. Example the tcindex
(maybe even the cb) etc.
cheers,
jamal
next prev parent reply other threads:[~2003-02-24 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 14:57 RFC: promote netfilter MARK value from IPv6 packets to sit packets Erik Hensema
2003-02-23 19:33 ` Harald Welte
2003-02-23 23:42 ` Erik Hensema
2003-02-24 13:41 ` jamal [this message]
2003-02-24 14:41 ` Harald Welte
2003-02-25 2:30 ` jamal
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=20030224083946.H34066@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=erik@hensema.net \
--cc=laforge@netfilter.org \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).