All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Ssagarr Patil <hugarsagar@outlook.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: ip -details link fails
Date: Thu, 28 May 2015 17:42:18 +0200	[thread overview]
Message-ID: <5567375A.404@hartkopp.net> (raw)
In-Reply-To: <BAY176-W52B59690F5605C23AA3A3D3CA0@phx.gbl>



On 28.05.2015 11:48, Ssagarr Patil wrote:
> Hi Oliver,
>
>>
>> On 05/27/2015 07:24 PM, Oliver Hartkopp wrote:
>>>> # ip -details link show wlan0
>>>> RTNETLINK answers: Invalid argument
>>>> Cannot send link get request: Invalid argument
>>>
>>> The fact that your 'ip' tool doesn't work with wlan0 too your problem is
>>> probably not CAN related.
>>
>> BTW: the busybox version of ip doesn't talk can.
>>
> I am not using the ip from the busybox,
> I am using the release version from [1] (# ip -V
> ip utility, iproute2-ss150413)
>

Looks good.

>
> # ip -details link show can0
> RTNETLINK answers: Invalid argument
> Cannot send link get request: Invalid argument
> #
>


>
> [1] https://www.kernel.org/pub/linux/utils/net/iproute2/
>
> Or is that I am missing something in the kernel defconfig do I need to enable some via
> doing menuconfig to get it working

Hm.

Can you post the output of

	strace ip -details link show can0

Maybe there"s really something missing in the kernel config to run the netlink 
configuration.

Regards,
Oliver


  reply	other threads:[~2015-05-28 15:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 16:38 ip -details link fails Ssagarr Patil
2015-05-27 17:06 ` Oliver Hartkopp
2015-05-27 17:11   ` Ssagarr Patil
2015-05-27 17:24     ` Oliver Hartkopp
2015-05-27 19:16       ` Marc Kleine-Budde
2015-05-28  9:48         ` Ssagarr Patil
2015-05-28 15:42           ` Oliver Hartkopp [this message]
2015-05-28 16:28             ` Ssagarr Patil
2015-05-28 17:19               ` Oliver Hartkopp
2015-05-28  0:46 ` Tom Evans

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=5567375A.404@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=hugarsagar@outlook.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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.