Contributor zubozrout on Network Manager
Be able to create a hot-spot in network-manager
Written by ariel.haviv the 8 Jun 12 at 09:34.
New
network manager enables creation of Ad-Hoc network, but many devides running Android won't recognize Ad-Hoc. To be able to work with hostapd you need to be a real pro, and it conflicts with network manager. It would be wonderful if hostapd worked out of the box (GUI) in network manager, with no conflicts.
Ubuntu should warn if your IP is in conflict
Written by lotif the 20 Aug 10 at 19:51.
Already implemented
Right now, if you manually set an IP in Ubuntu and if this IP is already registered in your network, or if somebody try to pick your IP by mistake or something, Ubuntu simply does nothing and let you without internet and without knowing what's going on. That's not right.
490
votes
493
7
3
Solution #1:
Ubuntu should warn that your IP is in conflict in the network
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>
63
votes
81
29
18
Solution #2:
Add help link/button to #1 solution with #3
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.
160
votes
168
10
8
Solution #3:
Add Fix button to solution #1
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.
87
votes
110
17
23
Solution #4:
Make IPwatchD a default app
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.
-44
votes
21
8
65
Solution #5:
Just fix it (and report it)
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).
-51
votes
1
9
52
Solution #6:
Display "network misconfiguration" message + disable networking
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.
Save network settings during install
Written by bud the 4 Mar 10 at 20:23.
New
For the installation many users use the CD. At live boot you can configure the network to fetch many packages during installation.
Before the installation, at reboot all settings are lost, and many users had to reconfigure the network.
For example, do you remember the wpa key?
Solution #1:
Save the configuration
Written by
bud the 4 Mar 10 at 20:23.
During install, the installer can store the connection settings in the "new" installed system. At reboot, the network is ready to go!
During install, the installer can store the connection settings in the "new" installed system. At reboot, the network is ready to go!
Solution #2:
Don't automatically save configuration. Add choice to.
What If you are like me (& I know some who are), and you like to see what the liveCD environment can do by adding tons of stuff. & then once you see how cool or messed up you can make it, you decide to install it anyways. Wouldn't you like a FRESH install without saving your mistakes and learning from them when you start Ubuntu from the HDD? I think it would be a cool choice to save the configurations that you made to the system, but why not just WRITE DOWN THE WPA KEY?!
I have mine saved in a secure location. that way, I can just get the piece of paper, and type it in. It isn't that difficult to type.
What If you are like me (& I know some who are), and you like to see what the liveCD environment can do by adding tons of stuff. & then once you see how cool or messed up you can make it, you decide to install it anyways. Wouldn't you like a FRESH install without saving your mistakes and learning from them when you start Ubuntu from the HDD? I think it would be a cool choice to save the configurations that you made to the system, but why not just WRITE DOWN THE WPA KEY?!
I have mine saved in a secure location. that way, I can just get the piece of paper, and type it in. It isn't that difficult to type.