hi all,
I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0. After
reading the existing MUX code, I have a doubt.
Do we require the notify object DLL at all? As far as my understanding goes
the DLL does the following:
So we may as well skip it, if:
Regards,
AP
Look carefully at what the NO does. I believe that it also prevents
protocols such as TCP/IP from binding to the real NIC miniports in addition
to the functions you have noted. You wouldn’t want TCP/IP bound to your
virtual NICs and the real NICs at the same time.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 9:17 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] notify object
hi all,
I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0. After
reading the existing MUX code, I have a doubt.
Do we require the notify object DLL at all? As far as my understanding goes
the DLL does the following:
dynamically catch new adapters added to the system.
provides the GUI in the driver.
So we may as well skip it, if:
we want to add our own GUI.
we want to skip dynamic configurations.
Regards,
AP
— 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
do u mean, it constantly prevents, or it does it once when an adapter is
created. If so then any user mode app can do that while setting up MVLAN
configs. I didn’t see it constantly keeping track. I could tick the tcpip
bindings on the real adapter back to enabled.
is my understanding wrong?
AP
On 9/11/07, Thomas F. Divine wrote:
>
> Look carefully at what the NO does. I believe that it also prevents
> protocols such as TCP/IP from binding to the real NIC miniports in addition
> to the functions you have noted. You wouldn’t want TCP/IP bound to your
> virtual NICs and the real NICs at the same time.
>
>
>
> Thomas F. Divine
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 9:17 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] notify object
>
>
>
> hi all,
>
>
>
> I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0.
> After reading the existing MUX code, I have a doubt.
>
>
>
> Do we require the notify object DLL at all? As far as my understanding
> goes the DLL does the following:
>
>
>
> 1. dynamically catch new adapters added to the system.
>
> 2. provides the GUI in the driver.
>
>
>
>
>
> So we may as well skip it, if:
>
>
>
> 1. we want to add our own GUI.
>
> 2. we want to skip dynamic configurations.
>
>
>
>
>
>
>
> Regards,
>
>
>
> AP
>
> — 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
>
Search for DISABLE_PROTOCOLS_TO_PHYSICAL in notify.cpp
Thomas
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 12:09 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
do u mean, it constantly prevents, or it does it once when an adapter is
created. If so then any user mode app can do that while setting up MVLAN
configs. I didn’t see it constantly keeping track. I could tick the tcpip
bindings on the real adapter back to enabled.
is my understanding wrong?
AP
On 9/11/07, Thomas F. Divine wrote:
Look carefully at what the NO does. I believe that it also prevents
protocols such as TCP/IP from binding to the real NIC miniports in addition
to the functions you have noted. You wouldn’t want TCP/IP bound to your
virtual NICs _ and_ the real NICs at the same time.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 9:17 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] notify object
hi all,
I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0. After
reading the existing MUX code, I have a doubt.
Do we require the notify object DLL at all? As far as my understanding goes
the DLL does the following:
1. dynamically catch new adapters added to the system.
2. provides the GUI in the driver.
So we may as well skip it, if:
1. we want to add our own GUI.
2. we want to skip dynamic configurations.
Regards,
AP
— 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
in the implementation of LBFO, wher there are two adapters in the team, say
A and B, i need to create a third adapter C for the bundle through the IMD.
Which MAC address do I use in the virtual adapter?
On 9/11/07, Thomas F. Divine wrote:
>
> Search for DISABLE_PROTOCOLS_TO_PHYSICAL in notify.cpp
>
>
>
> Thomas
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 12:09 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] notify object
>
>
>
> do u mean, it constantly prevents, or it does it once when an adapter is
> created. If so then any user mode app can do that while setting up MVLAN
> configs. I didn’t see it constantly keeping track. I could tick the tcpip
> bindings on the real adapter back to enabled.
>
>
>
> is my understanding wrong?
>
>
>
>
>
> AP
>
>
>
> On 9/11/07, Thomas F. Divine wrote:
>
> Look carefully at what the NO does. I believe that it also prevents
> protocols such as TCP/IP from binding to the real NIC miniports in addition
> to the functions you have noted. You wouldn’t want TCP/IP bound to your
> virtual NICs _ and_ the real NICs at the same time.
>
>
>
> Thomas F. Divine
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 9:17 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] notify object
>
>
>
> hi all,
>
>
>
> I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0.
> After reading the existing MUX code, I have a doubt.
>
>
>
> Do we require the notify object DLL at all? As far as my understanding
> goes the DLL does the following:
>
>
>
> 1. dynamically catch new adapters added to the system.
>
> 2. provides the GUI in the driver.
>
>
>
>
>
> So we may as well skip it, if:
>
>
>
> 1. we want to add our own GUI.
>
> 2. we want to skip dynamic configurations.
>
>
>
>
>
>
>
> Regards,
>
>
>
> AP
>
> — 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
>
It doesn’t really matter, does it?
Just pick lower-level NIC miniport one and call it “Primary”. The “Primary”
could simply be the first adapter that you happen to bind to; however, to
preserve ARP tables on other machines and routers it might be better to
try to preserve the virtual NIC MAC address across reboots, etc.
Adopt your choice of “Primary” adapter MAC address for the one virtual
miniport and use it forever. Call all other bindings “Secondary”.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 2:29 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
in the implementation of LBFO, wher there are two adapters in the team, say
A and B, i need to create a third adapter C for the bundle through the IMD.
Which MAC address do I use in the virtual adapter?
On 9/11/07, Thomas F. Divine wrote:
Search for DISABLE_PROTOCOLS_TO_PHYSICAL in notify.cpp
Thomas
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 12:09 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
do u mean, it constantly prevents, or it does it once when an adapter is
created. If so then any user mode app can do that while setting up MVLAN
configs. I didn’t see it constantly keeping track. I could tick the tcpip
bindings on the real adapter back to enabled.
is my understanding wrong?
AP
On 9/11/07, Thomas F. Divine wrote:
Look carefully at what the NO does. I believe that it also prevents
protocols such as TCP/IP from binding to the real NIC miniports in addition
to the functions you have noted. You wouldn’t want TCP/IP bound to your
virtual NICs _ and_ the real NICs at the same time.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 9:17 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] notify object
hi all,
I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0. After
reading the existing MUX code, I have a doubt.
Do we require the notify object DLL at all? As far as my understanding goes
the DLL does the following:
1. dynamically catch new adapters added to the system.
2. provides the GUI in the driver.
So we may as well skip it, if:
1. we want to add our own GUI.
2. we want to skip dynamic configurations.
Regards,
AP
— 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
— 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
but since the virtual adapter will be the only one to be bound to the
protocols, will will be able to support WOL and wake of magic packets?
also how do i handle statistics OIDS for the adapters in the team?
On 9/12/07, Thomas F. Divine wrote:
>
> It doesn’t really matter, does it?
>
>
>
> Just pick lower-level NIC miniport one and call it “Primary”. The
> “Primary” could simply be the first adapter that you happen to bind to;
> however, to preserve ARP tables on other machines and routers it might be
> better to try to preserve the virtual NIC MAC address across reboots,
> etc.
>
>
>
> Adopt your choice of “Primary” adapter MAC address for the one virtual
> miniport and use it forever. Call all other bindings “Secondary”.
>
>
>
> Thomas F. Divine
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 2:29 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] notify object
>
>
>
> in the implementation of LBFO, wher there are two adapters in the team,
> say A and B, i need to create a third adapter C for the bundle through the
> IMD. Which MAC address do I use in the virtual adapter?
>
>
>
>
>
>
>
> On 9/11/07, Thomas F. Divine wrote:
>
> Search for DISABLE_PROTOCOLS_TO_PHYSICAL in notify.cpp
>
>
>
> Thomas
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 12:09 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] notify object
>
>
>
> do u mean, it constantly prevents, or it does it once when an adapter is
> created. If so then any user mode app can do that while setting up MVLAN
> configs. I didn’t see it constantly keeping track. I could tick the tcpip
> bindings on the real adapter back to enabled.
>
>
>
> is my understanding wrong?
>
>
>
>
>
> AP
>
>
>
> On 9/11/07, Thomas F. Divine wrote:
>
> Look carefully at what the NO does. I believe that it also prevents
> protocols such as TCP/IP from binding to the real NIC miniports in addition
> to the functions you have noted. You wouldn’t want TCP/IP bound to your
> virtual NICs _ and_ the real NICs at the same time.
>
>
>
> Thomas F. Divine
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 9:17 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] notify object
>
>
>
> hi all,
>
>
>
> I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0.
> After reading the existing MUX code, I have a doubt.
>
>
>
> Do we require the notify object DLL at all? As far as my understanding
> goes the DLL does the following:
>
>
>
> 1. dynamically catch new adapters added to the system.
>
> 2. provides the GUI in the driver.
>
>
>
>
>
> So we may as well skip it, if:
>
>
>
> 1. we want to add our own GUI.
>
> 2. we want to skip dynamic configurations.
>
>
>
>
>
>
>
> Regards,
>
>
>
> AP
>
> — 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
>
>
> — 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
>
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 3:41 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
but since the virtual adapter will be the only one to be bound to the
protocols, will will be able to support WOL and wake of magic packets?
[PCAUSA] Actually, I haven’t thought about that too much.
Probably all that is necessary is to route the related OIDs to the NIC
miniports. They do the wakeup.
also how do i handle statistics OIDS for the adapters in the team?
[PCAUSA] Most likely you would simply keep statistics yourself. Answer the
queries from your own virtual miniport’s statistics table instead of passing
the query down to the lower-level NICs.
Thomas F. Divine
On 9/12/07, Thomas F. Divine wrote:
It doesn’t really matter, does it?
Just pick lower-level NIC miniport one and call it “Primary”. The “Primary”
could simply be the first adapter that you happen to bind to; however, to
preserve ARP tables on other machines and routers it might be better to
try to preserve the virtual NIC MAC address across reboots, etc.
Adopt your choice of “Primary” adapter MAC address for the one virtual
miniport and use it forever. Call all other bindings “Secondary”.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 2:29 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
in the implementation of LBFO, wher there are two adapters in the team, say
A and B, i need to create a third adapter C for the bundle through the IMD.
Which MAC address do I use in the virtual adapter?
On 9/11/07, Thomas F. Divine wrote:
Search for DISABLE_PROTOCOLS_TO_PHYSICAL in notify.cpp
Thomas
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 12:09 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
do u mean, it constantly prevents, or it does it once when an adapter is
created. If so then any user mode app can do that while setting up MVLAN
configs. I didn’t see it constantly keeping track. I could tick the tcpip
bindings on the real adapter back to enabled.
is my understanding wrong?
AP
On 9/11/07, Thomas F. Divine wrote:
Look carefully at what the NO does. I believe that it also prevents
protocols such as TCP/IP from binding to the real NIC miniports in addition
to the functions you have noted. You wouldn’t want TCP/IP bound to your
virtual NICs _ and_ the real NICs at the same time.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 9:17 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] notify object
hi all,
I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0. After
reading the existing MUX code, I have a doubt.
Do we require the notify object DLL at all? As far as my understanding goes
the DLL does the following:
1. dynamically catch new adapters added to the system.
2. provides the GUI in the driver.
So we may as well skip it, if:
1. we want to add our own GUI.
2. we want to skip dynamic configurations.
Regards,
AP
— 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
— 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
thanks thomas.
is it possible that an IMD be installed for only a set of adapters leaving
the others? i dnt mean binding and unbinding, but that the imd should
totally not be present in the stack of some adapters?
ap
On 9/12/07, Thomas F. Divine wrote:
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 3:41 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] notify object
>
>
>
> but since the virtual adapter will be the only one to be bound to the
> protocols, will will be able to support WOL and wake of magic packets?
>
> [PCAUSA] Actually, I haven’t thought about that too much.
>
> * *
>
> Probably all that is necessary is to route the related OIDs to the NIC
> miniports. They do the wakeup?
>
>
>
> also how do i handle statistics OIDS for the adapters in the team?
>
> [PCAUSA] Most likely you would simply keep statistics yourself. Answer
> the queries from your own virtual miniport’s statistics table instead of
> passing the query down to the lower-level NICs.
>
> * *
>
> Thomas F. Divine
>
>
>
>
> On 9/12/07, Thomas F. Divine wrote:
>
> It doesn’t really matter, does it?
>
>
>
> Just pick lower-level NIC miniport one and call it “Primary”. The
> “Primary” could simply be the first adapter that you happen to bind to;
> however, to preserve ARP tables on other machines and routers it might be
> better to _ try_ to preserve the virtual NIC MAC address across reboots,
> etc.
>
>
>
> Adopt your choice of “Primary” adapter MAC address for the one virtual
> miniport and use it forever. Call all other bindings “Secondary”.
>
>
>
> Thomas F. Divine
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 2:29 PM
>
>
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] notify object
>
>
>
> in the implementation of LBFO, wher there are two adapters in the team,
> say A and B, i need to create a third adapter C for the bundle through the
> IMD. Which MAC address do I use in the virtual adapter?
>
>
>
>
>
>
>
> On 9/11/07, Thomas F. Divine wrote:
>
> Search for DISABLE_PROTOCOLS_TO_PHYSICAL in notify.cpp
>
>
>
> Thomas
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 12:09 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] notify object
>
>
>
> do u mean, it constantly prevents, or it does it once when an adapter is
> created. If so then any user mode app can do that while setting up MVLAN
> configs. I didn’t see it constantly keeping track. I could tick the tcpip
> bindings on the real adapter back to enabled.
>
>
>
> is my understanding wrong?
>
>
>
>
>
> AP
>
>
>
> On 9/11/07, Thomas F. Divine wrote:
>
> Look carefully at what the NO does. I believe that it also prevents
> protocols such as TCP/IP from binding to the real NIC miniports in addition
> to the functions you have noted. You wouldn’t want TCP/IP bound to your
> virtual NICs _ and_ the real NICs at the same time.
>
>
>
> Thomas F. Divine
>
>
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, September 11, 2007 9:17 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] notify object
>
>
>
> hi all,
>
>
>
> I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0.
> After reading the existing MUX code, I have a doubt.
>
>
>
> Do we require the notify object DLL at all? As far as my understanding
> goes the DLL does the following:
>
>
>
> 1. dynamically catch new adapters added to the system.
>
> 2. provides the GUI in the driver.
>
>
>
>
>
> So we may as well skip it, if:
>
>
>
> 1. we want to add our own GUI.
>
> 2. we want to skip dynamic configurations.
>
>
>
>
>
>
>
> Regards,
>
>
>
> AP
>
> — 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
>
>
> — 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
>
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Wednesday, September 12, 2007 5:40 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
thanks thomas.
is it possible that an IMD be installed for only a set of adapters leaving
the others? i dnt mean binding and unbinding, but that the imd should
totally not be present in the stack of some adapters?
[PCAUSA] Surely.
1.) Use the Network Control Panel to Uncheck the IM driver from unwanted
miniports.
2.) Use the WDK BindView sample application to do the same.
3.) Create a BindView-Like application to do the same.
4.) Use you IM driver’s NotifyObject to veto binding on unwanted
adapters.
The hard part, IMHO, is coming up with logic to decide which binding are
wanted, which are not.
It is relatively easy for a NO to select adapters by information that is in
the adapter’s INF file. For example, if you only want to bind to adapters
with a specific PnP VID/PID, then that is easy.
Other logic might be difficult or impossible without user input of some
sort.
Good luck,
Thomas F. Divine
ap
On 9/12/07, Thomas F. Divine wrote:
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 3:41 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
but since the virtual adapter will be the only one to be bound to the
protocols, will will be able to support WOL and wake of magic packets?
[PCAUSA] Actually, I haven’t thought about that too much.
Probably all that is necessary is to route the related OIDs to the NIC
miniports. They do the wakeup.
also how do i handle statistics OIDS for the adapters in the team?
[PCAUSA] Most likely you would simply keep statistics yourself. Answer the
queries from your own virtual miniport’s statistics table instead of passing
the query down to the lower-level NICs.
Thomas F. Divine
On 9/12/07, Thomas F. Divine wrote:
It doesn’t really matter, does it?
Just pick lower-level NIC miniport one and call it “Primary”. The “Primary”
could simply be the first adapter that you happen to bind to; however, to
preserve ARP tables on other machines and routers it might be better to
try to preserve the virtual NIC MAC address across reboots, etc.
Adopt your choice of “Primary” adapter MAC address for the one virtual
miniport and use it forever. Call all other bindings “Secondary”.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 2:29 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
in the implementation of LBFO, wher there are two adapters in the team, say
A and B, i need to create a third adapter C for the bundle through the IMD.
Which MAC address do I use in the virtual adapter?
On 9/11/07, Thomas F. Divine wrote:
Search for DISABLE_PROTOCOLS_TO_PHYSICAL in notify.cpp
Thomas
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 12:09 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] notify object
do u mean, it constantly prevents, or it does it once when an adapter is
created. If so then any user mode app can do that while setting up MVLAN
configs. I didn’t see it constantly keeping track. I could tick the tcpip
bindings on the real adapter back to enabled.
is my understanding wrong?
AP
On 9/11/07, Thomas F. Divine wrote:
Look carefully at what the NO does. I believe that it also prevents
protocols such as TCP/IP from binding to the real NIC miniports in addition
to the functions you have noted. You wouldn’t want TCP/IP bound to your
virtual NICs _ and_ the real NICs at the same time.
Thomas F. Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, September 11, 2007 9:17 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] notify object
hi all,
I am planning to implement LBFO logic in an IMD for NDIS 5.x and 6.0. After
reading the existing MUX code, I have a doubt.
Do we require the notify object DLL at all? As far as my understanding goes
the DLL does the following:
1. dynamically catch new adapters added to the system.
2. provides the GUI in the driver.
So we may as well skip it, if:
1. we want to add our own GUI.
2. we want to skip dynamic configurations.
Regards,
AP
— 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
— 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
— 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