Laine Stump 2a537fe187 network: differentiate macvtap/bridge from host-bridge based networks ... Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1316465 An attempt to simplify the code for the VIR_NETWORK_FORWARD_BRIDGE case of networkUpdateState in commit b61db335 (first in release 1.2.14) resulted in networks based on macvtap bridge mode being erroneously marked as inactive any time libvirtd was restarted. The problem is that the original code had differentiated between a network using tap devices to connect to an existing host-bridge device (forward mode of VIR_NETWORK_FORWARD_BRIDGE and a non-NULL def->bridge), and one using macvtap bridge mode to connect to any ethernet device (still forward mode VIR_NETWORK_FORWARD_BRIDGE, but null def->bridge), but the changed code assumed that all networks with VIR_NETWORK_FORWARD_BRIDGE were tap + host-bridge networks, so a null def->bridge was interpreted as "inactive". This patch restores the original code in networkUpdateState		2016-03-25 13:21:29 -04:00
..
bridge_driver_linux.c	network: Add another collision check into networkCheckRouteCollision	2015-07-14 09:56:44 +02:00
bridge_driver_nop.c	Replace virNetworkObjPtr with virNetworkDefPtr in network platform APIs	2014-04-25 15:44:09 +01:00
bridge_driver_platform.c	bridge driver: extract platform specifics	2013-08-01 15:47:02 -06:00
bridge_driver_platform.h	struct _virNetworkDriverState: Annotate items	2015-03-13 15:55:56 +01:00
bridge_driver.c	network: differentiate macvtap/bridge from host-bridge based networks	2016-03-25 13:21:29 -04:00
bridge_driver.h	bridge_driver: Introduce networkBandwidthUpdate	2015-08-11 16:10:32 +02:00
default.xml	Remove the space before the slash in network XML	2013-08-28 08:05:46 +02:00
leaseshelper.c	Export virLease* functions for leases file handling	2016-03-18 17:29:53 +01:00