Console-conf and ip address

[Victor Palau]

Right, here in the office environment I can tell you that at least there
are 3 ubuntu-core devices :)  Nice to know that there is one more work
around to try.

But we need a more robust solution IMHO

On Fri, Sep 23, 2016 at 1:59 PM, Loïc Minier <loic.minier at ubuntu.com> wrote:

> I agree this isn't great; I wanted to mention an old but still working
> workaround: mDNS. Snapweb should publish a snapweb.local mDNS record on
> your LAN, so ssh you at snapweb.local should work. Note that this only works
> for one device at a time, so you want to change the hostname to have e.g.
> rpi3-xyz.local.
>
> On Fri, Sep 23, 2016 at 11:45 AM, Victor Palau <victor.palau at canonical.com
> > wrote:
>
>> Hi,
>>
>> I have an issue, and talking to a few people they had it too, where I set
>> up my user link to my sso via console -conf and failed to write down the ip
>> address of the box.
>>
>> Even having a keyboard and screen connected to the device (RPI2) does not
>> help to get access to the box, since I never had a chance to set up a
>> password. So I had to reflash the device and try again.
>>
>> My concern is that if I take the device somewhere else or I loose the
>> lease for that ip and did not set up a password, my only option would be to
>> reflash the device (if I dont have admin access in the network router i am
>> connected). This seems a bad user experience.
>>
>> Could we not at least have the ip address for the device always displayed
>> on the console login prompt.
>>
>> However, it still feels very fragile user experience
>>
>> Thanks
>>
>> Victor
>>
>> --
>> Devices mailing list
>> Devices at lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.snapcraft.io/mai
>> lman/listinfo/devices
>>
>>
>
>
> --
> - Loïc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.snapcraft.io/archives/devices/attachments/20160923/d01a9f60/attachment.html>