Bug 9082

Summary: Display network information on log-in screens
Product: [Runtime] General Runtime Reporter: Chris Lord <chrislord.net>
Component: General RuntimeAssignee: Jussi Kukkonen <jku>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: Medium CC: ross.burton
Version: 2.0   
Target Milestone: 2.2 M1   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Chris Lord 2016-02-09 14:31:11 UTC
It would be very useful if default log-ins (both graphical and terminal) would display network information. Useful for bringing up what will eventually be headless devices the first time.
Comment 1 Ross Burton 2016-02-11 23:25:56 UTC
In Sato the IP configuration should be in the network settings in the panel, and obviously ifconfig works at the console.  Can you elaborate on your thoughts?

Personally for this sort of thing I use mDNS and give the device a sensible name.  By default the hostname is the MACHINE (ie qemux86) but this is trivially changed.  All of my images have the hostname "bob" (hostname_pn-base-files = "bob" in local.conf) so if I can just do ssh bob.local or go to http://bob.local/.
Comment 2 Jussi Kukkonen 2016-02-18 09:10:01 UTC
What Ross said: it's not really clear what the missing feature is.
Comment 3 Chris Lord 2016-02-18 09:39:41 UTC
I hadn't thought of mDNS when I filed this, but my thought was pretty much it would be helpful for bringing up networked devices that are intended to be headless, but are still work-in-progress. Having a screen is surely awkward enough without having to also find a keyboard and type things.

Like Ross said, mDNS is a much nicer solution, but it still might be nice to list interface information on login screens so that you don't need to interact with a machine to find its IP.

Feel free to close this as WONTFIX, it's not really an issue for me anymore :)
Comment 4 Stephen K Jolley 2016-03-29 18:27:36 UTC
It appears that the information has been provided.
Comment 5 Jussi Kukkonen 2016-03-30 08:55:37 UTC
This is not happening for 2.1.


Moving to 2.2: if I find an easy way to provide this info, I'll try it. I will not spend a lot of time though: as Ross mentioned, mdns is an alternative  and IMO better solution: it even works on headless devices. The only drawback currently is the small amount of required configuration.
Comment 6 Ross Burton 2016-04-04 13:10:24 UTC
mDNS works out of the box if you ensure avahi-daemon is installed on the target.
Comment 7 Jussi Kukkonen 2016-06-30 15:21:43 UTC
I think wontfix is the realistic resolution instead of pushing the milestone further (especially since everyone involved seems fine with it).