Forums

[Vadim Smirnov]

Internet Gateway code simply treats all adapters with media different from NdisMedium802_3 as WAN. This is not correct of course, but works for most cases and good enough for the sample. I think your intrface reports media different from 802.3 and this causes described misbehave. NDIS_MEDIUM is defined as following:

typedef enum _NDIS_MEDIUM
{
NdisMedium802_3,
NdisMedium802_5,
NdisMediumFddi,
NdisMediumWan,
NdisMediumLocalTalk,
NdisMediumDix, // defined for convenience, not a real medium
NdisMediumArcnetRaw,
NdisMediumArcnet878_2,
NdisMediumAtm,
NdisMediumWirelessWan,
NdisMediumIrda,
NdisMediumBpc,
NdisMediumCoWan,
NdisMedium1394,
NdisMediumInfiniBand,
#if ((NTDDI_VERSION >= NTDDI_VISTA) || NDIS_SUPPORT_NDIS6)
NdisMediumTunnel,
NdisMediumNative802_11,
NdisMediumLoopback,
#endif // (NTDDI_VERSION >= NTDDI_VISTA)

#if (NTDDI_VERSION >= NTDDI_WIN7)
NdisMediumWiMAX,
NdisMediumIP,
#endif

There are too many things to improve in this sample to build a real NAT aplication suitable for different environments and it would take plenty of time to build a desired list. You’d better look at some solutions alreaddy available on market to see what features can be implemented.

[Vadim Smirnov]

Thank you for reporting this, but the more detailed network configuration would be appreciated. Like what network adapters do you have, what type and which of them are connected (ipconfig output?). And how Internet Gateway identifies these ones (may be screenshot?).

Although, I have to note that Internet Gateway is just a sample coded in a day to demonstrate usage of WinpkFilter driver for NAT solutions. And of course it does not pretend to be a well tested end user application.

[Vadim Smirnov]

Ndisrdmp is a miniport part of WinpkFilter NDIS IM driver. However, if you use one of the latest versions (starting 3.0.8) of WinpkFilter then it is supposed to install NDIS LWF driver on Windows Vista and later which does not have that part. Probably the WinpkFilter version you use is out-of-date.

[Vadim Smirnov]

Yes, you can fragment the resulted packet and send out two packets instead one, server will reassemble it. However, please note that fragmented packets often are blocked by firewalls.

[Vadim Smirnov]

There was one fix in 3.1.1 (LWF unload/unbind bug) which may be related to your problem. It was very difficult to reproduce and caused various side effects one of those is network lock.

[Vadim Smirnov]

Have you started command line (under which you execute snetcfg) under Administrator account?

Normally when you install LWF driver the network is temporary disconnected and then reconnected. Do you mean that in your case the network is permanently disabled?

[Vadim Smirnov]

Windows Packet Filter Kit 3.1.1 released:
– Updated C# samples and interface header
Bug fixes:
– Unload LWF driver hang problem fixed. As a side issue this bug has also caused network lock with Windows Hardware Certification Kit on some systems

If you are eligible for a free update, please send the following details to [email protected] tо receive an update instruction:

1) Your order ID.
2) An approximate date of purchasing.

[Vadim Smirnov]

Только на C++, на C# перенесены только самые базовые примеры.

[Vadim Smirnov]

Исходники wwwcensor включены в дистрибутив, можете их найти среди msvc примеров.

Ваша задача так же решаема, но невозможно же в самом деле написать пример под каждый конкретный случай 😉

[Vadim Smirnov]

I’m sorry for the delayed response. I’ve been away for the New Year holidays.

I have generated the new netcfgInstanceId , change it in my inf file and my filter driver is properly installed but it is connected with another machine and not able to communicate with each other.

Besides changing netcfgInstanceId in INF file you also have to change it in common.h and rebuild the driver from the source code. Have you rebuilt the driver?

And again, your manipulations with Characteristics value are incorrect.

[Vadim Smirnov]

Vikash,

Could you describe all the steps you did to customize and install the driver? The more complete details the better, I can’t make a guess from your short description.

[Vadim Smirnov]

@vikashm05 wrote:

1)How generate new GUID .

You can use guidgen utility to generate new GUID.

@vikashm05 wrote:

2)How to change it in winpk filter after generating a new GUID :

Change INF file and string in common.h. Then just rebuild LWF drivers.

[Vadim Smirnov]

Windows Packet Filter Kit 3.1 released:
– LWF driver updated according Windows 8 requirements
– Added VLAN tagging 802.1Q
– Added IPv6 support for built-in filters

Bug fixes:
– Incorrect spinlock acquire in LWF driver
– Adapter list changed event in LWF driver

If you are eligible for a free update, please send the following details to [email protected] tо receive an update instruction:

1) Your order ID.
2) An approximate date of purchasing.

[Vadim Smirnov]

Thanks for reporting this. However, this is a known issue and it was fixed in version 3.1

[Vadim Smirnov]

You should use 0x40000 for LWF driver for system to install and start driver properly.

To eliminate compatibility issue with original standard WinpkFilter LWF you have to generate new GUID and replace it in both

NetCfgInstanceId present in my INF file is NetCfgInstanceId=”{5cbf81bd-5055-47cd-9055-a76b2b4e3697}”

and

#define FILTER_UNIQUE_NAME L”{5cbf81bd-5055-47cd-9055-a76b2b4e3697}” //unique name, quid name

Then rebuild LWF driver.

[Author]

Posts