Hi.
The situation is quite complex. NDISWAN has not the behaviour of a normal network adapter: it exports several NIC interfaces, and each of these interfaces can be bound only by a particular protocol and refuses all other protocol drivers. For example there are WAN interfaces for IP, IPX, MS netmon.
Moreover, these interfaces have a non standard behaviour: I was able to manually force the packet driver to bind over one of them pretending to be MS IP protocol. The binding process was successful, but I was not able to make it work properly. In particular:
- if I try to set the adapter in promiscuous mode (through the standard NDIS calls) the PPP connection freezes: no packets can be sent or received by the userland applications. Everything returns OK when the adapter exits from promiscuous mode.
- if the adapter is not in promiscuous mode, I'm able to sniff only incoming packets, outgoing packets are not seen by the packet driver.
As you can see, it's quite hard to make a protocol driver that works correctly over NDISWAN. I think that a better solution could be the use of an intermediate network driver. I read on usenet that it is possible to obtain wan packets correctly with such a driver. I am examinig this solution, but obviously intermediate drivers are more complex than protocol drivers...
Cheers,
Loris.
-----Messaggio Originale-----
Da: Guy Harris <gharris@xxxxxxxxxxxx>
A: Fulvio Risso <risso@xxxxxxxxx>
Cc: Guy Harris <gharris@xxxxxxxxxxxx>; Fulvio Risso <risso@xxxxxxxxxxxxxxxx>; Loris Degioanni <loris@xxxxxxxxxxxxxxxxxxxxxxx>; <ethereal-users@xxxxxxxx>
Data invio: giovedì 3 agosto 2000 21.39
Oggetto: Re: [ethereal-users] find the Interface under win98
> On Thu, Aug 03, 2000 at 08:49:25AM +0200, Fulvio Risso wrote:
> > The problem is that we are not able to make PPP working properly. Code
> > should be the same (opening an Ethernet card should be the same as opening a
> > PPP interface), however it doesn't work.
>
> Hmm.
>
> Perhaps this is the result of the odd plumbing used on WAN links - I
> think the low-level driver might talk to a PPP driver, which then talks
> to NDISWAN which translates between PPP and Ethernet, which then talks
> to the other protocols (IP, etc.).
>
> Does the capture driver appear above, or below, NDISWAN in the bindings
> on a system with PPP interfaces?
>
