Netdev List
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Pavel Simerda <psimerda@redhat.com>
Cc: netdev@vger.kernel.org, Dan Williams <danwilli@redhat.com>,
	danw@gnome.org
Subject: Re: Kernel doesn't propagate DNSSL to userspace (e.g. NetworkManager)
Date: Wed, 23 May 2012 09:24:25 -0500	[thread overview]
Message-ID: <1337783065.25721.1.camel@dcbw.foobar.com> (raw)
In-Reply-To: <fb24ca84-9976-42ab-b81a-73955b753731@zmail19.collab.prod.int.phx2.redhat.com>

On Wed, 2012-05-23 at 04:16 -0400, Pavel Simerda wrote:
> Hi,
> 
> I filed a bugreport to about lack of DNSSL support in kernel:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=824121
> 
> While NetworkManager recieves RDNSS neighbor discovery user option from kernel, it doesn't recieve DNSSL at all. This can be debugged with NetworkManager
> (or hopefully some better testing tool) and radvdump (to check if DNSSL is present).
> 
> radvdump reports DNSSL is there, NetworkManager gets no netlink message from kernel.
> 
> kernel-3.3.4-4.fc17.x86_64
> NetworkManager-0.9.4.0-7.git20120403.fc17.x86_64
> 
> Dave Jones asked me to contact this ML directly. I'm offlist.

So Pierre Ossman sent some RFC patches for DNSSL back in December 2010,
but Dave Miller wanted actual formal submissions which Pierre never got
around to doing.  I'll resubmit Pierre's second patch, which exports all
options the kernel doesn't care about to userspace.

Sun, 12 Dec 2010:
"[RFC][PATCH] Export all RA options that we don't handle to userspace"

Dan

  reply	other threads:[~2012-05-23 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0263d6e6-50ba-4101-b958-260e2948c4ab@zmail19.collab.prod.int.phx2.redhat.com>
2012-05-23  8:16 ` Kernel doesn't propagate DNSSL to userspace (e.g. NetworkManager) Pavel Simerda
2012-05-23 14:24   ` Dan Williams [this message]
2012-05-23 14:46     ` Dan Williams

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=1337783065.25721.1.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=danw@gnome.org \
    --cc=danwilli@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=psimerda@redhat.com \
    /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