Prev: IoCreateDevice returns STATUS_OBJECT_NAME_NOT_FOUND
Next: Confirmation needed, DIFx + Sensor type = No go.
From: stuyckp on 26 Feb 2010 04:36
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 :
- install some kind of virtual adapter which needs to be configured with an ip address. This virtual adapter should be visible with ipconfig. And the ip configuration will be done manually. Say for instance I configure it with a dummy ip@ 200.200.200.200/24.
The ip@ of my application (with its own stack) is configured with say 200.200.200.201/24 so it is in the same subnet. If then by using a cmd window I do :
ping 200.200.200.201, I expect the application to receive ICMP messages in its stack, it should be able reply and the ICMP would be handed over to the stack of the PC (windows). So basically I can ping the application and it would work.
It is not completely clear to me what examples in the DDK I need to look at. I think more than one. Since the drivers seem to be layered too.
I have the feeling it are all NDIS related drivers.
Or does something like this exist already ?

---
frmsrcurl: http://msgroups.net/microsoft.public.development.device.drivers
From: Pavel A. on 26 Feb 2010 09:16
"stuyckp" <user(a)msgroups.net/> wrote in message
news:u#sbscstKHA.4492(a)TK2MSFTNGP05.phx.gbl...
> 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.
...........
> Or does something like this exist already ?

VMware!

--pa



From: stuyckp on 26 Feb 2010 14:12
how can I interface with a vmware driver then ?
Can I install this driver standalone without the remainder of vmware ? Point is I want to capture and send ethernet frames.

---
frmsrcurl: http://msgroups.net/microsoft.public.development.device.drivers/virtual-adapter-driver
From: Pavel A. on 26 Feb 2010 14:46
"stuyckp" <user(a)msgroups.net/> wrote in message
news:uQhUYextKHA.4908(a)TK2MSFTNGP06.phx.gbl...
> how can I interface with a vmware driver then ?

VMware provides several ways to talk with the VM - from creating a private
network hub between the host and VM,
and creating shared folders (independent of any networking) , to special
API.

You'll need to install a complete OS with your app in the VM, but you also
get
independent tcpip (or other protocol) stack. Very attractive for fast
prototyping.

> Can I install this driver standalone without the remainder of vmware ?
> Point is I want to capture and send ethernet frames.

AFAIK, interface of the virtual network is not published. So the quick
answer is no.
Maybe I'm wrong, need to check the current state on VMware forums.
MS has a virtual network software similar to VMware's in their Virtual PC
product, which is also used by their simulator of WinCE devices.
Again, the interface is not documented.

Good luck,
--pa


From: Burkhardt Braun on 27 Feb 2010 04:38
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



 |  Next  |  Last
Pages: 1 2 3
Prev: IoCreateDevice returns STATUS_OBJECT_NAME_NOT_FOUND
Next: Confirmation needed, DIFx + Sensor type = No go.