All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Maik Hentsche <maik@mm-double.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: bugreport ipt_CLUSTERIP
Date: Sat, 29 Jul 2006 03:49:48 +0200	[thread overview]
Message-ID: <44CABEBC.9050101@trash.net> (raw)
In-Reply-To: <1154078751.44c9d81ff2c50@www.domainfactory-webmail.de>

Maik Hentsche wrote:
> Zitat von Patrick McHardy <kaber@trash.net>:
> 
>>What options did you use to trigger this?
> 
> 
> iptables -D INPUT -i eth1 -d 172.20.251.25  -j CLUSTERIP --new
> --hashmode sourceip-sourceport --clustermac 01:00:5e:12:34:56
> --total-nodes 2 --local-node 2
> 
> The first time, I tried this to delete the appropiate rule, it directly
> crashed. Unfortunatelly, I do not have the related Oops message, since
> I thought it might occur again and wanted to log via serial console.
> The second time, the already mentioned error occured, when I rebooted
> my machine and unfortunatelly after I had plugged the serial cable off
> :o(


I tried to reproduce this (by first adding your rule, then deleting it,
adding it again, rebooting), but got no crash. CLUSTERIP keeps global
state, so it might be that some previous actions using it contributed
to the crash, although its strange that it crashed in ip_tables, not
in CLUSTERIP itself. Did you added/deleted/flushed/... any CLUSTERIP
rules before the crashes? If you can find a way to reproducibly cause
the crash it would help a lot.

  reply	other threads:[~2006-07-29  1:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  6:26 bugreport ipt_CLUSTERIP Maik Hentsche
2006-07-27 14:19 ` Patrick McHardy
2006-07-28  9:25   ` Maik Hentsche
2006-07-29  1:49     ` Patrick McHardy [this message]
2006-08-02 18:12       ` Maik Hentsche
2006-08-03  9:48         ` Patrick McHardy
2006-08-03 13:59           ` Maik Hentsche

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=44CABEBC.9050101@trash.net \
    --to=kaber@trash.net \
    --cc=maik@mm-double.de \
    --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.