From: "Andrew Hall" <temp02@bluereef.com.au>
To: <netfilter-devel@lists.netfilter.org>
Subject: RE: conntrack clarification
Date: Tue, 7 Aug 2007 18:08:01 +1000 [thread overview]
Message-ID: <4618641.2011186474076639.JavaMail.root@localhost> (raw)
In-Reply-To: <29656818.1521186459222779.JavaMail.root@localhost>
> I'm sorry if I'm missing something plainly obvious here, but the case
> in
> point doesn't make sense unless there is some locking function that
> reinserts the state back into the table BEFORE the flush has a chance
> to
> commit the removal.
>
Please disregard my last mail. I now realize that it is the return TCP
traffic that is keeping the conntrack populated.
Regards,
"Blue Reef disclaimer: This electronic message transmission contains information that is confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution, or use of the contents of this information is prohibited. If you have received this transmission in error, please notify us by telephone immediately."
Scanned by Sonar.
Date: 2007-08-07 18:07:56
From: temp02@bluereef.com.au
To: netfilter-devel@lists.netfilter.org
Mail id: challenge-64740762800
next parent reply other threads:[~2007-08-07 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29656818.1521186459222779.JavaMail.root@localhost>
2007-08-07 8:08 ` Andrew Hall [this message]
2007-08-07 9:42 ` conntrack clarification Pascal Hambourg
[not found] <3434740.221186389567173.JavaMail.root@localhost>
2007-08-06 8:54 ` Andrew Hall
2007-08-06 9:07 ` Jan Engelhardt
2007-08-06 10:27 ` Krzysztof Oledzki
[not found] ` <8883276.421186396148778.JavaMail.root@localhost>
2007-08-07 4:00 ` Andrew Hall
2007-08-06 12:37 ` Pascal Hambourg
2007-08-06 8:31 Andrew Hall
2007-08-06 8:38 ` Eric Leblond
-- strict thread matches above, loose matches on Subject: below --
2007-08-06 0:17 Conntrack clarification Andrew Hall
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=4618641.2011186474076639.JavaMail.root@localhost \
--to=temp02@bluereef.com.au \
--cc=netfilter-devel@lists.netfilter.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.