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

2014-06-05 Thread Maxime Daniel
Cameron, can you take a look at https://jira.reactos.org/browse/CORE-8292 ?
This describe the problem occured with the on-the-fly load driver that we need

Thanks

(Cameron Gutman aicomman...@gmail.com) Tue, 13 May 2014 15:29:47 -0500:

 InitializeHandler is called when the miniport is started by the PnP
 Manager. You can't force a miniport driver to be loaded without a device
 (whether real or virtual) for the miniport driver to control.
 
 You'll want to just create an INF file that installs your miniport driver
 for some PnP ID that you make up. You can then call some SetupAPI functions
 to create a virtual device node and install your driver on it.
 
 Here's an example of what you'll want to do to create the virtual device:
 https://github.com/CrowdStrike/Tortilla/blob/master/Tortilla/InstallTortillaDriver/InstallTortillaDriver.cppon
 lines 635-811
 And here's an example of the INF you'll need to write:
 https://github.com/CrowdStrike/Tortilla/blob/master/Tortilla/TortillaAdapter/netTor.inf
 
 I don't know whether this will work on ReactOS. The code seems to be there,
 but that's no guarantee that it works ;)
 
 Thanks,
 Cameron
 
 
 On Tue, May 13, 2014 at 3:15 PM, Maxime Daniel l...@maxux.net wrote:
 
  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/ndis/miniport.c;h=399ff1cb97546d9f0a43bb1c2a698ee831e3983b;hb=e3cbb33ea64b0bd3f56767dc397500ed6bb38e16
  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 alek...@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@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
 
  ___
  Ros-dev mailing list
  Ros-dev@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
 15:44:54 up 40 days, 15:03, 16 users,  load average: 0.30, 0.35, 0.39

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


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

2014-05-13 Thread 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/ndis/miniport.c;h=399ff1cb97546d9f0a43bb1c2a698ee831e3983b;hb=e3cbb33ea64b0bd3f56767dc397500ed6bb38e16
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 alek...@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@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

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


[ros-dev] Instanciate TAP device for Virtualisation

2014-05-08 Thread Maxime Daniel
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

-- 
Daniel Maxime
Linux version 3.6.9-maxux64 (emy) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, 
pie-0.5.5) ) #3 SMP PREEMPT Wed Feb 19 16:40:22 CET 2014
 17:15:01 up 1 day,  1:44,  1 user,  load average: 0.29, 0.28, 0.35

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


[ros-dev] Installing driver without reboot

2014-03-28 Thread Maxime Daniel
Hi,

Is it possible to install a driver (virtual network interface) witout reboot 
the system ?
I tried TAP interface (installation with devcon: devcon install inf-file 
tap0901) but the interface is only loaded during the next reboot (same for a 
ndis sample from DDK)

Is there a way to load a driver interface with a true plug'n'play mechanism ?

-- 
Daniel Maxime
Linux version 3.6.9-maxux64 (emy) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, 
pie-0.5.5) ) #3 SMP PREEMPT Wed Feb 19 16:40:22 CET 2014
 16:33:29 up 24 days, 8 min,  1 user,  load average: 0.31, 0.68, 0.72

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


[ros-dev] ndis netvmini adapter

2014-03-25 Thread Maxime Daniel
Hi,

I'm trying to compile and test the netvmini ndis 5 adapter code from WDK, at 
first to understand how it works, then to modify it for another purpose.

At this time I:
- put the code on driver/network/dd/netvmini and adapted CMakeLists
- put the inf on media/inf and adapted CMakeLists
- fixed the code, it builds
- add an entry to hivesys.inf to load the driver at boot

The driver is well displayed during boot, debug message appears (the 
DriverEntry), on NtObj, the driver is visible and it appears on Non Plug and 
Play on device manager.

Now, I don't know exactly what to do with it. How can I call the driver and add 
an adapter ?
The userland tool given with the code works (I needed to comment some functions 
and add _DEV_BROADCAST_HANDLE struct by hand, it seems to not be implemented on 
dbt.h).
When I run the userland tools, it fails with EnumDevices.

Some help ?

Thanks

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


Re: [ros-dev] NDIS NdisIMRegisterLayeredMiniport

2014-03-07 Thread Maxime Daniel
Thanks

How/when MiniportInitialize is triggered ?
I tried with NdisMRegisterMiniport at first, and the driver is loaded 
(DriverEntry is called and succeed) but MiniportInitialize is not called. 
Should I specify something ? There is no PnP event.

(Cameron Gutman cameron.gut...@reactos.org) Thu, 6 Mar 2014 22:30:49 -0500:

 There’s no requirement to have any real hardware behind a miniport. You can 
 use NdisMRegisterMiniport and return whatever media type you want in your 
 MiniportInitialize function (most likely NdisMedium802_3 to use Ethernet 
 framing).
 
 On Mar 6, 2014, at 8:23 AM, Maxime Daniel l...@maxux.net wrote:
 
  Hello,
  
  I need to use NDIS NdisIMRegisterLayeredMiniport functions to provide a 
  virtual ethernet card. I read the documentation on MSDN and it seems that 
  this functions is required to build an adapter without physical link (eg, 
  with no hardware IRQ).
  
  The problem is that this function is not implemented yet on reactos (svn 
  rev. 62083). Is someone can tell me if it's implementable or if there is an 
  alternative to build a virtual ethernet adapter with current implementation 
  of NDIS.
  
  Thanks.
  
  -- 
  Daniel Maxime
  Linux version 3.6.9-maxux64 (emy) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, 
  pie-0.5.5) ) #3 SMP PREEMPT Wed Feb 19 16:40:22 CET 2014
  14:02:53 up 1 day, 21:38,  1 user,  load average: 0.17, 0.26, 0.23
  
  ___
  Ros-dev mailing list
  Ros-dev@reactos.org
  http://www.reactos.org/mailman/listinfo/ros-dev
 
 
 ___
 Ros-dev mailing list
 Ros-dev@reactos.org
 http://www.reactos.org/mailman/listinfo/ros-dev

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] NDIS NdisIMRegisterLayeredMiniport

2014-03-06 Thread Maxime Daniel
Hello,

I need to use NDIS NdisIMRegisterLayeredMiniport functions to provide a virtual 
ethernet card. I read the documentation on MSDN and it seems that this 
functions is required to build an adapter without physical link (eg, with no 
hardware IRQ).

The problem is that this function is not implemented yet on reactos (svn rev. 
62083). Is someone can tell me if it's implementable or if there is an 
alternative to build a virtual ethernet adapter with current implementation of 
NDIS.

Thanks.

-- 
Daniel Maxime
Linux version 3.6.9-maxux64 (emy) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, 
pie-0.5.5) ) #3 SMP PREEMPT Wed Feb 19 16:40:22 CET 2014
 14:02:53 up 1 day, 21:38,  1 user,  load average: 0.17, 0.26, 0.23

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev