NDIS6.0 如何拦截数据包

见习学术士 见习学术士 墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年,写一次发全网 我也要 + 加入社区


VOID
FilterReceiveNetBufferLists(
IN NDIS_HANDLE FilterModuleContext,
IN PNET_BUFFER_LIST NetBufferLists,
IN NDIS_PORT_NUMBER PortNumber,
IN ULONG NumberOfNetBufferLists,
IN ULONG ReceiveFlags
)
/*++

Routine Description:

FilerReceiveNetBufferLists is an optional function for filter drivers.
If provided, this function process receive indications made by underlying
NIC or lower level filter drivers. This function can also be called as a
result of loopback. If this handler is NULL, NDIS will skip calling this
filter when processing a receive indication and will call the next upper
filter in the stack with a non-NULL FitlerReceiveNetBufferLists handler
or the procotol driver. A filter that doesn't provide a
FilterReceiveNetBufferLists handler can not provided a
FilterReturnNetBufferLists handler or a initiate a receive indication on
its own.

Arguments:

FilterModuleContext: Pointer to our filter context area.
NetBufferLists: A linked list of NetBufferLists allocated by underlying driver each containing
one NetBuffer.
PortNumber: Port on which the Receive is indicated
ReceiveFlags: Flags associated with the Receive such as whether the filter
can pend the receive


Return Value:

None

--*/
{

PMS_FILTER pFilter = (PMS_FILTER)FilterModuleContext;
BOOLEAN DispatchLevel;
ULONG Ref;
BOOLEAN bFalse = FALSE;
PNET_BUFFER_LIST CurrNbl, NextNbl;
PNET_BUFFER pCurrentNetBuffer;
PVOID pPacketBuffer = NULL;
ULONG ulPacketLength = 0;
IPRESULT result = enumIP_Unknow;

#if DBG
ULONG ReturnFlags;
#endif

DEBUGP(DL_TRACE, ("===>ReceiveNetBufferList: NetBufferLists = %p.\n", NetBufferLists));
do
{

DispatchLevel = NDIS_TEST_RECEIVE_AT_DISPATCH_LEVEL(ReceiveFlags);
#if DBG
FILTER_ACQUIRE_LOCK(&pFilter->Lock, DispatchLevel);

if (pFilter->State != FilterRunning)
{
FILTER_RELEASE_LOCK(&pFilter->Lock, DispatchLevel);

if (NDIS_TEST_RECEIVE_CAN_PEND(ReceiveFlags))
{
ReturnFlags = 0;
if (NDIS_TEST_RECEIVE_AT_DISPATCH_LEVEL(ReceiveFlags))
{
NDIS_SET_RETURN_FLAG(ReturnFlags, NDIS_RETURN_FLAGS_DISPATCH_LEVEL);
}

NdisFReturnNetBufferLists(pFilter->FilterHandle, NetBufferLists, ReturnFlags);
}
break;
}
FILTER_RELEASE_LOCK(&pFilter->Lock, DispatchLevel);
#endif

ASSERT(NumberOfNetBufferLists >= 1);

FILTER_ACQUIRE_LOCK(&pFilter->Lock, DispatchLevel);
CurrNbl = NetBufferLists;
while (CurrNbl && result != enumIP_Block)
{
for(pCurrentNetBuffer = NET_BUFFER_LIST_FIRST_NB(CurrNbl);
pCurrentNetBuffer != NULL;
pCurrentNetBuffer = NET_BUFFER_NEXT_NB(pCurrentNetBuffer))
{
pPacketBuffer = NULL;
ReadNetBuffer(pCurrentNetBuffer, &pPacketBuffer, ulPacketLength);

if( pPacketBuffer )
{
if( g_ndisFirewall != NULL )
{
result = g_ndisFirewall->Filter( pPacketBuffer, ulPacketLength, enumPD_Recieve );

if( result == enumIP_Block )
{
break;
}
}

non_paged_pool::__DeallocateSystemMemory( pPacketBuffer );
pPacketBuffer = NULL;
}
}
CurrNbl= NET_BUFFER_LIST_NEXT_NBL(CurrNbl);
}
FILTER_RELEASE_LOCK(&pFilter->Lock, DispatchLevel);

if( result == enumIP_Block )
{
NDIS_SET_RECEIVE_FLAG(ReceiveFlags, NDIS_RECEIVE_FLAGS_RESOURCES);
NdisFReturnNetBufferLists(pFilter->FilterHandle, NetBufferLists, ReceiveFlags);
break;
}


//
// If necessary, queue the NetBufferList in a local structure for later processing.
// We may need to travel the list, some of them may not need post processing
//
if (pFilter->TrackReceives)
{
FILTER_ACQUIRE_LOCK(&pFilter->Lock, DispatchLevel);
pFilter->OutstandingRcvs += NumberOfNetBufferLists;
Ref = pFilter->OutstandingRcvs;

FILTER_LOG_RCV_REF(1, pFilter, NetBufferLists, Ref);
FILTER_RELEASE_LOCK(&pFilter->Lock, DispatchLevel);
}

NdisFIndicateReceiveNetBufferLists(
pFilter->FilterHandle,
NetBufferLists,
PortNumber,
NumberOfNetBufferLists,
ReceiveFlags);


if (NDIS_TEST_RECEIVE_CANNOT_PEND(ReceiveFlags) &&
pFilter->TrackReceives)
{
FILTER_ACQUIRE_LOCK(&pFilter->Lock, DispatchLevel);
pFilter->OutstandingRcvs -= NumberOfNetBufferLists;
Ref = pFilter->OutstandingRcvs;
FILTER_LOG_RCV_REF(2, pFilter, NetBufferLists, Ref);
FILTER_RELEASE_LOCK(&pFilter->Lock, DispatchLevel);
}

} while (bFalse);

DEBUGP(DL_TRACE, ("<===ReceiveNetBufferList: Flags = %8x.\n", ReceiveFlags));

}


