live migration

network settings for live migration must use the “Settings” button in the failover cluster manager.

Bind NDIS filter driver to a NDIS Mux driver

Normally, you cannot bind a NDIS filter driver to a NDIS Mux driver. This is because usually a NDIS filter driver will specify FilterMediaTypes as

HKR, Ndi\Interfaces, FilterMediaTypes, , "Ethernet, TokenRing, FDDI"

On the other hand, NDIS Mux driver need to specify

HKR, Ndi\Interfaces, LowerRange, 0, "nolower"

The “nolower” is not in the filter driver’s FilterMediaTypes list, thus you need to add “nolower” into FilterMediaTypes list in order to bind a filter driver to a mux driver.

See here for the reference.

wmi and powershell

 

Getting WMI Objects using PowerShell 2.0

WMI Enhancements in Windows PowerShell 2.0

Monitoring WMI Events with the Register-WMIEvent Cmdlet

parse ip addresses:

"10.1.1.1” | %{[Net.IPAddress]::Parse($_)}

NdisRegisterDeviceEx return STATUS_OBJECT_NAME_COLLISION

when i uninstall my mux driver and reinstall it, the driver fails at NdiRegisterDeviceEx() and the error code is STATUS_OBJECT_NAME_COLLISION.

This happens when i initially binding no adapter to my mux driver. If i initially bind one physical adapter to my mux driver, this does not happen. 

We can use !object \Device  and !object \GLOBAL?? to check the devices as shown here, but this provide no solution to my problem. I also traced to nt!IoCreateDevice and nt!IoCreateSymbolicLink, also no help. Maybe i’ll solve this bug later.

tcpanalyzer

TCPanalyzer using ESTAT info, RFC4898.