Re: How does a passthru driver intercept wireless wan network traf

On Feb 14, 1:46 am, Olle <O...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi!

I'm also trying to get the passthru filter to work with wwan.

The NdisOpenProtocolConfiguration always returns with
status=STATUS_INSUFFICIENT_RESOURCES for me although the bind seems to
complete successfully. Do you see the same behaviour?

I also get a lot of calls to ProtocolStatus with
status=NDIS_STATUS_WW_INDICATION. Not sure how to decode these though. I seem
to get thre types; NDIS_WW_REGISTER_STATE, NDIS_WW_PACKET_SERVICE and
NDIS_WW_SIGNAL_STATE. But I'm having some problems with getting the
attributes mode,state, etc. They all look like garbage...

Any help would be higly appreciated.

BR
Olle



"danlo" wrote:
On Feb 13, 11:37 am, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
Useful information. Thanks for posting back.

Paul T.

"danlo" <danti...@xxxxxxxxx> wrote in message

news:05c2516b-5710-4d33-9532-9ecf8d6abda2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 13, 7:39 am, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

OK. I presume that the adapter is related to actual WWAN radios, GPRS or
whatever. Again, are you testing binding when you are *NOT* connected via
ActiveSync? I don't think that phone-based networking is enabled when
ActiveSync is connected, either.

Paul T.

"danlo" <danti...@xxxxxxxxx> wrote in message

news:864fbf81-db7f-4d7a-a429-52899a6254a6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 12, 11:24 am, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

OK, no, that's not the name of the SDIO WiFi adapter. At least on my
device, which has basically the same set of things, the WiFi adapter is
TNETWLN1. Remote Registry Editor will tell you quite a bit about what
adapters are what (HKLM/Comm is the root for NDIS stuff). Remember that
most, if not all, WM5 devices disable WiFi while they are connected to
USB...

Paul T.

"danlo" <danti...@xxxxxxxxx> wrote in message

news:b4b34602-880f-49ce-bfba-cb147d6b408c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 12, 9:51 am, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

There are several possible meanings of that. What does the network
cards
list show? Just "WWAN1"? Mine shows several adapters, most of which
are
not active and, I presume, could not be bound.

Paul T.

"danlo" <danti...@xxxxxxxxx> wrote in message

news:a6cf3432-6172-44f2-8299-de8b708cb72c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 12, 7:50 am, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:

What do you mean by that? It gets all of the network data that any
other
media type would get. If you're saying that you want to intercept
the
negotiation of access point association or something like that, you
can't
do
that. That never comes to the Windows CE end of things. It might be
done
in the driver or it might be in hardware.

Paul T.

"danlo" <danti...@xxxxxxxxx> wrote in message

news:f9eb472c-a85a-4a3d-aee7-097fb8a1ea8f@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi,

I'm developing a NDIS IM driver based on the sample passthru
driver.
This driver needs to be able to intercept all the traffic
including
ethernet lan, wan, wireless wan traffic. The sample passthru
driver
obviously is not capable of intercepting wireless wan network
traffic.
Can anybody shed some light on what I should do to be able to
intercept the wirelss wan traffic? Thanks.

Daniel- Hide quoted text -

- Show quoted text -

Hi Paul,

Sorry. I forgot to mention. This is in pocket pc environment. There's
a NIC called WWAN1, which is for wireless wan, which the sample
passthru driver fails to bind to.

Daniel- Hide quoted text -

- Show quoted text -

I have a Wi-Fi SDIO card, Remote NDIS Host. Others are like non-
bindable.
I think it's the Wi-Fi SDIO that I have problem bind to.

Daniel- Hide quoted text -

- Show quoted text -

Hi Paul,

You are right. I was wrong. It's not a Wi-Fi. I know the device name
is WWAN1, and the medium type is NdisMediumWirelessWan.
The sample passthru driver does not support this mediuam type, so
NdisOpenAdapter would fail, and the passthru driver was not able to
bind to this adapter, thus not able to intercept the inbound/outbound
packets on this adapter.

Daniel- Hide quoted text -

- Show quoted text -

Yes. I was testing with the device in standalone. So when I launched
internet explorer, I saw the dialing going on.

The other thing is, the sample passthru driver does not support
NdisMediumWirelessWan. So in ProtocolBindAdapter, when I tried to bind
to WWAN1, NdisOpenAdapter would fail. I added NdisMediumWirelessWan to
the g_aNdisMedium array, that helped fixed the problem, and I was able
to bind to WWAN1 successfully. (NdisOpenAdapter ,
NdisIMInitializeDeviceInstanceEx, MPInitialize all completed
successfully)

Daniel- Hide quoted text -

- Show quoted text -

You are welcome. Thanks for your replies.- Hide quoted text -

- Show quoted text -

Yes. I also got STATUS_INSUFFICIENT_RESOURCES from
NdisOpenProtocolConfiguration. But this is benign. If you look at
passthru sample code, it actually proceeds.

In addition, to intercept wan traffic. You need to bind to ASYNCMAC.

Daniel
.

Relevant Pages

  • Re: How does a passthru driver intercept wireless wan network traf
    ... I'm also trying to get the passthru filter to work with wwan. ... passthru driver fails to bind to. ... The sample passthru driver does not support this mediuam type, ... NdisOpenAdapter would fail, and the passthru driver was not able to ...
    (microsoft.public.windowsce.embedded)
  • Re: pci probe
    ... PCI Hotplug is showing up in more places that people ... called for two PCI devices and bind to both of them. ... No, you can specify multiple devices in the same device id table, and ... your driver will get called for all of the matching devices. ...
    (Linux-Kernel)
  • Re: [RFC] bind and unbind drivers from userspace through sysfs
    ... which will detect the kindof device plugged and will load proper driver. ... In bind mode case ... driver should work with given hardware. ... imagine I have a MUX controller (4 AUX ports) and I have standard PS/2 ...
    (Linux-Kernel)
  • Re: [SOLARIS 10][X86] metadb problem
    ... read the "FAQ on the rootnex bind warning ... can wrongly return more cookies than a driver specifies is ... This is a bug ... If it cannot handle that number of cookies, ...
    (comp.unix.solaris)
  • Re: NDIS IM Layering
    ... have their FilterClass specified as failover in their respective INF ... cannot have more than one modifying LWF in the same stack, ... then it will bind to one or the other but not both. ... modifying driver will probably bind as 802.3 above the Microsoft Native ...
    (microsoft.public.development.device.drivers)