From: Tobias DiPasquale <codeslinger@gmail.com>
To: Max Kellermann <max@duempel.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: new REBOOT target
Date: Mon, 28 Feb 2005 21:39:40 -0500 [thread overview]
Message-ID: <876ef97a05022818395d69281c@mail.gmail.com> (raw)
In-Reply-To: <20050228090635.GA25632@roonstrasse.net>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
On Mon, 28 Feb 2005 10:06:35 +0100, Max Kellermann <max@duempel.org> wrote:
> On 2005/02/26 15:30, Wang Jian <lark@linux.net.cn> wrote:
> > # iptables -I INPUT -p icmp -j REBOOT --passphrase pass [--offset offset]
> > [--hard (0|1)]
>
> Ugly hack for an ugly problem ;) - still, it's an interesting idea for
> people plagued with such a problem.
I agree.
> You have implemented the "--passphrase" parameter in your REBOOT
> target, but that "--passphrase" is in fact a match, not a target
> parameter. Targets should not perform a test on the packet, it's not
> their task (it should not assume the packet is ICMP either, that drops
> a lot of flexibility). You should implement this part as a match
> module.
>
> Maybe someone has already written such a module.. look at
> patch-o-matic.
They have; its called ipt_string. Use that in conjunction with the
attached code to implement the functionality you require.
> In contrary, "--hard" is not a match, it controls what REBOOT should
> do in detail, so this is one ok.
Agreed; --hard stuck around for this.
--
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d
[-- Attachment #2: REBOOT.tgz --]
[-- Type: application/x-gzip, Size: 3233 bytes --]
next prev parent reply other threads:[~2005-03-01 2:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 14:30 new REBOOT target Wang Jian
2005-02-28 9:06 ` Max Kellermann
2005-02-28 9:41 ` Re[2]: " Wang Jian
2005-03-01 0:20 ` Max Kellermann
2005-03-01 5:14 ` Re[2]: " Wang Jian
2005-03-01 8:22 ` Andrew Kozachenko
2005-03-01 9:49 ` Re[2]: " Wang Jian
2005-03-01 2:39 ` Tobias DiPasquale [this message]
2005-03-01 5:10 ` Wang Jian
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=876ef97a05022818395d69281c@mail.gmail.com \
--to=codeslinger@gmail.com \
--cc=max@duempel.org \
--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.