Hi all,
I seem to have a problem with my NDIS intermediate driver.
When I receive an OID_GEN_CURRENT_PACKET_FILTER request,
I pass the filter down to the underlying miniport(s). Everything seems
to be fine with this except when promiscuous mode is set in the filter.
At that point, any packets indicated up to me by the underlying
miniport driver are not received. I know that the underlying miniport
is operating properly in promiscuous mode. It almost seems as
if NDIS is refusing to deliver received data to my intermediate driver if
promiscuous mode is enabled.
Has anyone seen anything like this? Any suspicions about what
the problem might be?
Thanks for your help
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
Hi Peter,
Are you just passing through the request of OID_GEN_CURRENT_PACKET_FILTER
from the protocol without modification ? is NDIS_PACKET_TYPE_PROMISCUOUS
set?
Rod.
-----Original Message-----
From: Peter Craft [mailto:xxxxx@alacritech.com]
Sent: Sunday, 21 January 2001 12:37 pm
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver and promiscuous mode
Hi all,
I seem to have a problem with my NDIS intermediate driver.
When I receive an OID_GEN_CURRENT_PACKET_FILTER request,
I pass the filter down to the underlying miniport(s). Everything seems
to be fine with this except when promiscuous mode is set in the filter.
At that point, any packets indicated up to me by the underlying
miniport driver are not received. I know that the underlying miniport
is operating properly in promiscuous mode. It almost seems as
if NDIS is refusing to deliver received data to my intermediate driver if
promiscuous mode is enabled.
Has anyone seen anything like this? Any suspicions about what
the problem might be?
Thanks for your help
You are currently subscribed to ntdev as: xxxxx@mobilesoft.com.au
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
Yes. Yes.
Note, this occurs when the segment counters are monitored with the
performance monitor. Once the counters are removed I get
an OID_GEN_CURRENT_PACKET_FILTER without
NDIS_PACKET_TYPE_PROMISCUOUS set. When I pass that
down to the underlying miniport everything starts working again. Strange.
I forget to mention in my original email - this is on NT4.
Any idea?
----- Original Message -----
From: Rodney Sigmund
To: NT Developers Interest List
Sent: Monday, January 22, 2001 3:33 PM
Subject: [ntdev] RE: NDIS intermediate driver and promiscuous mode
Hi Peter,
Are you just passing through the request of OID_GEN_CURRENT_PACKET_FILTER from the protocol without modification ? is NDIS_PACKET_TYPE_PROMISCUOUS set?
Rod.
-----Original Message-----
From: Peter Craft [mailto:xxxxx@alacritech.com]
Sent: Sunday, 21 January 2001 12:37 pm
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver and promiscuous mode
Hi all,
I seem to have a problem with my NDIS intermediate driver.
When I receive an OID_GEN_CURRENT_PACKET_FILTER request,
I pass the filter down to the underlying miniport(s). Everything seems
to be fine with this except when promiscuous mode is set in the filter.
At that point, any packets indicated up to me by the underlying
miniport driver are not received. I know that the underlying miniport
is operating properly in promiscuous mode. It almost seems as
if NDIS is refusing to deliver received data to my intermediate driver if
promiscuous mode is enabled.
Has anyone seen anything like this? Any suspicions about what
the problem might be?
Thanks for your help
You are currently subscribed to ntdev as: xxxxx@mobilesoft.com.au
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@alacritech.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
Hi Peter,
So you are saying you receive one OID_GEN_CURRENT_PACKET_FILTER without
NDIS_PACKET_TYPE_PROMISCUOUS set, when monitoring segment counters - then no
receives. Then removing the monitoring of segment counters you get antoher
OID_GEN_CURRENT_PACKET_FILTER without NDIS_PACKET_TYPE_PROMISCUOUS set and
you recieve indication from the miniport driver? if I understand you right,
then the only thing I can think of, is perhaps some other packet type field
is set in the filter, mudding the water.
Rod.
-----Original Message-----
From: Peter Craft [mailto:xxxxx@alacritech.com]
Sent: Tuesday, 23 January 2001 10:56 am
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS intermediate driver and promiscuous mode
Yes. Yes.
Note, this occurs when the segment counters are monitored with the
performance monitor. Once the counters are removed I get
an OID_GEN_CURRENT_PACKET_FILTER without
NDIS_PACKET_TYPE_PROMISCUOUS set. When I pass that
down to the underlying miniport everything starts working again. Strange.
I forget to mention in my original email - this is on NT4.
Any idea?
----- Original Message -----
From: Rodney Sigmund mailto:xxxxx
To: NT Developers mailto:xxxxx Interest List
Sent: Monday, January 22, 2001 3:33 PM
Subject: [ntdev] RE: NDIS intermediate driver and promiscuous mode
Hi Peter,
Are you just passing through the request of OID_GEN_CURRENT_PACKET_FILTER
from the protocol without modification ? is NDIS_PACKET_TYPE_PROMISCUOUS
set?
Rod.
-----Original Message-----
From: Peter Craft [mailto:xxxxx@alacritech.com
mailto:xxxxx]
Sent: Sunday, 21 January 2001 12:37 pm
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver and promiscuous mode
Hi all,
I seem to have a problem with my NDIS intermediate driver.
When I receive an OID_GEN_CURRENT_PACKET_FILTER request,
I pass the filter down to the underlying miniport(s). Everything seems
to be fine with this except when promiscuous mode is set in the filter.
At that point, any packets indicated up to me by the underlying
miniport driver are not received. I know that the underlying miniport
is operating properly in promiscuous mode. It almost seems as
if NDIS is refusing to deliver received data to my intermediate driver if
promiscuous mode is enabled.
Has anyone seen anything like this? Any suspicions about what
the problem might be?
Thanks for your help
—
You are currently subscribed to ntdev as: xxxxx@mobilesoft.com.au
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@alacritech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@mobilesoft.com.au
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</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>