console-conf shows the previous IP address after reconfiguration

[Robert Liu]

[steps]
1. Set up a system connected to WiFi AP-1 which is using subnet-A
2. After entering system, launch console-conf to re-configure WiFi settings
  $ sudo console-conf
3. Go through wifi setup process again, but connect to WiFi AP-2 which is using subnet-B
4. In console-conf finish page (Configuration Complete), observe the IP addresses listed
5. Use command ifconfig to check the current wlan0 IP address in use

[expected]
IP addresses in step 4 & step 5 should be the same

[actual]
IP address in step 4 is still the old IP address, and ifconfig shows the new one.
It seems that console-conf/subiquity has to handle the addr_change event for this case.

[Michael Hudson-Doyle (mwhudson)]

Do you mean the screen with the "Configuration complete" header or the one
that starts "Congratulations! This device is now registered to
{realname}."? The former would surprise me, the latter not at all really.

On 19 January 2017 at 16:35, Robert Liu <email address hidden> wrote:

> ** Attachment added: "subiquity-debug.log"
> https://bugs.launchpad.net/snappy/+bug/1657633/+
> attachment/4806109/+files/subiquity-debug.log
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to Snappy.
> https://bugs.launchpad.net/bugs/1657633
>
> Title:
> console-conf shows the previous IP address after reconfiguration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1657633/+subscriptions
>

[Robert Liu (robertliu)]

Hi @Michael,

This test is done with core snap r.888.
The screen i mentioned was the one with 'Configuration Complete' header.
Attached two screenshots, the first one is wifi configuration which shows the IP address before changing AP.
The second one is the last step of console-conf shows 'Configuration Complete' and the IP address. According to the log and ipconfig result, the IP address should be 192.168.158.118.

[Robert Liu (robertliu)]

It has associated with another AP with a different subnet, but the IP address displayed is still the old one.

[Dimitri John Ledkov (xnox)]

console-conf is not meant to be used more than once....

Why are you using console-conf again? is there any documentation about that you are following or test case?

If you meant to change networking settings, expectation is that one would modify /etc/netplan/* files and perform sudo netplan apply; or use snapd to change the netplan yaml.

[Oliver Grawert (ogra)]

It used to be a pretty common practice in the community in UC16 days to (ab)use console-conf as network-setup GUI when you had a device that needed to be moved between WLANs regulary (note that there wasn't even documentation about netplan in the early days of UC16. netplan was used in Ubuntu Core way before it entered the normal Ubuntu distro as a default tool).

I guess that habit simply stuck around because people fond instructions via google ...

[Robert Liu (robertliu)]

At that moment, I found console-conf could be used to update the network configuration easily. that was the reason I used console-conf in that way.

If console-conf is not for the purpose, perhaps we could add a note somewhere and add a check in console-conf to prevent the abuse. Does this make more sense?