** Description changed: Binary package hint: network-manager - NM has no only problems on servers, but on a bit more complicated - usecases on the clientside, e.g. if there are more fixed-ip settings on + NM has problems not only on servers, but also for more complicated use + cases on the client side, e.g. if there are more fixed-ip settings on lan, lan/wlan/mobile connected alltogether etc. Therefore, a few suggestions: - add an option "default setting for with connection type" - the now available "connect automatically" is a bit annoying, because I need to click way too many checkboxes. Or, as an alternative, save the previsously used setting (for me it is almost random which NM uses, despite it depends a bit of the frequency of using.) -add an option "use this connection for the default gateway/internet" - interesting for cases where e.g. mobile is used for internet while lan is used for local data sharing -add an option "use this connection for DNS" -for vpns: "autoconnection to the vpn if the connections ... are used" - interesting for e.g. vpns in unis -add an option "disconnect on log" - its very annoying when its disconnects only because the X-Server has crashed or something like that while dowloading files in text-consoles, screen etc. So, thats it, thanks ;)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/433540 Title: NM not flexible enough for complicated cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/433540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
