精华内容
下载资源
问答
  • RNDIS数据在原生Wireshark只能解析到USB URB层,后面是RAW DATA;为了调研方便,于是用lua语言开发了rndis的解析插件。 20210806: 更新了脚本中的一些解析bug。
  • 小米rndis驱动xp下载

    2020-09-14 17:22:06
    台式机电脑没有无线网卡,没法共享手机wifi热点上网,那么可以通过手机USB共享网络上网,安装rndis驱动,这里包括了所有rndis的驱动,安卓设备pad在xp的情况下无法共享,后面吧htc的rndis复制到驱动中即可。...
  • XP系统USB绑定RNDIS驱动

    2018-09-20 00:57:30
    3这里我们可以看到设备管理器中RNDIS设备这里出现问题,驱动不正常。4这时候我们首先需要下载“USB绑定RNDIS驱动”。5这时候在设备管理器中,在RNDIS设备上单击右键,出现菜单点击更新驱动程序。6硬件更新向导中,...
  • 小米rndis驱动.rar

    2020-09-02 10:49:04
    小米可以用的RNDIS的驱动程序!Android通用吧!!!! 小米可以用的RNDIS的驱动程序!Android通用吧!!!!
  • kindle_rndis.inf_amd64.zip

    2019-11-02 12:16:42
    kindle_rndis_inf_amd64-v1_0_0_1 大家知道我们的手机上有一个USB共享上网的功能,就是电脑可以通过数据线连接手机,然后手机USB共享网络,这样电脑就可以使用手机连接的 WIFI上网了,当然有时候我们可能需要通过...
  • win10_RNDIS_驱动.7z

    2020-08-20 19:18:22
    win10 RNDIS 驱动,usbnet 访问,按照附件中的文档说明,依次执行脚本后安装,安装成功后,配置ip, 亲测有效,能ping通,然后连telnet 或vlc,非常方便。
  • RNDIS共享windows网络连接 1.内核驱动配置 2.驱动加载顺序 3.网络设置
  • arm linux 使用RNDIS协议,通过USB模拟网卡,实现与PC端的交互,这是win10的驱动,缺少该驱动windows会认为是串口设备
  • USB-RNDIS_win10 64位驱动

    2020-02-12 20:39:25
    win10 64位的USB-RNDIS驱动,亲测可用,win10自带驱动会驱成串口,需要更新驱动使用本驱动。
  • rndis驱动。如果设备被识别为串口,管理员权限运行第五个程序。右键选中识别为串口的RNDIS设备。手动安装该驱动
  • 说明:win10下usb rndis驱动会默认识别为com口,经本人亲测可以使用该驱动在网络适配器里面出现小电脑,并网络ping通
  • # [ 3793.175183] g_ether gadget: high-speed config #2: RNDIS [ 3793.266107] g_ether gadget: high-speed config #2: RNDIS # ping 192.168.1.121 PING 192.168.1.121 (192.168.1.121): 56 data bytes 64 bytes ...
  • RNDIS/Ethernet Gadget driver

    2018-05-07 11:55:50
    RNDIS/Ethernet Gadget Windows driver
  • usb rndis驱动, win10的

    2018-07-25 11:46:05
    在win10下安装 usb rndis驱动。。
  • RNDIS/Ethernet Gadget 虚拟网卡驱动,用于win10下和树莓派Zero/ZeroW的直接otg连接。树莓派Zero直连Win10电脑方法参考:https://blog.csdn.net/weixin_41216356/article/details/107125138
  • win10 的RNDIS驱动

    2018-07-06 13:48:25
    连接RNDIS,在windows10系统下应用的驱动,用于连接motolora ACE
  • usb绑定rndis驱动是专门用来帮助用户通过usb连接电脑来共享网络的电脑驱动程序,有了它用户就可以实现共享上网了,非常的方便与实用。有需要的的朋友快来下载体验吧!usb绑定rndis驱动介绍安卓手机usb共享电脑宽带...
  • RNDIS/Ethernet 驱动for win10 ,可能设备已经被识别成了串口,要重新安装驱动
  • 这里包括了所有rndis的驱动,本人遇到了一个问题,pad在xp的情况下无法共享,后面吧htc的rndis复制到驱动中即可。
  • RNDIS

    千次阅读 2020-02-06 10:01:21
    rndis既是RemoteNDIS,既是远程网络驱动接口规范。 Remote Network Driver Interface Specification,既是RemoteNDIS,既是远程网络驱动接口规范。基于USB实现RNDIS实际上就是TCP/IP over USB,就是在USB设备上跑...

    rndis既是RemoteNDIS,既是远程网络驱动接口规范

    Remote Network Driver Interface Specification,既是RemoteNDIS,既是远程网络驱动接口规范。基于USB实现RNDIS实际上就是TCP/IP over USB,就是在USB设备上跑TCP/IP,让USB设备看上去像一块网卡。

     

     

     

    展开全文
  • Windows10 64位的USB-RNDIS驱动,win10自带驱动会驱成串口,需要更新驱动使用本驱动。
  • windows RNDIS

    2021-01-04 19:30:57
    refer to: ...Remote NDIS (RNDIS) is a bus-independent class specification for Ethernet (802.3) network devices on dynamic Plug and Play (PnP) bu...

     

    refer to:  https://docs.microsoft.com/en-us/windows-hardware/drivers/network/remote-ndis--rndis-2

     

     

    1. introduction

    Remote NDIS (RNDIS) is a bus-independent class specification for Ethernet (802.3) network devices on dynamic Plug and Play (PnP) buses such as USB, 1394, Bluetooth, and InfiniBand. Remote NDIS defines a bus-independent message protocol between a host computer and a Remote NDIS device over abstract control and data channels. Remote NDIS is precise enough to allow vendor-independent class driver support for Remote NDIS devices on the host computer.

    Microsoft Windows versions beginning with Windows XP include a Remote NDIS driver for USB devices. To use this driver with a USB device, an IHV must provide an INF file that follows the template in Remote NDIS INF Template.

    Remote NDIS messages are sent to a Remote NDIS device from the host, and a Remote NDIS device responds with an appropriate completion message. Messages are also sent in a unsolicited fashion from a Remote NDIS device to the host.

     

     

    2. RNDIS overview

    2.1 overview

    Remote NDIS (RNDIS) eliminates the need for hardware vendors to write an NDIS miniport device driver for a network device attached to the USB bus. Remote NDIS accomplishes this by defining a bus-independent message set and a description of how this message set operates over the USB bus. Because this Remote NDIS interface is standardized, one set of host drivers can support any number of networking devices attached to the USB bus. This significantly reduces the development burden on device manufacturers, improves the overall stability of the system because no new drivers are required, and improves the end-user experience because there are no drivers to install to support a new USB bus-connected network device. Currently Microsoft Windows provides support for Remote NDIS over USB.

    The following figure shows the replacement of the device manufacturer's NDIS miniport with the combination of a Remote NDIS miniport driver and a USB transport driver. The device manufacturer can therefore concentrate on device implementation and not have to develop a Windows NDIS device driver.

    Microsoft provides an NDIS miniport driver, Rndismp.sys, which implements the Remote NDIS message set and communicates with generic bus transport drivers, which in turn communicate with the appropriate bus driver. This NDIS miniport driver is implemented and maintained by Microsoft and is distributed as part of Windows.

    The following Remote NDIS message set mirrors the semantics of the NDIS miniport driver interface:

    • Initializing, resetting, and halting device operation

    • Transmitting and receiving networking data packets

    • Setting and querying device operational parameters

    • Indicating media link status and monitoring device status

    Microsoft also provides a USB bus transport driver that implements a mechanism for carrying the Remote NDIS messages across the USB bus. This driver transports standardized Remote NDIS messages between the Remote NDIS miniport driver and the bus-specific driver, such as USB. The bus-specific drivers are also required to map any bus-specific requirements, such as power management, into standardized Remote NDIS messages. The transport driver for USB 1.1 and 2.0 is implemented and maintained by Microsoft and distributed as part of Windows.

    This structure allows a single device driver to be used for any Remote NDIS device for which there is a bus-specific transport layer. In addition, only one bus transport layer is required for all network devices on a specific bus.

     

    2.2 RNDIS file

    In order to support legacy Remote NDIS devices, multiple Remote NDIS drivers have been included with various versions of Windows. The following table lists the Remote NDIS driver names used in each version of Windows.

     

    2.3 RNDIS inf template

    Microsoft provides an NDIS miniport driver, Rndismp.sys, which implements the Remote NDIS message set and communicates with generic bus transport drivers, which in turn communicate with the appropriate bus driver. This NDIS miniport driver is implemented and maintained by Microsoft and is distributed as part of all supported Windows versions. You can find it in the %SystemRoot%\System32\drivers directory.

     

    RNDIS INF template for NDIS 6.0 (Windows 7 and later)

    ; Remote NDIS template device setup file

    ; Copyright (c) Microsoft Corporation

    ;

    ; This is the template for the INF installation script  for the RNDIS-over-USB

    ; host driver that leverages the newer NDIS 6.x miniport (rndismp6.sys) for

    ; improved performance. This INF works for Windows 7, Windows Server 2008 R2,

    ; and later operating systems on x86, amd64 and ia64 platforms.

     

    [Version]

    Signature           = "$Windows NT$"

    Class               = Net

    ClassGUID           = {4d36e972-e325-11ce-bfc1-08002be10318}

    Provider            = %Microsoft%

    DriverVer           = 07/21/2008,6.0.6000.16384

    ;CatalogFile        = device.cat

     

    [Manufacturer]

    %Microsoft%         = RndisDevices,NTx86,NTamd64,NTia64

     

    ; Decoration for x86 architecture

    [RndisDevices.NTx86]

    %RndisDevice%    = RNDIS.NT.6.0, USB\VID_xxxx&PID_yyyy

     

    ; Decoration for x64 architecture

    [RndisDevices.NTamd64]

    %RndisDevice%    = RNDIS.NT.6.0, USB\VID_xxxx&PID_yyyy

     

    ; Decoration for ia64 architecture

    [RndisDevices.NTia64]

    %RndisDevice%    = RNDIS.NT.6.0, USB\VID_xxxx&PID_yyyy

     

    ;@@@ This is the common setting for setup

    [ControlFlags]

    ExcludeFromSelect=*

     

    ; DDInstall section

    ; References the in-build Netrndis.inf

    [RNDIS.NT.6.0]

    Characteristics = 0x84   ; NCF_PHYSICAL + NCF_HAS_UI

    BusType         = 15

    ; NEVER REMOVE THE FOLLOWING REFERENCE FOR NETRNDIS.INF

    include         = netrndis.inf

    needs           = usbrndis6.ndi

    AddReg          = Rndis_AddReg

    *IfType            = 6    ; IF_TYPE_ETHERNET_CSMACD.

    *MediaType         = 16   ; NdisMediumNative802_11

    *PhysicalMediaType = 14   ; NdisPhysicalMedium802_3

     

    ; DDInstal.Services section

    [RNDIS.NT.6.0.Services]

    include     = netrndis.inf

    needs       = usbrndis6.ndi.Services

     

    ; Optional registry settings. You can modify as needed.

    [RNDIS_AddReg] 

    HKR, NDI\params\RndisProperty, ParamDesc,  0, %Rndis_Property%

    HKR, NDI\params\RndisProperty, type,       0, "edit"

    HKR, NDI\params\RndisProperty, LimitText,  0, "12"

    HKR, NDI\params\RndisProperty, UpperCase,  0, "1"

    HKR, NDI\params\RndisProperty, default,    0, " "

    HKR, NDI\params\RndisProperty, optional,   0, "1"

     

    ; No sys copyfiles - the sys files are already in-build 

    ; (part of the operating system).

     

    ; Modify these strings for your device as needed.

    [Strings]

    Microsoft             = "Microsoft Corporation"

    RndisDevice           = "Remote NDIS6 based Device"

    Rndis_Property         = "Optional RNDIS Property"

     

     

    3 . RNDIS to usb mapping

    A USB Remote NDIS device is implemented as a USB Communication Device Class (CDC) device with two interfaces. A Communication Class interface, of type Abstract Control, and a Data Class interface combine to form a single functional unit representing the USB Remote NDIS device. The Communication Class interface includes a single endpoint for event notification and uses the shared bidirectional Control endpoint for control messages. The Data Class interface includes two bulk endpoints for data traffic.

     

    3.1 usb descriptor

    1) device desc

    2) configuration desc

    none

    3) communication class interface

    The Communication Class interface is described by a USB interface descriptor, three class-specific descriptors, and an endpoint descriptor for the notification endpoint. The notification endpoint descriptor is a standard USB Interrupt-type IN endpoint descriptor whose wMaxPacketSize field is 8 bytes. The following table defines the prominent fields of the Communication Class interface descriptor.

    4) data class interface

    The Data Class interface is described by a standard USB Interface Descriptor followed by two endpoint descriptors. The two endpoint descriptors in the Data Class interface define standard USB Bulk-type endpoints: one Bulk-IN and one Bulk-OUT. The following table defines the prominent fields of the Data Class Interface Descriptor.

     

     

     

     

     

     

    展开全文
  • 很多人在寻找RNDIS/EthernetGadget驱动,这里将这款驱动带给大家,希望能对大家有所帮助。驱动介绍RNDIS/EthernetGadget驱动,很难找到,装了activesync也没有用,只有自己下载了之后修改的inf配置文件。安装,欢迎...
  • 台式机电脑没有无线网卡,没法共享手机wifi热点上网,那么可以通过手机USB共享网络上网,安装rndis驱动,这里包括了所有rndis的驱动,安卓设备pad在xp的情况下无法共享,后面吧htc的rndis复制到驱动中即可。...
  • [MS-RNDIS].7z

    2019-07-17 09:19:05
    微软RNDIS规范资料,详细介绍了RNDIS协议规范,及RNDIS驱动兼容性问题
  • 修改的RNDIS USB kit 2005驱动,支持linux的USB虚拟RNDIS驱动设备在windows下使用的驱动。

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 2,061
精华内容 824
关键字:

rndis