Hi, after installing a bunch of virtual miniport devices (through
devcon), I would like to keep the devices in a Paused state or some
state that would prevent protocols from binding above and a large
stream of ARP pkts from flowing out which I usually see right after
installation. I am finding that returning Pending from the Pause
handler isn’t helping since it’s blocking installation of the devices
on the devcon side. Is there a way to achieve something along the
lines of keeping all the interfaces in a state that roughly maps to
NET_IF_OPER_STATUS_DOWN until I send down an IOCTL on a separate
device exposed by the driver that signals everything is in a ready
state and data transmission can begin?
From: Puchu Pachok
Sent: 10/31/2012 8:57 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] keeping a NDIS miniport in a Paused/Down state for a while after intallation without blocking PNP
Hi, after installing a bunch of virtual miniport devices (through
devcon), I would like to keep the devices in a Paused state or some
state that would prevent protocols from binding above and a large
stream of ARP pkts from flowing out which I usually see right after
installation. I am finding that returning Pending from the Pause
handler isn’t helping since it’s blocking installation of the devices
on the devcon side. Is there a way to achieve something along the
lines of keeping all the interfaces in a state that roughly maps to
NET_IF_OPER_STATUS_DOWN until I send down an IOCTL on a separate
device exposed by the driver that signals everything is in a ready
state and data transmission can begin?
Great … that’s exactly what I was trying out! Bring up the
interfaces as MediaConnectStateDisconnected and then when things are
ready, NdisMIndicateStatusEx a NDIS_STATUS_LINK_STATE.
Thanks!
On Wed, Oct 31, 2012 at 9:03 PM, Doron Holan wrote: > Can you report media disconnected? > > d > > debt from my phone > ________________________________ > From: Puchu Pachok > Sent: 10/31/2012 8:57 PM > To: Windows System Software Devs Interest List > Subject: [ntdev] keeping a NDIS miniport in a Paused/Down state for a while > after intallation without blocking PNP > > Hi, after installing a bunch of virtual miniport devices (through > devcon), I would like to keep the devices in a Paused state or some > state that would prevent protocols from binding above and a large > stream of ARP pkts from flowing out which I usually see right after > installation. I am finding that returning Pending from the Pause > handler isn’t helping since it’s blocking installation of the devices > on the devcon side. Is there a way to achieve something along the > lines of keeping all the interfaces in a state that roughly maps to > NET_IF_OPER_STATUS_DOWN until I send down an IOCTL on a separate > device exposed by the driver that signals everything is in a ready > state and data transmission can begin? > > Thanks! > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer
I am not an ndis expert at all, my suggestion was a mere shot in the dark in terms of trying to reflect your state with what little I know about ndis. Hope it works.
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Puchu Pachok
Sent: Wednesday, October 31, 2012 9:57 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] keeping a NDIS miniport in a Paused/Down state for a while after intallation without blocking PNP
Great … that’s exactly what I was trying out! Bring up the interfaces as MediaConnectStateDisconnected and then when things are ready, NdisMIndicateStatusEx a NDIS_STATUS_LINK_STATE.
Thanks!
On Wed, Oct 31, 2012 at 9:03 PM, Doron Holan wrote: > Can you report media disconnected? > > d > > debt from my phone > ________________________________ > From: Puchu Pachok > Sent: 10/31/2012 8:57 PM > To: Windows System Software Devs Interest List > Subject: [ntdev] keeping a NDIS miniport in a Paused/Down state for a > while after intallation without blocking PNP > > Hi, after installing a bunch of virtual miniport devices (through > devcon), I would like to keep the devices in a Paused state or some > state that would prevent protocols from binding above and a large > stream of ARP pkts from flowing out which I usually see right after > installation. I am finding that returning Pending from the Pause > handler isn’t helping since it’s blocking installation of the devices > on the devcon side. Is there a way to achieve something along the > lines of keeping all the interfaces in a state that roughly maps to > NET_IF_OPER_STATUS_DOWN until I send down an IOCTL on a separate > device exposed by the driver that signals everything is in a ready > state and data transmission can begin? > > Thanks! > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer
So the steps mentioned below seems to work out pretty well. NDIS pros,
let me know if there is something that is not recommended about the
approach:
Bring up the interfaces as MediaConnectStateDisconnected and then when
things are ready, NdisMIndicateStatusEx a NDIS_STATUS_LINK_STATE
On Wed, Oct 31, 2012 at 10:22 PM, Doron Holan wrote: > I am not an ndis expert at all, my suggestion was a mere shot in the dark in terms of trying to reflect your state with what little I know about ndis. Hope it works. > > d > > -----Original Message----- > From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Puchu Pachok > Sent: Wednesday, October 31, 2012 9:57 PM > To: Windows System Software Devs Interest List > Subject: Re: [ntdev] keeping a NDIS miniport in a Paused/Down state for a while after intallation without blocking PNP > > Great … that’s exactly what I was trying out! Bring up the interfaces as MediaConnectStateDisconnected and then when things are ready, NdisMIndicateStatusEx a NDIS_STATUS_LINK_STATE. > > Thanks! > > On Wed, Oct 31, 2012 at 9:03 PM, Doron Holan wrote: >> Can you report media disconnected? >> >> d >> >> debt from my phone >> ________________________________ >> From: Puchu Pachok >> Sent: 10/31/2012 8:57 PM >> To: Windows System Software Devs Interest List >> Subject: [ntdev] keeping a NDIS miniport in a Paused/Down state for a >> while after intallation without blocking PNP >> >> Hi, after installing a bunch of virtual miniport devices (through >> devcon), I would like to keep the devices in a Paused state or some >> state that would prevent protocols from binding above and a large >> stream of ARP pkts from flowing out which I usually see right after >> installation. I am finding that returning Pending from the Pause >> handler isn’t helping since it’s blocking installation of the devices >> on the devcon side. Is there a way to achieve something along the >> lines of keeping all the interfaces in a state that roughly maps to >> NET_IF_OPER_STATUS_DOWN until I send down an IOCTL on a separate >> device exposed by the driver that signals everything is in a ready >> state and data transmission can begin? >> >> Thanks! >> >> — >> NTDEV is sponsored by OSR >> >> For our schedule of WDF, WDM, debugging and other seminars visit: >> http://www.osr.com/seminars >> >> To unsubscribe, visit the List Server section of OSR Online at >> http://www.osronline.com/page.cfm?name=ListServer >> >> — >> NTDEV is sponsored by OSR >> >> For our schedule of WDF, WDM, debugging and other seminars visit: >> http://www.osr.com/seminars >> >> To unsubscribe, visit the List Server section of OSR Online at >> http://www.osronline.com/page.cfm?name=ListServer > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Just indicate medium state as disconnected and nobody will bother you
with sends.
– pa
On 01-Nov-2012 05:57, Puchu Pachok wrote:
Hi, after installing a bunch of virtual miniport devices (through
devcon), I would like to keep the devices in a Paused state or some
state that would prevent protocols from binding above and a large
stream of ARP pkts from flowing out which I usually see right after
installation. I am finding that returning Pending from the Pause
handler isn’t helping since it’s blocking installation of the devices
on the devcon side. Is there a way to achieve something along the
lines of keeping all the interfaces in a state that roughly maps to
NET_IF_OPER_STATUS_DOWN until I send down an IOCTL on a separate
device exposed by the driver that signals everything is in a ready
state and data transmission can begin?
I remembered in ndistest, they asks you to connect the cable, and then
the script will be waitng for link up indication. If no indication within
some seconds, the test will fail. Do they still have this test?
On Thu, Nov 1, 2012 at 7:00 AM, Pavel A wrote:
> Just indicate medium state as disconnected and nobody will bother you with > sends. > – pa > > > On 01-Nov-2012 05:57, Puchu Pachok wrote: > >> Hi, after installing a bunch of virtual miniport devices (through >> devcon), I would like to keep the devices in a Paused state or some >> state that would prevent protocols from binding above and a large >> stream of ARP pkts from flowing out which I usually see right after >> installation. I am finding that returning Pending from the Pause >> handler isn’t helping since it’s blocking installation of the devices >> on the devcon side. Is there a way to achieve something along the >> lines of keeping all the interfaces in a state that roughly maps to >> NET_IF_OPER_STATUS_DOWN until I send down an IOCTL on a separate >> device exposed by the driver that signals everything is in a ready >> state and data transmission can begin? >> >> Thanks! >> >> > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.**cfm?name=ListServerhttp: ></http:>