Written by lotif the 20 Aug 10 at 19:51.

A little warning and a red sign next to the connection indicator means a lot in usability.

A picture is worth a 1000 words.

A little warning and a red sign next to the connection indicator means a lot in usability. A picture is worth a 1000 words. <a href="http://desmond.yfrog.com/Himg59/scaled.php?tn=0&server=59&filename=capturadetela1y.png&xsize=640&ysize=640"><img src="http://desmond.yfrog.com/Himg59/scaled.php?tn=0&server=59&filename=capturadetela1y.png&xsize=640&ysize=640" border="0" /></a>

Written by Oxwivi the 24 Aug 10 at 08:16.

A non-technical and standard user will not understand what to do in such a situation. A fix button bay help, but if it doesn't, a help link/button would go a long way to solve the problem.

A non-technical and standard user will not understand what to do in such a situation. A fix button bay help, but if it doesn't, a help link/button would go a long way to solve the problem.

Written by DaedalusPrime the 24 Aug 10 at 11:58.

Clicking the "FIX" button would attempt to change the IP address automatically by 1) if DHCP is enabled, renew the IP, or 2) if not DHCP, perform a search for an IP that appears to be open on the current subnet, using ipwatchd or a similar mechanism.

Clicking the "FIX" button would attempt to change the IP address automatically by 1) if DHCP is enabled, renew the IP, or 2) if not DHCP, perform a search for an IP that appears to be open on the current subnet, using ipwatchd or a similar mechanism.

Written by lotif the 24 Aug 10 at 13:27.

As some pointed out, there's already an app out there which makes the job pretty well: IPwatchD. Let's make it a default app!



The only drawback I see is that the warnings aren't any further than this message. It should add an icon below the connection icon, like in Solution #1.

To install it, go to http://ipwatchd.sourceforge.net/ or just search for ipwatch on synaptic.

As some pointed out, there's already an app out there which makes the job pretty well: IPwatchD. Let's make it a default app! <a href="http://a.imageshack.us/img715/8051/capturadetelapb.png"><img src="http://a.imageshack.us/img715/8051/capturadetelapb.png" border="0" /></a> The only drawback I see is that the warnings aren't any further than this message. It should add an icon below the connection icon, like in Solution #1. To install it, go to http://ipwatchd.sourceforge.net/ or just search for ipwatch on synaptic.

Written by ivanpd the 30 Aug 10 at 14:42.

I think part of the Ubuntu philosophy is that the user will be provided with a reasonable solution that works in most cases by default. Instead of complaining and allowing the user to fix it, I think the right approach would be:
- If DHCP is enabled, request a new IP with no user intervention.
- If DHCP is not enabled, allow the user to fix it automatically (as described in #3, no-dhcp) or to change the configuration by hand.

I don't have the time to draw anything (help is welcome to show this idea), but something similar to the pic in #1 with the text "Enable automatic fix or change settings by hand" would do.

Regarding the design, I think "Enable automatic fix" and "change settings by hand" could both have the appearance of web links (instead of buttons).

I think part of the Ubuntu philosophy is that the user will be provided with a reasonable solution that works in most cases by default. Instead of complaining and allowing the user to fix it, I think the right approach would be: - If DHCP is enabled, request a new IP with no user intervention. - If DHCP is not enabled, allow the user to fix it automatically (as described in #3, no-dhcp) or to change the configuration by hand. I don't have the time to draw anything (help is welcome to show this idea), but something similar to the pic in #1 with the text "Enable automatic fix or change settings by hand" would do. Regarding the design, I think "Enable automatic fix" and "change settings by hand" could both have the appearance of web links (instead of buttons).

Written by amay82 the 1 Sep 10 at 14:23.

If someone picks an IP address manually, (s)he should know what (s)he is doing, so a generalised "network misconfiguration" message + disabling the network should be enough. The rest can be seen in the system logs.

If someone picks an IP address manually, (s)he should know what (s)he is doing, so a generalised "network misconfiguration" message + disabling the network should be enough. The rest can be seen in the system logs.