Approximately every 60 seconds, Odyssey polls the adapter's status. When the call is made the following message is displayed in the OAC log if the log is set to level 5. The message appears to be an error message but it in no way indicates a problem.
COdysseyKernel::AdapterGetOID Failed OID 00010202 OID_GEN_PHYSICAL_MEDIUM Error Code = c00000bb NDIS_STATUS_NOT_SUPPORTED
When the call is made the adapter should return with a link state of connected or disconnected. If the state is connected Odyssey will “shut down” for lack of a better term.
One cause of the issue, seen with suppression, is when the registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
is set to 1. For additional information, refer to :
Microsoft: How to disable the Media Sensing feature for TCP/IP in WindowsTo correct the issue:
- Use Registry Editor (Regedt32.exe) to view the key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
Use caution whenever editing the Registry as serious problems can occur if modified incorrectly. Consult your IT organization for assistance with Registry issues
- Add the following registry value:
Value Name: DisableDHCPMediaSense
Data Type: REG_DWORD -Boolean
Value Data Range: 0, 1 (False, True) Default: 0 (False)
Description: This parameter controls DHCP Media Sense behavior. If you set this value data to 1, DHCP, and even non-DHCP, clients ignore Media Sense events from the interface. By default, Media Sense events trigger the DHCP client to take an action, such as attempting to obtain a lease (when a connect event occurs), or invalidating the interface and routes (when a disconnect event occurs).
If set to 0 Wireless suppression will not function properly.

Windows contains the "Media Sensing" feature. You may use this feature on a Windows-based computer using Transmission Control Protocol/Internet Protocol (TCP/IP) to detect whether your network media is in a "link state."
If OAC reports that a wired connection is active whenever you launch a VPN connection see
KB10522 on how to configure OAC to properly recognize the VPN virtual adaper.