From: Wolfram Schlich <lists@wolfram.schlich.org>
To: netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] libnetfilter_conntrack 0.0.98 release
Date: Sun, 30 Nov 2008 11:03:14 +0100 [thread overview]
Message-ID: <20081130100314.GF9523@bla.fasel.org> (raw)
In-Reply-To: <20081130094646.GE9523@bla.fasel.org>
* Wolfram Schlich <lists@wolfram.schlich.org> [2008-11-30 10:47]:
> After upgrading to 0.0.98 and restarting conntrackd, I constantly
> get such messages on the backup firewall, even after restarting
> conntrackd on both firewalls once again:
>
> 2008-11-30 10:40:08 +01:00; hafw2; daemon.warning; conntrack-tools[29154]: Received seq=1228038103 before expected seq=1228039271
> 2008-11-30 10:40:09 +01:00; hafw2; daemon.warning; conntrack-tools[29154]: Received seq=1228038104 before expected seq=1228039271
> 2008-11-30 10:40:10 +01:00; hafw2; daemon.warning; conntrack-tools[29154]: Received seq=1228038105 before expected seq=1228039273
> 2008-11-30 10:40:11 +01:00; hafw2; daemon.warning; conntrack-tools[29154]: Received seq=1228038106 before expected seq=1228039274
>
> The numbers look kinda confusing to me.
>
> What's wrong? :)
Interesting... it went away after rebooting both machines at once.
--
Regards,
Wolfram Schlich <wschlich@gentoo.org>
Gentoo Linux * http://dev.gentoo.org/~wschlich/
next prev parent reply other threads:[~2008-11-30 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 12:49 [ANNOUNCE] libnetfilter_conntrack 0.0.98 release Pablo Neira Ayuso
2008-11-30 9:46 ` Wolfram Schlich
2008-11-30 10:03 ` Wolfram Schlich [this message]
2008-12-01 19:50 ` conntrackd reports message before expected seq [was Re: [ANNOUNCE] libnetfilter_conntrack 0.0.98 release] Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2008-12-14 21:52 [ANNOUNCE] libnetfilter_conntrack 0.0.98 release Pablo Neira Ayuso
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=20081130100314.GF9523@bla.fasel.org \
--to=lists@wolfram.schlich.org \
--cc=netfilter@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.