Landscape Client

sysinfo doesn't report IPv6 addresses

Bug #829379 reported by Andreas Hasenack on 2011-08-19

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	Landscape Client	Fix Released	High	Maximiliano Bertacchini	Landscape Client backlog

Bug Description

In my case eth0 has both an IPv4 and a global IPv6 address, but sysinfo doesn't report it:

root@ls1-lucid:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr f2:3c:91:96:7c:70
          inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:255.255.255.0
          inet6 addr: yyyy:yyyy::yyyy:yyyy:yyyy:yyyy/64 Scope:Global
          inet6 addr: fe80::f03c:91ff:fe96:7c70/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:18831 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21597 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4069307 (4.0 MB) TX bytes:2384860 (2.3 MB)
          Interrupt:28

root@ls1-lucid:~# landscape-sysinfo
  System load: 0.11 Processes: 104
  Usage of /: 30.6% of 3.94GB Users logged in: 1
  Memory usage: 23% IP address for eth0: xxx.xxx.xxx.xxx
  Swap usage: 0%

Graph this data and manage this system at https://landscape.canonical.com/

Tags:

Andreas Hasenack (ahasenack) on 2011-08-19

tags:	added: ipv6
Changed in landscape-client:
milestone:	none → backlog

Revision history for this message

🤖 Landscape Builder (landscape-builder) wrote on 2015-12-23:

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-client:
status:	New → Invalid

Revision history for this message

Markus Ueberall (ueberall) wrote on 2016-01-15:

Given the growing support/use of IPv6, it would be nice to get this implemented.

Changed in landscape-client:
status:	Invalid → New

Adam Collard (adam-collard) on 2016-04-08

Changed in landscape-client:
importance:	Undecided → High
status:	New → Triaged
tags:	added: squad-bug

Maximiliano Bertacchini (maxiberta) on 2019-01-25

Changed in landscape-client:
assignee:	nobody → Maximiliano Bertacchini (maxiberta)

Maximiliano Bertacchini (maxiberta) on 2019-02-05

Changed in landscape-client:
status:	Triaged → In Progress

Maximiliano Bertacchini (maxiberta) on 2019-02-11

Changed in landscape-client:
status:	In Progress → Fix Committed

Patrickvw (patrick-vande-walle) on 2019-07-23

Changed in landscape-client:
status:	Fix Committed → Fix Released

Revision history for this message

Patrickvw (patrick-vande-walle) wrote on 2019-07-23:

For some odd reason, I was able to change the status by mistake to "fix committed" but cannot revert to the previous status. I actually have no fix to offer.
Please revert my changes.

Maximiliano Bertacchini (maxiberta) on 2019-07-23

Changed in landscape-client:
status:	Fix Released → Fix Committed

Revision history for this message

Christian Ehrhardt  (paelzer) wrote on 2021-09-20:

$ landscape-sysinfo
...
IPv4 address for lxdbr0: 10.128.57.1
IPv6 address for lxdbr0: fd42:97e3:9a49:c9a1::1

It is fix released at least in 19.12-0ubuntu4.2 and later.

Changed in landscape-client:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.