Hi
Could you help me finding out MUX based ndis IM driver which has 1 to N
interfaces.
The MUX driver comes with ddk supports n to 1 not 1 to n.
Daliraju
Software engineer
For limitations on the use and distribution of this message, please visit www.sbs.com/emaildisclaimer.
I can answer if you have any questions on 1:N driver since i have written
one. Though i won’t be able to share the source code as it belongs to my
company.
–
Pankaj Garg
This posting is provided “AS IS” with no warranties and confers no rights.
“Vysyaraju Daliraju” wrote in message
news:xxxxx@ntdev…
> Hi
> Could you help me finding out MUX based ndis IM driver which has 1 to N
> interfaces.
> The MUX driver comes with ddk supports n to 1 not 1 to n.
>
> Daliraju
> Software engineer
>
> For limitations on the use and distribution of this message, please visit
www.sbs.com/emaildisclaimer.
>
HI pankaj
Thanks for the help. If I modify the .inf files of mux driver, will it work
as 1 to n interfaces.
Daliraju
X-Message-Number: 15
X-lyris-Id: 77741
Date: Tue, 12 Jul 2005 16:57:55 -0700
From: “Pankaj Garg”
Subject: Re: Mux based ndis IM driver
I can answer if you have any questions on 1:N driver since i have written
one. Though i won’t be able to share the source code as it belongs to my
company.
–
Pankaj Garg
X-Message-Number: 14
X-lyris-Id: 77727
Date: Tue, 12 Jul 2005 10:58:01 -0600
From: Vysyaraju Daliraju
Subject: Mux based ndis IM driver
Hi
Could you help me finding out MUX based ndis IM driver which has 1 to N
interfaces.
The MUX driver comes with ddk supports n to 1 not 1 to n.
Daliraju
Software engineer
For limitations on the use and distribution of this message, please visit www.sbs.com/emaildisclaimer.
You don’t need to modify the INF files. You should modify the notify dll to
create (Install) a virtual adapter during the driver initialization (in
function CMuxNotify::Install) and not create any more virtual adapters when
the driver is bound to physical adapters. You shall also disable the
property sheet in the notify driver since you just want to create one
virtual adapter.
You will also have to modify the driver to store adapters information in 1:N
manner. Mainly you will have to change ADAPT and VELAN struct. In MUX
sample, one ADAPT can store list of VELAN, you will have to do the opposite.
Other changes depends on what you exactly want this driver to do. Like if
you are building a load balancing driver, then you can distribute the
network traffic coming from one Virtual adapter between N physical adapters
etc.
–
Pankaj Garg
This posting is provided “AS IS” with no warranties and confers no rights.
“Vysyaraju Daliraju” wrote in message
news:xxxxx@ntdev…
>
> HI pankaj
>
> Thanks for the help. If I modify the .inf files of mux driver, will it
work
> as 1 to n interfaces.
>
> Daliraju
>
> X-Message-Number: 15
> X-lyris-Id: 77741
> Date: Tue, 12 Jul 2005 16:57:55 -0700
> From: “Pankaj Garg”
> Subject: Re: Mux based ndis IM driver
>
> I can answer if you have any questions on 1:N driver since i have written
> one. Though i won’t be able to share the source code as it belongs to my
> company.
>
> –
> Pankaj Garg
>
>
> X-Message-Number: 14
> X-lyris-Id: 77727
> Date: Tue, 12 Jul 2005 10:58:01 -0600
> From: Vysyaraju Daliraju
> Subject: Mux based ndis IM driver
>
> Hi
> Could you help me finding out MUX based ndis IM driver which has 1 to N
> interfaces.
> The MUX driver comes with ddk supports n to 1 not 1 to n.
>
> Daliraju
> Software engineer
>
> For limitations on the use and distribution of this message, please visit
www.sbs.com/emaildisclaimer.
>
HI pankaj garg!
I still have some questions. I am new to intermediate drivers !!! Pl
clarify !
Can you link to any document if exits ?
You don’t need to modify the INF files. You should modify the notify dll to
create (Install) a virtual adapter during the driver initialization (in
function CMuxNotify::Install) and not create any more virtual adapters when
the driver is bound to physical adapters.
> How to create a virtual adapter ? What call I need to use ? How to avoid
virtual adapters generated by mux drivers. It is creating 8 virtual adapters
for each physical adapters. Where is this number 8 coming from ? Is it from
windows registry ?
You shall also disable the property sheet in the notify driver since you
just want to create one virtual adapter.
> you mean I need to comment notify.rc in the sources file ?
You will also have to modify the driver to store adapters information in 1:N
manner. Mainly you will have to change ADAPT and VELAN struct. In MUX
sample, one ADAPT can store list of VELAN, you will have to do the opposite.
> I am not clear how to do it ?
Other changes depends on what you exactly want this driver to do. Like if
you are building a load balancing driver, then you can distribute the
network traffic coming from one Virtual adapter between N physical adapters
etc.
> I am writing fail-over driver
I really appreciate your help.
Daliraju
For limitations on the use and distribution of this message, please visit www.sbs.com/emaildisclaimer.
The best thing to do is read the source code of MUX sample and understand
how binding to physical adapters work and how virtual adapters are created.
If you are new to windows driver development as well, then it will take a
good amount of time to understand it. For documentation refer to DDK and
look for INetCfg, INetCfgComponentSetup etc interfaces.
–
Pankaj Garg
This posting is provided “AS IS” with no warranties and confers no rights.
“Vysyaraju Daliraju” wrote in message
news:xxxxx@ntdev…
> HI pankaj garg!
>
>
> I still have some questions. I am new to intermediate drivers !!! Pl
> clarify !
> Can you link to any document if exits ?
>
>
> You don’t need to modify the INF files. You should modify the notify dll
to
> create (Install) a virtual adapter during the driver initialization (in
> function CMuxNotify::Install) and not create any more virtual adapters
when
> the driver is bound to physical adapters.
>
> >> How to create a virtual adapter ? What call I need to use ? How to
avoid
> virtual adapters generated by mux drivers. It is creating 8 virtual
adapters
> for each physical adapters. Where is this number 8 coming from ? Is it
from
> windows registry ?
>
> You shall also disable the property sheet in the notify driver since you
> just want to create one virtual adapter.
>
> >> you mean I need to comment notify.rc in the sources file ?
>
> You will also have to modify the driver to store adapters information in
1:N
> manner. Mainly you will have to change ADAPT and VELAN struct. In MUX
> sample, one ADAPT can store list of VELAN, you will have to do the
opposite.
>
> >> I am not clear how to do it ?
>
> Other changes depends on what you exactly want this driver to do. Like if
> you are building a load balancing driver, then you can distribute the
> network traffic coming from one Virtual adapter between N physical
adapters
> etc.
>
> >> I am writing fail-over driver
>
> I really appreciate your help.
>
> Daliraju
>
> For limitations on the use and distribution of this message, please visit
www.sbs.com/emaildisclaimer.
>