betgaq.blogg.se

Note Starting with NDIS 6.20, wake-up patterns set through OID_PM_ADD_WOL_PATTERN must be restored by the miniport driver.Code: Select all > export compact hide-sensitiveĪdd admin-mac=B8:69:F4:F7:94:CD auto-mac=no comment=defconf name=bridgeĪdd name=default-dhcp ranges=192.168.88.10-192.168.88.254Īdd address-pool=default-dhcp disabled=no interface=bridge name=defconfĪdd bridge=bridge comment=defconf interface=ether2Īdd bridge=bridge comment=defconf interface=ether3Īdd bridge=bridge comment=defconf interface=ether4Īdd bridge=bridge comment=defconf interface=pwr-line1Īdd comment=defconf interface=bridge list=LANĪdd comment=defconf interface=ether1 list=WANĪdd address=192.168.88.1/24 comment=defconf interface=bridge network=192.168.88.0Īdd comment=defconf disabled=no interface=ether1Īdd address=192.168.88.0/24 comment=defconf gateway=192.168.88.1

Power management wake-up patterns through a set request of OID_PNP_ADD_WAKE_UP_PATTERN. Task offload encapsulation settings through a set request of OID_OFFLOAD_ENCAPSULATION. The multicast address list through a set request of OID_802_3_MULTICAST_LIST. The network packet filter through a set request of OID_GEN_CURRENT_PACKET_FILTER.

If the miniport driver returns TRUE in AddressingReset, NDIS calls a connectionless miniport driver's MiniportOidRequest function or a connection-oriented miniport driver's MiniportCoOidRequest function to set the following configuration settings: If the miniport driver returns FALSE in the AddressingReset parameter, the miniport driver restores its multicast addresses, packet filters, task offload settings, and wake up patterns to their initial state. The miniport driver determines who is responsible for restoring these settings by returning a Boolean value in the AddressingReset parameter. These setting are restored by either the miniport driver or NDIS. The miniport driver is responsible for restoring the hardware state of the device except for multicast addresses, packet filters, task offload settings, and wake up patterns. Restore the hardware state and the miniport driver's internal state to the state that existed before the reset operation. Deserialized and connection-oriented miniport drivers must return NDIS_STATUS_REQUEST_ABORTED for any queued send requests. For example, on a ring buffer for a bus-master direct memory access (DMA) device, the pointers to send buffers should be cleared. MiniportResetEx can complete synchronously or asynchronously with a call to NdisMResetComplete(see the following figure).Ĭlear out the data that is associated with any sends in progress. A miniport driver must register a MiniportResetEx function with NdisMRegisterMiniportDriver.