From: Andi Kleen <ak@suse.de>
To: Peter Bieringer <pb@bieringer.de>
Cc: Maillist netdev <netdev@oss.sgi.com>
Subject: Re: Debug kernel network hook chain or why has Check Point Firewall module problems with IPv6
Date: Mon, 22 Apr 2002 09:22:52 +0200 [thread overview]
Message-ID: <20020422092252.A17861@wotan.suse.de> (raw)
In-Reply-To: <22830000.1019458033@localhost>
On Mon, Apr 22, 2002 at 08:47:13AM +0200, Peter Bieringer wrote:
> Looks like CP never sees (or recognizes) packets leaving the
> firewalled host from a dual-stack application.
Linux has no "generic" firewall hooks, only protocol specific ones.
Checkpoint is probably using the v4 specific ones only.
Other protocols can be received (by registering a protocol to ETH_P_ALL via
SOCK_PACKET or in the kernel), but not stolen from protocol handlers.
2.2 had no working firewall chains for IPv6, 2.4 has a v6 netfilter
interface.
BTW the CheckPoint module seems to leak routes too at least on 2.2,
there are regular reports of that.
> BTW: incoming SSH traffic via IPv6 is completly unrecognized and
> therefore quietly accepted. Looks like CP never sees or recognize
> incoming IPv6 packets at all - same issue, if on a IPv4-netfiltererd
> box the IPv6-netfilter was forgotten...
Sounds like a serious CheckPoint bug.
-Andi
next prev parent reply other threads:[~2002-04-22 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 6:47 Debug kernel network hook chain or why has Check Point Firewall module problems with IPv6 Peter Bieringer
2002-04-22 7:22 ` Andi Kleen [this message]
2002-04-22 8:53 ` Peter Bieringer
2002-04-22 10:06 ` Andi Kleen
2002-04-22 12:47 ` Peter Bieringer
2002-04-22 12:54 ` Andi Kleen
2002-04-22 13:05 ` Peter Bieringer
2002-04-22 13:08 ` Andi Kleen
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=20020422092252.A17861@wotan.suse.de \
--to=ak@suse.de \
--cc=netdev@oss.sgi.com \
--cc=pb@bieringer.de \
/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).