From: Jiri Pirko <jiri@resnulli.us>
To: Alexander Aring <alex.aring@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: ifconfig doesn't show assignment ip-addresses
Date: Tue, 10 Dec 2013 13:57:54 +0100 [thread overview]
Message-ID: <20131210125754.GC2469@minipsycho.orion> (raw)
In-Reply-To: <20131210114847.GA20146@omega>
Tue, Dec 10, 2013 at 12:48:48PM CET, alex.aring@gmail.com wrote:
>On Tue, Dec 10, 2013 at 12:43:39PM +0100, Jiri Pirko wrote:
>> Tue, Dec 10, 2013 at 12:06:49PM CET, alex.aring@gmail.com wrote:
>> >Hi,
>> >
>> >thanks for your reply.
>> >
>> >On Tue, Dec 10, 2013 at 11:57:41AM +0100, Jiri Pirko wrote:
>> >> Mon, Dec 09, 2013 at 04:32:39PM CET, alex.aring@gmail.com wrote:
>> >> >Hi,
>> >> >
>> >> >On current net-next with a lowpan interface created with:
>> >> >
>> >> >ip link add link wpan0 name lowpan0 type lowpan
>> >> >
>> >> >I don't see any ipv6 addresses in ifconfig anymore. The addresses exist,
>> >> >because I can ping my device.
>> >>
>> >>
>> >> Can you see the address in "ip a" ? Would you send me output of
>> >> "ifconfig" and "ip a" please? Is this a problem for lowpan only or do
>> >> you see this with other device types as well?
>> >>
>>
>> The problem is that ifconfig parses /proc/net/if_inet6 which changed
>> flag format from 2 hexa chars to 3.
>> I will send revert for this change in couple of minutes.
>>
>
>ah, nice to known. Thanks!
>
>What would be a proper solution to add a u32 flag property? Or we never
>should change this, because we want backwards compatibility?
I think that we should leave this as it is. The u32 flags are reachable
via Netlink and that is the preferred way nowadays.
>
>- Alex
next prev parent reply other threads:[~2013-12-10 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 15:32 ifconfig doesn't show assignment ip-addresses Alexander Aring
2013-12-10 10:57 ` Jiri Pirko
2013-12-10 11:06 ` Alexander Aring
2013-12-10 11:43 ` Jiri Pirko
2013-12-10 11:48 ` Alexander Aring
2013-12-10 12:57 ` Jiri Pirko [this message]
2013-12-10 11:52 ` Florent Fourcot
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=20131210125754.GC2469@minipsycho.orion \
--to=jiri@resnulli.us \
--cc=alex.aring@gmail.com \
--cc=netdev@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).