public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat•com>
To: David Laight <David.Laight@ACULAB•COM>
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: Does NetworkManager kill IPv6 connections?
Date: Fri, 05 Sep 2014 13:42:25 -0500	[thread overview]
Message-ID: <1409942545.15943.10.camel@dcbw.local> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1748838C@AcuExch.aculab.com>

On Fri, 2014-09-05 at 14:18 +0000, David Laight wrote:
> From: Dan Williams 
> > On Thu, 2014-09-04 at 14:47 +0000, David Laight wrote:
> > > I was running a overnight test that failed because an (almost idle) IPv6 connection
> > > unexpectedly disconnected.
> > > 30 seconds before the disconnect syslog contains (retyped):
> > >   NetworkManager[pid]: <info> policy set 'Wired connection 2' (eth0) as default for IPv6 routing and DNS.
> > > The same message appeared exactly 70 minutes earlier - with no ill effect.
> > > A second connection between the same pair if addresses (carrying a lot of traffic)
> > > was unaffected.
> > >
> > > Any idea what/why NetworkManager is doing?
> > > (Yes I know it is userspace, but it seems to be breaking the kernel....)
> > >
> > > The system is an ubuntu 13.04 desktop (3.8.0-19 kernel), that recent, but
> > > newer than the ones a lot of our customers use.
> > 
> > Is the version of the Ubuntu "network-manager" package on your systems
> > 0.9.8.0-0ubuntu6.1?
> 
> It is actually the slightly older 0.9.8.0-0ubuntu6.0
> 
> > If so, I know we've fixed a ton of issues with IPv6 since 0.9.8.0 (which
> > was released about 18 months ago), and the ones that may be affecting
> > you are related to router advertisement timing and expiry.  The latest
> > stable NM version upstream is 0.9.10 and should contain all of those
> > fixes.
> 
> I've flagged it with our management, they'll decide what to say
> about IPv6 support in various Linux distros.

Ok, keep me (and the NM upstream) in the loop depending on what gets
decided.  Like I said, subsequent stable versions of NetworkManager in
recent distros have much improved IPv6 support, and if you have a chance
to try it out and let me know how it goes, that would be awesome.

Dan

> 	David
> 
> > Since I'm pretty sure this isn't a kernel problem, would you mind
> > discussing this over on the NM lists here:
> > 
> > https://mail.gnome.org/mailman/listinfo/networkmanager-list
> > 
> > If you don't want to subscribe that's fine, I'll moderate your message
> > through and we can just use "reply all".
> > 
> > Thanks,
> > Dan
> > 
> > > I can rerun the test, but don't know what to look for.
> > > 'eth0' is the only ethernet interface in the system that is actually
> > > connected to a network.
> > >
> > > Some indications of where to look would be appreciated.
> > >
> > > 	David
> > >
> > >
> > >
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe netdev" in
> > > the body of a message to majordomo@vger•kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 

      reply	other threads:[~2014-09-05 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 14:47 Does NetworkManager kill IPv6 connections? David Laight
2014-09-04 17:43 ` Daniel Borkmann
2014-09-04 18:17 ` Dan Williams
2014-09-05 14:18   ` David Laight
2014-09-05 18:42     ` Dan Williams [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=1409942545.15943.10.camel@dcbw.local \
    --to=dcbw@redhat$(echo .)com \
    --cc=David.Laight@ACULAB$(echo .)COM \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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