Skip to contentSkip to conversation

ifconfig doesn't show assignment ip-addresses

DISCUSSION Alexander Aring 3 participants 7 messages Dec 9, 2013 – Dec 10, 2013

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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.

I bisect this issue on commit:
479840ffdbe4242e8a25349218c8e0859223aa35

Does anybody know what's going up there?

- Alex

#1 lore raw
Quoted 8 lines · Mon, Dec 09, 2013 at 04:32:39PM CET, [email protected] 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?

Quoted 7 lines

I bisect this issue on commit:
479840ffdbe4242e8a25349218c8e0859223aa35

Does anybody know what's going up there?

- Alex

#2 lore raw

Hi,

thanks for your reply.

Quoted 7 lines · Jiri Pirko
Quoted 6 lines · Mon, Dec 09, 2013 at 04:32:39PM CET, [email protected] wrote:

Hi,

On current net-next with a lowpan interface created with:

ip link add link wpan0 name lowpan0 type lowpan

Quoted 8 lines
Quoted 2 lines

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?

Yes I can see the address in "ip a".

Output of "ip a":

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
    inet6 2001::2/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 2001::3/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fe12:3456/64 scope link 
       valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop 
    link/sit 0.0.0.0 brd 0.0.0.0
4: wpan0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 127 qdisc pfifo_fast qlen 300
    link/[804] aa:aa:aa:aa:aa:aa:aa:aa brd ff:ff:ff:ff:ff:ff:ff:ff
5: lowpan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1281 qdisc noqueue 
    link/[804] aa:aa:aa:aa:aa:aa:aa:aa brd ff:ff:ff:ff:ff:ff:ff:ff
    inet6 2001::1/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link 
       valid_lft forever preferred_lft forever
    inet6 fe80::a8aa:aaaa:aaaa:aaaa/64 scope link 
       valid_lft forever preferred_lft forever

Output of "ifconfig":

eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1144 (1.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lowpan0 Link encap:UNSPEC HWaddr AA-AA-AA-AA-AA-AA-AA-AA-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1281 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wpan0 Link encap:UNSPEC HWaddr AA-AA-AA-AA-AA-AA-AA-AA-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING NOARP MTU:127 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:300
RX bytes:0 (0.0 B) TX bytes:597 (597.0 B)

So i can't see any inet6 addresses on eth0 interface, so maybe it isn't a lowpan specific problem.

I use ip/ifconfig from busybox at version:

BusyBox v1.20.2 (2013-11-16 07:37:30 CET) multi-call binary.

- Alex

#3 lore raw
Quoted 20 lines · Tue, Dec 10, 2013 at 12:06:49PM CET, [email protected] wrote:

Hi,

thanks for your reply.

Quoted 15 lines · Jiri Pirko
Quoted 8 lines · Mon, Dec 09, 2013 at 04:32:39PM CET, [email protected] 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.

Quoted 71 lines

Yes I can see the address in "ip a".

Output of "ip a":

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
inet6 2001::2/64 scope global
valid_lft forever preferred_lft forever
inet6 2001::3/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe12:3456/64 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
4: wpan0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 127 qdisc pfifo_fast qlen 300
link/[804] aa:aa:aa:aa:aa:aa:aa:aa brd ff:ff:ff:ff:ff:ff:ff:ff
5: lowpan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1281 qdisc noqueue
link/[804] aa:aa:aa:aa:aa:aa:aa:aa brd ff:ff:ff:ff:ff:ff:ff:ff inet6 2001::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::1/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::a8aa:aaaa:aaaa:aaaa/64 scope link
valid_lft forever preferred_lft forever

Output of "ifconfig":

eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1144 (1.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lowpan0 Link encap:UNSPEC HWaddr AA-AA-AA-AA-AA-AA-AA-AA-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1281 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wpan0 Link encap:UNSPEC HWaddr AA-AA-AA-AA-AA-AA-AA-AA-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING NOARP MTU:127 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:300
RX bytes:0 (0.0 B) TX bytes:597 (597.0 B)

So i can't see any inet6 addresses on eth0 interface, so maybe it isn't a lowpan specific problem.

I use ip/ifconfig from busybox at version:

BusyBox v1.20.2 (2013-11-16 07:37:30 CET) multi-call binary.

- Alex

#4 lore raw
Quoted 17 lines · Jiri Pirko
Quoted 16 lines · Tue, Dec 10, 2013 at 12:06:49PM CET, [email protected] wrote:

Hi,

thanks for your reply.

Quoted 11 lines · Jiri Pirko
Quoted 8 lines · Mon, Dec 09, 2013 at 04:32:39PM CET, [email protected] 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.

Quoted 9 lines
Quoted 4 lines
Quoted 4 lines

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?

- Alex

#6 lore raw
In reply to Alexander Aring

I think this is not a lowpan specific problem, I have the same here:

$ /sbin/ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 08:00:27:27:58:92
          inet adr:192.168.56.2  Bcast:192.168.56.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:494 errors:0 dropped:0 overruns:0 frame:0
          TX packets:380 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:41584 (40.6 KiB)  TX bytes:51017 (49.8 KiB)
$ ip -6 addr show eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 2001:470:51a3:666::666/128 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe27:5892/64 scope link
       valid_lft forever preferred_lft forever

(standard ethernet interface of a virtual machine).

Regards,

Florent.

#5 lore raw
In reply to Alexander Aring
Quoted 28 lines · Tue, Dec 10, 2013 at 12:48:48PM CET, [email protected] wrote:
Quoted 17 lines · Jiri Pirko
Quoted 16 lines · Tue, Dec 10, 2013 at 12:06:49PM CET, [email protected] wrote:

Hi,

thanks for your reply.

Quoted 11 lines · Jiri Pirko
Quoted 8 lines · Mon, Dec 09, 2013 at 04:32:39PM CET, [email protected] 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.

Quoted 9 lines
Quoted 4 lines
Quoted 4 lines

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.

Quoted 4 lines

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.

Quoted 2 lines

- Alex