这样整个拦截 NBL 好像有问题,一些正常的SOCKET连接都超时了。
怎么样能对单个NB 拦截呢?
...全文

相关推荐

design guide for wireless miniport driver development

在NDIS版本介绍部分,提供了对NDIS不同版本的概述,特别是NDIS 6.0及以后版本的介绍,这对于兼容不同版本的Windows操作系统以及了解驱动程序开发中可能遇到的版本特定问题至关重要。

sherry1981

windows7以上平台 NDISFilter 网卡过滤驱动开发

by fanxiushu 2019-01-16 转载或引用请注明原始作者 这里讨论的都是基于WIN7以上平台,NDIS 6.0以上版本的网络驱动。 做个驱动的目的,是因为很早之前,我使用 TDI 和 NDIS5.1 框架的...

雨中风华

NDIS 6.0 Filter Driver实战:数据包过滤与MAC地址查询

在Windows网络驱动开发中,NDIS(Network Driver Interface Specification)提供了一套标准化的网络数据路径扩展机制。其中,NDIS过滤驱动(Filter Driver)位于协议驱动与网卡驱动之间,能够以透明方式监控和干预所有收发数据包,是构建网络监控、流量管理及安全过滤功能的理想选择。通过挂载到网卡设备栈,驱动开发者可以截获网络数据包(NBL),进行统计、修改或丢弃,并可通过OID请求查询底层硬件属性,例如获取网卡的真实MAC地址。这种内核态的数据可见性与控制能力

鸳鸯蝴蝶派

NDIS 6.0 Filter驱动数据包收发与MAC地址查询实战指南

在Windows网络驱动开发中,NDIS(网络驱动接口规范)是连接协议栈与物理网卡的核心框架。Filter驱动(LWF)作为轻量级的过滤模块,通过回调机制透明介入数据包的发送与接收路径,实现对网络流量的实时监控与处理。NET_BUFFER_LIST承载着数据包的完整生命周期,而OID请求则用于向底层网卡查询MAC地址等关键属性,是驱动层获取硬件信息的标准通道。这类底层技术广泛应用于流量监控、防火墙、协议分析和链路聚合等场景。掌握NDIS Filter驱动的收发回调实现与OID查询机制,不仅是构建高性能网络功

镝不咸

Filter驱动开发笔记

它可以拦截和处理通过NDIS的数据包,从而实现网络监控、安全检查等功能。#### 2.

u011096139
评论 3
收藏 已收藏
分享
返回顶部
见习学术士
网络编程 18,356 成员 64,161 内容