From: Patrick McHardy <kaber@trash.net>
To: Nishit Shah <nishit@elitecore.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Accessing conntrack memory on multicore machine
Date: Fri, 29 Feb 2008 13:17:25 +0100 [thread overview]
Message-ID: <47C7F7D5.4040001@trash.net> (raw)
In-Reply-To: <005001c87abf$d328d570$797a8050$@com>
Nishit Shah wrote:
> Now,
> I am using CONNMARK target to do mark on conntrack. Here
> packets with direction IP_CT_DIR_ORIGINAL are marked with 1 and packets with
> direction IP_CT_DIR_REPLY are marked with 2. Now as eth0 and eth1 are served
> by different CPUs, is there chances of –m connmark will get wrong values of
> conntrack mark ?
Yes, you should mark the packet and not the connection since
the direction is a property of the packet.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-02-29 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 10:42 Accessing conntrack memory on multicore machine Nishit Shah
2008-02-29 12:17 ` Patrick McHardy [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=47C7F7D5.4040001@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=nishit@elitecore.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.