linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
To: linux-admin@vger.kernel.org
Subject: broken multicast in 3.12.6 (and probably 3.12.5)
Date: Tue, 31 Dec 2013 08:21:19 +0700	[thread overview]
Message-ID: <2485244.Sk40P3p13K@note> (raw)

Hi, list!

I've updated my virtual network (in Xen) to 3.12.6 few days ago and start 
encountering strange behaviour: random machins lose access via IPv6 ULA 
addresses to random others, until the moment, while losed machine itself 
pinged machine that search for it. IPv4 and link-local addresses worked okay.

I've downgraded all of them to 3.12.5 and all going to work properly until 
tonight: two machines mutually losed each other (even mutual ping doesn't 
help) until I rebooted both of them.

So,
1) I guess it can be some bug in 3.12 or hardened patches for it
2) Doesn't enybody else experienced same behaviour?

-- 
Best regsrds,
mva

                 reply	other threads:[~2013-12-31  1:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2485244.Sk40P3p13K@note \
    --to=mva@mva.name \
    --cc=linux-admin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).