NDIS IM and TDI filter in one driver image

NTDEV
1

Hi all,

what I want to do is to hook the TCIP stack from the top(by attaching to
device created by TCPIP driver, suppporting TDI) and down (by an NDIS
Intermediate driver).

I would prefer to do it all in one driver. Do you have any experince with
it?

Which points should I be carefull about??

Are there any better solutions to hook the TCPIP stack completely?? (I am
also interested about the processes, which make network IO)

thanks in advance

regards Johnny

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Johnny,

Since I’ve attached to the TCP/IP devices I’m aware of at least one gotcha.
Some of the IRPs sent down don’t have enough IRP stack entries. In those
instances, if you consume one of the stack entries you get a blue screen in
a lower driver. The way I got around the problem was to repackage the
original IRP in a new IRP with sufficient stack entries before calling
IoCallDriver. When the replacement IRP completed, I completed the original
IRP.

I assume one or more bits of code above me are assuming the depth of the
TCP/IP device stack. I never bothered to figure out exactly who. I just
needed my code to work. It’s been a while but the offending IRPs could very
well have been for undocumented IOCTLs but I’m not positive.

Hope this saves you some time.

Aaron Stavens
NetMotion Wireless, Inc.

-----Original Message-----
From: Johnny Habibi [mailto:xxxxx@yahoo.de]
Sent: Thursday, August 16, 2001 2:44 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS IM and TDI filter in one driver image

Hi all,

what I want to do is to hook the TCIP stack from the top(by attaching to
device created by TCPIP driver, suppporting TDI) and down (by an NDIS
Intermediate driver).

I would prefer to do it all in one driver. Do you have any experince with
it?

Which points should I be carefull about??

Are there any better solutions to hook the TCPIP stack completely?? (I am
also interested about the processes, which make network IO)

thanks in advance

regards Johnny

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com

You are currently subscribed to ntdev as: xxxxx@nmwco.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Aaron Stavens,

I think this is b’cause of system’s NETBT driver which creates a problem
of stack size. I had same experience while writing a TDI filter driver.
One has to change load order of their driver(service)before NETBT.

Thanks,
Sunil

-----Original Message-----
From: Aaron Stavens [mailto:xxxxx@nmwco.com]
Sent: Friday, August 17, 2001 10:06 AM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS IM and TDI filter in one driver image

Johnny,

Since I’ve attached to the TCP/IP devices I’m aware of at least one
gotcha.
Some of the IRPs sent down don’t have enough IRP stack entries. In those
instances, if you consume one of the stack entries you get a blue screen
in
a lower driver. The way I got around the problem was to repackage the
original IRP in a new IRP with sufficient stack entries before calling
IoCallDriver. When the replacement IRP completed, I completed the
original
IRP.

I assume one or more bits of code above me are assuming the depth of the
TCP/IP device stack. I never bothered to figure out exactly who. I just
needed my code to work. It’s been a while but the offending IRPs could
very
well have been for undocumented IOCTLs but I’m not positive.

Hope this saves you some time.

Aaron Stavens
NetMotion Wireless, Inc.

-----Original Message-----
From: Johnny Habibi [mailto:xxxxx@yahoo.de]
Sent: Thursday, August 16, 2001 2:44 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS IM and TDI filter in one driver image

Hi all,

what I want to do is to hook the TCIP stack from the top(by attaching to
device created by TCPIP driver, suppporting TDI) and down (by an NDIS
Intermediate driver).

I would prefer to do it all in one driver. Do you have any experince
with
it?

Which points should I be carefull about??

Are there any better solutions to hook the TCPIP stack completely?? (I
am
also interested about the processes, which make network IO)

thanks in advance

regards Johnny

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com

You are currently subscribed to ntdev as: xxxxx@nmwco.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@greenborder.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

Thanks Aaron for your help

regards johnny

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Aaron Stavens
Sent: Friday, August 17, 2001 7:06 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS IM and TDI filter in one driver image

Johnny,

Since I’ve attached to the TCP/IP devices I’m aware of at least one gotcha.
Some of the IRPs sent down don’t have enough IRP stack entries. In those
instances, if you consume one of the stack entries you get a blue screen in
a lower driver. The way I got around the problem was to repackage the
original IRP in a new IRP with sufficient stack entries before calling
IoCallDriver. When the replacement IRP completed, I completed the original
IRP.

I assume one or more bits of code above me are assuming the depth of the
TCP/IP device stack. I never bothered to figure out exactly who. I just
needed my code to work. It’s been a while but the offending IRPs could very
well have been for undocumented IOCTLs but I’m not positive.

Hope this saves you some time.

Aaron Stavens
NetMotion Wireless, Inc.

-----Original Message-----
From: Johnny Habibi [mailto:xxxxx@yahoo.de]
Sent: Thursday, August 16, 2001 2:44 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS IM and TDI filter in one driver image

Hi all,

what I want to do is to hook the TCIP stack from the top(by attaching to
device created by TCPIP driver, suppporting TDI) and down (by an NDIS
Intermediate driver).

I would prefer to do it all in one driver. Do you have any experince with
it?

Which points should I be carefull about??

Are there any better solutions to hook the TCPIP stack completely?? (I am
also interested about the processes, which make network IO)

thanks in advance

regards Johnny

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com

You are currently subscribed to ntdev as: xxxxx@nmwco.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: xxxxx@yahoo.de
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com