Windows TAP Driver PacketFilter Type issues

Weekly dev snapshots are available for testing.
We talk about them here. Testing features in the dev snapshot helps the features make it to stable.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please report your experience with testing branch. Include what you were using and how
If there is a problem, the more info the better!
Post Reply
carthickeyan
OpenVpn Newbie
Posts: 3
Joined: Wed Jun 04, 2014 5:31 pm

Windows TAP Driver PacketFilter Type issues

Post by carthickeyan » Wed Jun 25, 2014 2:44 pm

Hi

As part of Windows Hardware Certification we are running NDISTest 6.5 - [2 Machine] -PacketFilters test with our OpenVPN Windows TAP Driver. This test fails with an error saying Filter Directed / Multicast is not set correctly in Miniport/HW. since ours is virtual adapter we will not be able to set the filter type in HW as mentioned in source code (oidrequest.c). Any idea how can we set packet filter type in our openVPN TAP driver.

Note: we are using Latest OpenVPN Windows TAP driver from OpenVPN GIT.

Thank You,
Regards,

Karthikeyan Palanisamy

Content of the LOG:

10001 StartTime: 18:09:39.970
Packet filter on Test Device Directed.
Address to test: Invalid Multicast Address: 01-02-03-04-05-00
- Packets required to pass the test : 0 - Minimum Passing Percentage required : 0
Receive Filter set as: Directed
ClOpen::SetPacketFilter
- Name: Test Open for receiving
- Packet Filter: Directed

SimpleCommunicationHelper::SetupSend
- Name: SupportCommHelper
- Packet Size: 1514
- Destination MAC: 01-02-03-04-05-00
- Send Configuration
- Total NBs to send: 250 (10 Calls, 5 NBLs/Call, 5 NBs/NBL)
- Send Duration (ms): 0

CommunicationHelper::StartReceive
- Name: TestCommHelper
- Type: SimpleCommunicationHelper
- Traffic Manager Type: NDT_SIMPLE_TRAFFIC_MGR
- Receive Process Mech: NDT_PROCESS_RECEIVE_AT_PASSIVE
- Configured NetBufferModuleStack:
- [1] NDT_SIMPLE_NDISTEST_PAYLOAD_MODULE
- [2] NDT_NDISTEST_HEADER_MODULE
- [3] NDT_LLC_SNAP_HEADER_MODULE
- [4] NDT_ETHERNET_MEDIA_HEADER_MODULE
- STATUS: NDIS_STATUS_SUCCESS

CommunicationHelper::StartSend
- Name: SupportCommHelper
- Type: SimpleCommunicationHelper
- Traffic Manager Type: NDT_SIMPLE_TRAFFIC_MGR
- Send Mechanism: NDT_SEND_AT_PASSIVE
- Send Complete Mech: NDT_VERIFY_SEND_COMPLETE_AT_PASSIVE
- NDIS Send Flags: 0
- Send Latency (ms): 0
- Preallocated NBL Count: 5
- Configured NetBufferModuleStack:
- [0] NDT_SIMPLE_NB_ALLOCATOR_MODULE
- [1] NDT_SIMPLE_NDISTEST_PAYLOAD_MODULE
- [2] NDT_NDISTEST_HEADER_MODULE
- [3] NDT_LLC_SNAP_HEADER_MODULE
- [4] NDT_ETHERNET_MEDIA_HEADER_MODULE
- STATUS: NDIS_STATUS_SUCCESS

EndPoint::WaitForSendsToComplete
- Name: SupportCommHelper_EndPoint
- Timeout (ms): 300000
EndPoint::StopReceive
- Name: TestCommHelper_EndPoint
- Timeout (ms): 1000
EndPoint::GetSendResults
- Name: SupportCommHelper_EndPoint
EndPoint::GetReceiveResults
- Name: TestCommHelper_EndPoint
Test adapter sent 250 packets of 250 expected.
50021 0 packets expected but received 250 packets,
Some of the possible reasons for the failure:
1. Filter Directed was not correctly set up on the miniport/hardware

Post Reply