From: Bart De Schuymer <bdschuym@pandora.be>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com, snort2004@mail.ru
Subject: Re: [PATCH][BRIDGE-NF] Fix wrong use of skb->protocol
Date: Fri, 31 Dec 2004 11:51:00 +0100 [thread overview]
Message-ID: <1104490260.3373.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20041231083352.GA25031@xi.wantstofly.org>
Op vr, 31-12-2004 te 09:33 +0100, schreef Lennert Buytenhek:
> Just one more thing: AFAIK it is possible to inject a raw IPv4 packet
> with an invalid IPv4 header. So maybe the better 'fix' would be to have
> different hooks for PF_INET and PF_INET6, and distinguish v4/v6 packets
> that way instead of peeking into the header. (The hook you're talking
> about is a PF_INET* and not a PF_BRIDGE hook, right?)
That was my original plan, but it seems such a waste.
Wouldn't injecting such an invalid IPv4 header also screw up iptables?
Is there any reason why someone should be allowed to do this?
I checked ip_tables.c::ipt_do_table() before using the IP version, and
it looks at the IP header too without any precautions AFAICT.
> Then again, that would add yet another function onto the already rather
> deep call chains that we have in there.
The netfilter scheme itself implies call chains.
> Too bad I don't see any cleaner way of integrating the whole bridging
> thing into the stack. I wonder if any of the *BSDs found a cleaner way
> of doing this.
How about adding something like NF_STOP, which acts like NF_STOLEN but
still executes okfn in nf_hook_slow()?
cheers,
Bart
prev parent reply other threads:[~2004-12-31 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 18:55 [PATCH][BRIDGE-NF] Fix wrong use of skb->protocol Bart De Schuymer
2004-12-30 22:24 ` Lennert Buytenhek
2004-12-30 23:10 ` Bart De Schuymer
2004-12-31 0:33 ` Patrick McHardy
2004-12-31 8:33 ` Lennert Buytenhek
2004-12-31 10:51 ` Bart De Schuymer [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=1104490260.3373.15.camel@localhost.localdomain \
--to=bdschuym@pandora.be \
--cc=buytenh@wantstofly.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=snort2004@mail.ru \
/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).