Fredrik
Wed Mar 03 01:43:20 CST 2004
Thanks Maxim and Alireza!
I ended up using the MAC as unique identifier, it works pretty well. I
didn't use the the IP address since that might change over time.
/Fredrik
"Alireza Dabagh [MS]" <alid@online.microsoft.com> wrote in message
news:%23DRTAbMAEHA.3184@TK2MSFTNGP09.phx.gbl...
> This will be a lot easier in NDIS 6 because miniports can get their
ifIndex
> from NDIS directly.
>
> -ali
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
> news:%23%235xhMl$DHA.2576@tk2msftngp13.phx.gbl...
> > Your IM will catch OID_GEN_NETWORK_LAYER_ADDRESSES notification from
> TCPIP.
> > TCPIP sends it down to the adapter to notify the adapter's driver about
> its IP
> > addresses.
> >
> > Pass it down, but before doing this, save the IP addresses. Then do
> the
> > matching.
> >
> > Another variant is to use the adapter-related IP Helper APIs, then
use
> some
> > "Adapter Name", this is possibly the NDIS adapter name.
> >
> > --
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > maxim@storagecraft.com
> >
http://www.storagecraft.com
> >
> >
> > "Fredrik Jansson" <fredrik.jansson columbitech.com> wrote in message
> > news:uJBe%23rE$DHA.1844@TK2MSFTNGP11.phx.gbl...
> > > Hi!
> > >
> > > Is there any way for an intermediate driver to find out (in either
> > > ProtocolBindAdapter or MiniportInitialize) what interface index (IP
> Helper
> > > API) it will get.
> > >
> > > In userspace I keep track of adapter by their iphlp index and I would
> like
> > > to make a call down an intermediate driver with that index instead of
> the
> > > name of the adapter. It would be awesome if each of my miniports
> instances
> > > could figure out that index on their own.
> > >
> > > Cheers!
> > >
> > >
> >
> >
>
>