Prev: IoCreateDevice returns STATUS_OBJECT_NAME_NOT_FOUND
Next: Confirmation needed, DIFx + Sensor type = No go.
From: eagersh on 27 Feb 2010 15:28
On Feb 27, 2:38 am, Burkhardt Braun <burkhardt.br...(a)gmx.net> wrote:
> Hello!
> Not sure understanding you correctly,
>
> On Feb 26, 10:36 am, stuyckp <u...(a)msgroups.net/> wrote:> I am looking for a solution where I can run an application on my PC which can receive ethernet frames.
> > To the PC is must look as if the application is located on a different machine. This application has its own IP stack and a small ethernet layer.
> > So what I think that need sto be done is this :
>
> but you can install your own IP stack above the winpcap drivers.
> Using them enables you to run a second IP stack on one machine.
> So the whole SW stack would look like:
>
> Your application
> Your IP Stack  with you own IP-Address
> Winpcap libaries
>
> I assume that this is what you want to achieve.
>
> Kind regards
> Burkhardt Braun

To the advise of using Winpcap I would like to add that you could
develop your own NDIS Protocol driver and retrieve Ethernet frame
directly from the driver. WDK contains a good example of NDIS Protocol
driver which you could easily modify for your needs.

Igor Sharovar
From: Pavel A. on 27 Feb 2010 19:07
"eagersh" <eagersh20(a)gmail.com> wrote in message
news:81d23074-a921-4ae3-b143-bd570c2eeffc(a)e19g2000prn.googlegroups.com...
...........
> To the advise of using Winpcap I would like to add that you could
> develop your own NDIS Protocol driver and retrieve Ethernet frame
> directly from the driver. WDK contains a good example of NDIS Protocol
> driver which you could easily modify for your needs.

Igor, Winpcap is exactly this: a good example of NDIS protocol driver.

regards,
--pa


From: Thomas F. Divine on 27 Feb 2010 20:07
I would say that WinPcap is a good example of a NDIS protocol driver that is
designed specifically to support network monitoring. I would not promote it
as the foundation for a non-Microsoft TCP/IP transport.

In fact, it is likely that a NDIS protocol driver will not work at all for
this idea.

Because of the way the Windows network kernel is implemented all NDIS
protocol drivers will receive all inbound packets to the host. This presents
a problem for a second non-Microsoft TCP/IP implementation. For example, the
real Microsoft TCP/IP transport will receive all the packets packets
intended for the separate non-Microsoft TCP/IP transport; when it does, it
(or some firewall) may send abort or cause other mischief that will cause
problems.

So, it may be that instead of NDIS protocol driver one may need a NDIS MUX
or filter driver. (Or a separate real NIC that is not bound to the Microsoft
TCP/IP transport)

Thomas F. Divine

"Pavel A." <pavel_a(a)12fastmail34.fm> wrote in message
news:59EEAD40-A8FB-4F28-994B-9CE71C173EE4(a)microsoft.com...
> "eagersh" <eagersh20(a)gmail.com> wrote in message
> news:81d23074-a921-4ae3-b143-bd570c2eeffc(a)e19g2000prn.googlegroups.com...
> ..........
>> To the advise of using Winpcap I would like to add that you could
>> develop your own NDIS Protocol driver and retrieve Ethernet frame
>> directly from the driver. WDK contains a good example of NDIS Protocol
>> driver which you could easily modify for your needs.
>
> Igor, Winpcap is exactly this: a good example of NDIS protocol driver.
>
> regards,
> --pa
>
>
From: Philip Stuyck on 28 Feb 2010 14:41
I thought that winpcap is only for capturing ethernet frames, not for sending
own frames in response to what is being received.

"Pavel A." wrote:

> "eagersh" <eagersh20(a)gmail.com> wrote in message
> news:81d23074-a921-4ae3-b143-bd570c2eeffc(a)e19g2000prn.googlegroups.com...
> ..........
> > To the advise of using Winpcap I would like to add that you could
> > develop your own NDIS Protocol driver and retrieve Ethernet frame
> > directly from the driver. WDK contains a good example of NDIS Protocol
> > driver which you could easily modify for your needs.
>
> Igor, Winpcap is exactly this: a good example of NDIS protocol driver.
>
> regards,
> --pa
>
>
From: Philip Stuyck on 28 Feb 2010 14:48
I am not sure if I understand you.
I actually started with the example in the DDK NetVmini and activated the
traces. I changed the code somewhat to see the actual data.
Then I installed the driver and configured an ip address on this virtual
adapter : 200.200.200.200/24
If I then ping 200.200.200.201; the supposed ip address of my application,
then I see that the driver receive an ARP request message. So if my driver
would work properly, I would just forward this ARP towards my application and
let him handle it. The application would react with an ARP reply, which is
sent from application towards the driver I suppose (this is a bit blurry) and
then should go back to the requestor. For Windows it would seem like the
application is running remote on a network. There is no collision of ip
stacks that I can see.

"Thomas F. Divine" wrote:

> I would say that WinPcap is a good example of a NDIS protocol driver that is
> designed specifically to support network monitoring. I would not promote it
> as the foundation for a non-Microsoft TCP/IP transport.
>
> In fact, it is likely that a NDIS protocol driver will not work at all for
> this idea.
>
> Because of the way the Windows network kernel is implemented all NDIS
> protocol drivers will receive all inbound packets to the host. This presents
> a problem for a second non-Microsoft TCP/IP implementation. For example, the
> real Microsoft TCP/IP transport will receive all the packets packets
> intended for the separate non-Microsoft TCP/IP transport; when it does, it
> (or some firewall) may send abort or cause other mischief that will cause
> problems.
>
> So, it may be that instead of NDIS protocol driver one may need a NDIS MUX
> or filter driver. (Or a separate real NIC that is not bound to the Microsoft
> TCP/IP transport)
>
> Thomas F. Divine
>
> "Pavel A." <pavel_a(a)12fastmail34.fm> wrote in message
> news:59EEAD40-A8FB-4F28-994B-9CE71C173EE4(a)microsoft.com...
> > "eagersh" <eagersh20(a)gmail.com> wrote in message
> > news:81d23074-a921-4ae3-b143-bd570c2eeffc(a)e19g2000prn.googlegroups.com...
> > ..........
> >> To the advise of using Winpcap I would like to add that you could
> >> develop your own NDIS Protocol driver and retrieve Ethernet frame
> >> directly from the driver. WDK contains a good example of NDIS Protocol
> >> driver which you could easily modify for your needs.
> >
> > Igor, Winpcap is exactly this: a good example of NDIS protocol driver.
> >
> > regards,
> > --pa
> >
> >
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: IoCreateDevice returns STATUS_OBJECT_NAME_NOT_FOUND
Next: Confirmation needed, DIFx + Sensor type = No go.