From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: Lost in iptables code.
Date: Thu, 22 Jul 2010 11:02:56 -0700 [thread overview]
Message-ID: <4C4887D0.3050309@candelatech.com> (raw)
I'm trying to debug an appearant bug in the "CT zones"
logic in 2.6.34, and I'm having a hard time figuring out where the
code enters the iptables logic. (In case it matters, the
CT Zones logic is related to the 'raw' table.)
I assume it would be somewhere in netif_receive_skb,
but I don't see anything obvious.
If anyone has suggestions where to start poking at this,
please let me know.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-07-22 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 18:02 Ben Greear [this message]
2010-07-22 18:37 ` Lost in iptables code Peter Chacko
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=4C4887D0.3050309@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.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.