From: Patrick McHardy <kaber@trash.net>
To: Cody Tubbs <tubbs@wispdirect.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipv4options still broken (posted prev w/ no reply)...
Date: Thu, 01 Jun 2006 05:25:41 +0200 [thread overview]
Message-ID: <447E5E35.1090304@trash.net> (raw)
In-Reply-To: <1149102130.6167.20.camel@mbox>
Cody Tubbs wrote:
> Bottom line is, it would be nice to -j LOG these options passing through
> or attempting to be passed through a bridged firewall. It details
> malicious activity, thus deterring that fact into a presumption that "I
> most likely have more serious problems" was blatantly absurd.
As I already said, please just send me your patch to disable or even
better fix this behaviour and I'm going to apply it. If you really want
to do something useful, please just fix the ipv4options match to be
acceptable for kernel inclusion. So far, it does stupid things like
using seperate flags for option negation and it depends on IP option
metadata provided by the IP layer, which doesn't work for bridging.
The last point BTW really is a good example why random crap from POM
shouldn't be trusted.
next prev parent reply other threads:[~2006-06-01 3:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1149033568.27117@www.broadwayinternet.com>
2006-05-30 23:46 ` ipv4options still broken (posted prev w/ no reply) Patrick McHardy
2006-05-31 4:54 ` Patrick Schaaf
2006-05-31 13:55 ` Patrick McHardy
2006-05-31 17:45 ` Cody Tubbs
2006-05-31 18:39 ` Patrick McHardy
2006-05-31 19:02 ` Cody Tubbs
2006-06-01 3:25 ` Patrick McHardy [this message]
2006-05-30 17:47 Cody Tubbs
2006-05-30 19:22 ` Patrick McHardy
2006-05-30 21:16 ` Cody Tubbs
2006-05-30 23:05 ` Patrick McHardy
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=447E5E35.1090304@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=tubbs@wispdirect.com \
/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.