Prev: DriverPackagePreinstall returns ERROR_ACCESS_DENIED
Next: System-wide Audio filter driver
From: Maxim S. Shatskih on 16 Apr 2010 05:05
>as far as i've investigated, it does NOT. :(

What I've said is from RFCs. Either pre-Vista IP is non-RFC-compliant, or you have overlooked something.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Vitalie Vrabie on 16 Apr 2010 06:20
On Apr 16, 12:05 pm, "Maxim S. Shatskih"
<ma...(a)storagecraft.com.no.spam> wrote:
> >as far as i've investigated, it does NOT. :(
>
> What I've said is from RFCs. Either pre-Vista IP is non-RFC-compliant, or you have overlooked something.

have you read mo other messages in this thread?
From: Pavel A. on 16 Apr 2010 08:20
NDIS can cache some OID queries, so your driver can see them only once.
--pa


"Vitalie Vrabie" <vitalie.vrabie(a)gmail.com> wrote in message
news:e2d5727e-30bc-472e-b5af-1dc3aee80a43(a)i37g2000yqn.googlegroups.com...
> On Apr 16, 12:05 pm, "Maxim S. Shatskih"
> <ma...(a)storagecraft.com.no.spam> wrote:
>> >as far as i've investigated, it does NOT. :(
>>
>> What I've said is from RFCs. Either pre-Vista IP is non-RFC-compliant, or
>> you have overlooked something.
>
> have you read mo other messages in this thread?

From: Vitalie Vrabie on 16 Apr 2010 08:31
On Apr 16, 1:20 pm, Vitalie Vrabie <vitalie.vra...(a)gmail.com> wrote:
> have you read mo other messages in this thread?

to sum up.
i found a tool called mturoute.exe that EXPERIMENTALLY figures out the
MTU on the path to a given host.
no tools found that can tell on xp what "netsh interface ipv4 show
subinterface" says on vista and up (a list of interfaces and the MTU
of each one).

anyway, mturoute told me what i wanted to know.
and indeed, the MTU of an ip interface on top of my IM is shorter than
the underlying miniport's exactly by the amount my IM chops off in
PtRequestComplete().

i am investigating a serious performance issue of the ip traffic on
top of my IM and the wrong MTU was a possible cause.
From: Pavel A. on 16 Apr 2010 08:47
Netsh on XP does not understand "ipv4" - only "ip" or "ipv6".
Win7 knows more tricks than XP, there is the progress ;)
And, IMs are known to cause bad performance, so on Vista+ better use LWFs or
WFP.

--pa

"Vitalie Vrabie" <vitalie.vrabie(a)gmail.com> wrote in message
news:06dee2f7-a5b1-4a47-b3bb-e6c5950e54ed(a)c36g2000yqm.googlegroups.com...
> On Apr 16, 1:20 pm, Vitalie Vrabie <vitalie.vra...(a)gmail.com> wrote:
>> have you read mo other messages in this thread?
>
> to sum up.
> i found a tool called mturoute.exe that EXPERIMENTALLY figures out the
> MTU on the path to a given host.
> no tools found that can tell on xp what "netsh interface ipv4 show
> subinterface" says on vista and up (a list of interfaces and the MTU
> of each one).
>
> anyway, mturoute told me what i wanted to know.
> and indeed, the MTU of an ip interface on top of my IM is shorter than
> the underlying miniport's exactly by the amount my IM chops off in
> PtRequestComplete().
>
> i am investigating a serious performance issue of the ip traffic on
> top of my IM and the wrong MTU was a possible cause.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: DriverPackagePreinstall returns ERROR_ACCESS_DENIED
Next: System-wide Audio filter driver