~vcs-imports/network-manager/trunk : changes

~vcs-imports/network-manager/trunk » Changes from revision 6566

From Revision 6561 to 6542

Rev	Summary	Authors	Date
6561	man: nmcli man page update for '--wait' and removing '--nowa... man: nmcli man page update for '--wait' and removing '--nowait', '--timeout' and '--private' -> 'private yes\|no' change	Jiří Klimeš	11 years ago
6560	cli: change '--private' to 'private yes\|no' in 'nmcli dev wi... cli: change '--private' to 'private yes\|no' in 'nmcli dev wifi connect' Missing 'private' argument default to private=no, the same way as before.	Jiří Klimeš	11 years ago
6559	cli: remove '--nowait' and '--timeout' options and use globa... cli: remove '--nowait' and '--timeout' options and use global '--wait' instead '--wait 0' corresponds to '--nowait' '--wait n' for n > 0 corresponds to '--timeout n'	Jiří Klimeš	11 years ago
6558	cli: add global '--wait <seconds>' option - timeout waiting ... cli: add global '--wait <seconds>' option - timeout waiting for operations --wait <0-maxint> 0 : means "do not wait". nmcli exits immediatelly with success. 1... : if operation doesn't finish within the timeout, nmcli exits with an error	Jiří Klimeš	11 years ago
6557	core: ensure newly-created master interfaces are ready for a... core: ensure newly-created master interfaces are ready for activation Reverts part of 2226a00cc2400a4150a83c119c8bfcc06ff2e988 core: add a "default-unmanaged" setting for devices Newly-created master interfaces are in the UNAVAILABLE state, but if they were created in response to a slave connection being activated, the master must be activated immediately too. But a device cannot be activated unless it's in the DISCONNECTED state, so restore that state change.	Dan Williams	11 years ago
6556	core: fix list manipulation when removing multiple slaves core: fix list manipulation when removing multiple slaves nm_device_release_one_slave() may change the list head, but the for loop in nm_device_master_release_slaves() can't handle that. Use a while loop instead.	Dan Williams	11 years ago
6555	libnm-glib: fix documentation C&P error libnm-glib: fix documentation C&P error	Dan Williams	11 years ago
6554	netlink: fix rtnl_route_alloc_cache() call netlink: fix rtnl_route_alloc_cache() call Same fix as in commit 195a09d7c0a57512b8e6298e97c3a3c4bad80fd0. NL_AUTO_PROVIDE is not a valid flag for this call and it's coincidental with ROUTE_CACHE_CONTENT, which is not what we want. One result arising from this fix is that per-device routes are now assigned priorities correctly. This means, for instance, you can have a wired and wireless connection on the same network, and have the wired connection always take precedence whilst it's available. Signed-off-by: Michael Chapman <mike@very.puzzling.org>	Pavel Šimerda	11 years ago
6553	build: don't install nm-dhcp-helper dbus permissions if we d... build: don't install nm-dhcp-helper dbus permissions if we don't need to The DHCP helper uses a private socket when building with dbus-glib >= 0.100, which means we don't need to install a D-Bus permissions file.	Dan Williams	11 years ago
6552	build: fix detection of Qt on non-Fedora platforms (bgo #691... build: fix detection of Qt on non-Fedora platforms (bgo #691583) Apparently Qt.pc is a Fedora-specific file to allow parallel install of Qt3 and Qt4. We should instead be using the upstream QtCore. https://bugzilla.gnome.org/show_bug.cgi?id=691583	Dan Williams	11 years ago
6551	trivial: remove a bit of debug code trivial: remove a bit of debug code	Dan Williams	11 years ago
6550	build: always generate docs at dist time (bgo #700093) build: always generate docs at dist time (bgo #700093) dist tarballs shouldn't ever be released without the documentation, and this allows us to build the tarballs with pre-generated docs that get installed on the end system, but don't need to be built there. So the end system doesn't need gtk-doc installed, only the dist system does. https://bugzilla.gnome.org/show_bug.cgi?id=700093	Dan Williams	11 years ago
6549	ifupdown: recalculate unmanaged specs on interface change (d... ifupdown: recalculate unmanaged specs on interface change (debian #707070) If a kernel interface changes its MAC address, and NM is not supposed to manage that interface, ifupdown needs to notice that MAC address change and tell NM that the unmanaged devices have changed, so that NM continues to not touch the device after the MAC has changed.	Dan Williams	11 years ago
6548	ifupdown: fix naming confusion in plugin hash tables ifupdown: fix naming confusion in plugin hash tables well_known_interfaces -> eni_ifaces, since it's a hash of any interfaces read from /etc/network/interfaces. well_known_ifaces -> kernel_ifaces, since it's a hash of any network subsystem interface the kernel knows about	Dan Williams	11 years ago
6547	ifupdown: clarify name of connections hash ifupdown: clarify name of connections hash 'iface_connections' is really the list of all NMIfupdownConnections known to the plugin, read from /e/n/i and hashed by block name. Since ifupdown doesn't store anything except connections from /e/n/i, just rename it to 'connections' to reduce confusion with the well_known_interfaces and well_known_ifaces hashes.	Dan Williams	11 years ago
6546	man: minor cleanup in nmcli manual page (for 'nmcli device w... man: minor cleanup in nmcli manual page (for 'nmcli device wimax list')	Jiří Klimeš	11 years ago
6545	devices: fix a bug in activation logic devices: fix a bug in activation logic It is legitimate to (re-)activate a connection on an already-active device, so remove the newly-added "sanity check" preventing that. Pointed out by jklimes.	Dan Winship	11 years ago
6544	configure.ac cleanups configure.ac cleanups - unconditionally use AM_SILENT_RULES, automake 1.11 is already required - remove the following macros whose results were unused: - AC_PROG_INSTALL - AC_HEADER_STDC - AC_CHECK_HEADERS(fcntl.h paths.h sys/ioctl.h sys/time.h syslog.h unistd.h) - AC_TYPE_MODE_T - AC_HEADER_TIME - AC_CHECK_FUNCS(select socket uname) - remove the following obsolete macros (not relevant on non-historic systems): - AC_PROG_GCC_TRADITIONAL - AC_FUNC_MEMCMP https://bugzilla.gnome.org/show_bug.cgi?id=700169	Adrian Bunk	11 years ago
6543	wifi: only remove AP on link timeout if not found by supplic... wifi: only remove AP on link timeout if not found by supplicant If for some reason the connection is disrupted and the AP rejects reconnection attempts (perhaps the driver has a bug, you get disconnected, and the AP rejects association because it thinks you're already associated), the AP object was being removed from the scan list by code meant to handle out-of-range or turned-off APs. Thus even though the AP was in-range, it wouldn't be found and the connection retried until the next scan. Instead, only remove the AP object from the scan list if the supplicant hasn't been able to exchange any frames with the AP. This preserves the out-of-range handling, becuase the supplicant wouldn't be able to talk to the AP and thus 'ssid_found' will be FALSE, and also ensures that an in-range but confused AP says in the scan list and will be retried immediately.	Dan Williams	11 years ago
6542	platform: fix NMFakePlatformLink handling platform: fix NMFakePlatformLink handling	Pavel Šimerda	11 years ago

Older »