summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* settings: shortcut nm_settings_get_connection_by_uuid() if @uuid is invaliddcbw/dcbw/devices-for-all-1Thomas Haller2014-12-111-0/+3
| | | | Signed-off-by: Thomas Haller <thaller@redhat.com>
* fixup! core: allow multiple devices with the same interface nameDan Williams2014-12-111-11/+4
| | | | VPNs won't necessarily specify a device.
* core: allow multiple devices with the same interface nameDan Williams2014-12-116-125/+192
| | | | | | | | | | | | | | | | | | | | | | | | | But, of course, only one realized device can have the same interface name at a time. This commit effectively reverts most of: 1b37cd03409fa3c0fb26fb6e8093b54b2b7c5d8d core: allow ActiveConnections to be created without a device But it's not easy to do a separate revert of that code due to interdependencies with nm-manager.c. Creating devices when they are defined by a connection also makes makes it possible to require the NMDevice to be present when activating it, which means we can remove a bunch of code from NMManager that had to handle software devices not existing yet at the time of the activation request. But it also means we must be more careful when finding master interfaces during slave activation, since we cannot simply match by interface name alone. Instead we must find the master which matches both the interface name and can control slaves of the type which is being activated.
* fixup! core: ensure platform links are compatible with the NMDeviceDan Williams2014-12-114-3/+5
| | | | | Some of these devices didn't specify their "connection_type" earlier, but that was an oversight. Fix that.
* core: ensure platform links are compatible with the NMDeviceDan Williams2014-12-1119-21/+121
| | | | | | | | Ensure the platform link with the same interface name as the NMDevice is actually compatible with it before using the link for initialization of device properties. If not, remove the NMDevice and create a new one since there are kernel resources with a different type.
* fixup! libnm/libnm-glib: add NMClient.get_all_devices() method and ↵Dan Williams2014-12-115-6/+125
| | | | "all-devices" property
* fixup! libnm/libnm-glib: add NMClient.get_all_devices() method and ↵Dan Williams2014-12-111-0/+8
| | | | "all-devices" property
* libnm/libnm-glib: add NMClient.get_all_devices() method and "all-devices" ↵Dan Williams2014-12-118-32/+167
| | | | | | | property Mirror new NetworkManager API to return both real devices and device placeholders.
* fixup! api/manager: add GetAllDevices() method and AllDevices propertyDan Williams2014-12-113-14/+42
|
* api/manager: add GetAllDevices() method and AllDevices propertyDan Williams2014-12-113-3/+67
| | | | Returns both realized and un-realized devices.
* fixup! core: create devices first and realize them laterDan Williams2014-12-111-2/+3
|
* fixup! core: create devices first and realize them laterDan Williams2014-12-111-18/+1
| | | | All virtual connections are now backed by NMDevices.
* fixup! core: create devices first and realize them laterDan Williams2014-12-111-0/+6
| | | | Don't delete software devices, just unrealize them.
* fixup! core: create devices first and realize them laterDan Williams2014-12-111-1/+1
|
* fixup! core: create devices first and realize them laterDan Williams2014-12-111-8/+13
| | | | Don't leak unrealized devices in existing APIs.
* core: create devices first and realize them laterDan Williams2014-12-1112-206/+270
| | | | | | | | | | Unrealized devices aren't backed by kernel resources and so won't know all of their attributes. That means three things: 1) they must update their attributes when they become realized 2) they must clear those attributes when unrealized 3) they must be looser in checking compatible connections until they are realized
* core: rearrange some VLAN code and clean up dispose()Dan Williams2014-12-111-52/+38
| | | | | Move parent-related stuff before its callers and clean up dispose so that we no longer need priv->disposed.
* platform: move InfiniBand property reading into the platformDan Williams2014-12-115-16/+165
|
* fixup! core: earlier software capability detectionDan Williams2014-12-111-2/+5
|
* core: earlier software capability detectionDan Williams2014-12-116-18/+50
| | | | | | | We need to know whether we can create interfaces of any given NMDevice subclass or not. So don't rely on just the NMPlatformLink for that information, because we won't have a platform link for software devices before we create them.
* fixup! core: add class function for device unrealizationDan Williams2014-12-111-1/+4
|
* fixup! core: add class function for device unrealizationDan Williams2014-12-114-19/+25
|
* fixup! core: add class function for device unrealizationDan Williams2014-12-111-12/+28
|
* core: add class function for device unrealizationDan Williams2014-12-114-13/+120
|
* fixup! libnm-glib/libnm: add support for Realized device propertyDan Williams2014-12-116-63/+64
|
* libnm-glib/libnm: add support for Realized device propertyDan Williams2014-12-116-0/+81
|
* fixup! core: add "real" NMDevice propertyDan Williams2014-12-114-25/+24
|
* core: add "realized" NMDevice propertyDan Williams2014-12-114-6/+67
| | | | | | | This property is TRUE for devices that exist either as a kernel device or are backed by some other resource (eg, ModemManager object, Bluez device, etc). It will eventually be FALSE for software devices that are not yet instantiated.
* fixup! core: check duplicate devices by interface name not UDIDan Williams2014-12-111-0/+4
|
* core: check duplicate devices by interface name not UDIDan Williams2014-12-111-15/+13
| | | | | | We can't have devices with duplicate interface names so we might as well use that for dupe checking instead of the (mostly useless) UDI.
* fixup! core: split device creation and device setupDan Williams2014-12-111-0/+3
|
* fixup! core: split device creation and device setupDan Williams2014-12-111-2/+1
|
* fixup! core: split device creation and device setupDan Williams2014-12-111-5/+0
|
* fixup! core: split device creation and device setupDan Williams2014-12-112-3/+3
|
* fixup! core: split device creation and device setupDan Williams2014-12-118-67/+67
|
* core: split device creation and device setupDan Williams2014-12-1130-794/+781
| | | | | | Future patches will create devices long before they are backed by kernel resources, so we need to split NMDevice object creation from actual setup based on the backing resources.
* fixup! core: move permanent and initial MAC address reading to NMDevice and ↵Dan Williams2014-12-112-26/+30
| | | | NMPlatform
* core: move permanent and initial MAC address reading to NMDevice and NMPlatformDan Williams2014-12-119-239/+176
| | | | | | | | Ethernet, WiFi, and VLAN used the same implementation for initial address. Ethernet and WiFi used the same implementation (and duplicated code) for permanent MAC address, plus they both used ethtool in what should be generic code, which is better done in the platform.
* fixup! platform: move driver & firmware version reading into the platformDan Williams2014-12-111-0/+5
|
* platform: move driver & firmware version reading into the platformDan Williams2014-12-115-46/+73
|
* platform: add nm_platform_link_get_by_address()Dan Williams2014-12-114-0/+78
|
* platform: ensure created interface matches requested typeDan Williams2014-12-111-5/+17
| | | | | If the caller requested that a bond be created, don't return success if there was an existing bridge with the same name.
* fixup! platform: return link objects from add functionsDan Williams2014-12-113-3/+4
|
* fixup! platform: return link objects from add functionsDan Williams2014-12-111-5/+15
|
* platform: return link objects from add functionsDan Williams2014-12-1114-59/+124
|
* fixup! core: move virtual interface name handling into device pluginsThomas Haller2014-12-111-4/+6
|
* fixup! core: move virtual interface name handling into device pluginsThomas Haller2014-12-111-0/+8
| | | | (allow-none) for the out arguments
* fixup! core: move virtual interface name handling into device pluginsThomas Haller2014-12-112-5/+8
| | | | Saves 16 copies of these static arrays.
* fixup! core: move virtual interface name handling into device pluginsDan Williams2014-12-111-63/+57
|
* core: move virtual interface name handling into device pluginsDan Williams2014-12-115-172/+248
| | | | | | Instead of having a bunch of logic in the Manager for determining the VLAN and Infiniband virtual interface names, move the type-specific logic into the plugins themselves.
View Lorry Controller Status