From: Rusty Russell <rusty@linuxcare.com.au>
To: "Christian W. Zuckschwerdt" <zany@triq.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipchains log will show all flags
Date: Wed, 06 Dec 2000 00:55:09 +1100 [thread overview]
Message-ID: <20001205135519.9747C813F@halfway.linuxcare.com.au> (raw)
In-Reply-To: Your message of "Tue, 05 Dec 2000 14:22:00 BST." <0012051408110.1526-100000@localhost>
In message <0012051408110.1526-100000@localhost> you write:
> Hi Linus,
>
> This tiny patch extends ipchains logging. This way one can distinguish
> (plain) connection attempts and (Xmas, Fin,...) scans. E.g.
> kernel: Packet log: input - lo PROTO=6 127.0.0.1:40326 127.0.0.1:80
> L=40 S=0x00 I=5808 F=0x0000 T=51 (#1)
> vs.
> L=40 S=0x00 I=5808 F=0x0000 T=51 (#1) B=-s--a-
> and
> L=40 S=0x00 I=5808 F=0x0000 T=51 (#1) B=fs-p-u
>
> Please comment on the format (B=...) and implementation details (speed).
> The patch is against 2.2.17's /net/ipv4/ip_fw.c
Looks OK, but CC'ing the maintainer is simple politeness.
> + if (ip->protocol == IPPROTO_TCP)
You probably want to insert `&& !(ip->frag_off & htons(IP_OFFSET))'
> + tcp-syn ? 's' : '-', tcp->rst ? 'r' : '-',
You mean `tcp->syn' not `tcp-syn'.
I like the fact that it doesn't disturb the format, simply appends,
and it has been a not-uncommon request.
But application is up to Alan Cox, who ruleth the 2.2 series.
Rusty.
--
Hacking time.
-
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/
next prev parent reply other threads:[~2000-12-05 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 13:22 Christian W. Zuckschwerdt
2000-12-05 13:55 ` Rusty Russell [this message]
2000-12-05 16:00 ` Mike A. Harris
2000-12-06 0:40 ` Rusty Russell
2000-12-06 7:29 ` Mike A. Harris
2000-12-05 14:44 Tony Gale
2000-12-11 14:52 Christian W. Zuckschwerdt
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=20001205135519.9747C813F@halfway.linuxcare.com.au \
--to=rusty@linuxcare.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=zany@triq.net \
/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®