Re: [ros-dev] Instanciate TAP device for Virtualisation

[Maxime Daniel]

In fact, we the problem we face is the Miniport Initialize function which seems to be
ignored when using Virtual Ethernet (without hardware). This problem seems linked with PnP
Manager.

In this version:
http://git.reactos.org/?p=reactos.git;a=blob;f=reactos/drivers/net/ndis/ndi…
The InitializeHandler is hard-called on the end of NdisMRegisterMiniport.

On the current implementation, the single time InitializeHandler is called is on
NdisIPnPStartDevice. How the PnP Manager can be called by another driver to load it
manually ? What should be done or edited to make it possible ?

Thanks

(Aleksey Bragin <aleksey(a)reactos.org>) Thu, 08 May 2014 21:35:14 +0400:

>   Guys, any ideas?
>  Cameron, maybe you could tell what direction to look?
>  
>  This blocks further work in the area.
>  
>  Regards,
>  Aleksey Bragin
>  
>  On 08.05.2014 19:15, Maxime Daniel wrote:
> >   Hi,
> >
> >  I'm working on network virtualization support in ReactOS.
> >  At this time, PoC works but I reach a point where I need a solution that would allow to
> > add and remove TAP (TAP-Win32 from OpenVPN for exemple) Network Devices from kernel space,
> > without user intervention.
> >
> >  The problem right now is that there seems to be impossible in ReactOS to have a proper
> > way or tips and tricks to add/remove TAP devices without rebooting the system. What should
> > be fixed/edit to instanciate of TAP device on the fly on the current implementation
> > (r63193) ?
> >
> >  Thanks
> >  
>  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev 

-- 
Daniel Maxime
Linux version 3.10.9-maxux64 (syna) (gcc version 4.7.3 (Gentoo 4.7.3 p1.2, pie-0.5.5) ) #6
SMP Thu Sep 5 20:17:50 CEST 2013
 22:06:43 up 17 days, 21:25,  8 users,  load average: 0.22, 0.36, 0.34