Fotoloading632

TL-USBNet Device Driver for Windows 10, 8.1, 8 and 7

With integrated V BUS switch gate drivers (PMOS), this certified USB-C 1.4 Power Sinking Device can be supplied directly by V BUS. In this case, power is provided directly by the source, avoiding any leakage from local batteries when the USB-C port is not used. Moxa's UPort series USB-to-serial converters provide computers with high-performance, industrial-grade connections for up to 16 serial devices over a single USB port. A wide range of converters are available with features that include Hi-Speed USB 2.0 with data rates up to 480 Mbps, advanced UARTs for high-end serial performance, COM port mapping, fixed-base COM functionality, and more.

Supported PlatformsDemoPrices

Thesycon’s TL-USBNet driver provides a network adapter emulation on Windows operating systems by implementing the specific network protocol on USB.

TL-USBNet device driver works with USB devices that are compliant to the following CDC subclasses:

• Ethernet Control Model (CDC/ECM)
  
• Network Control Model (CDC/NCM)
  
• Ethernet Emulation Model (CDC/EEM)

The driver implements a network adapter based on Microsoft's network driver model NDIS (Network Driver Interface Specification).

• Supports USB 2.0 full speed and high speed, and USB 3.0 super speed or higher
• Supports devices that are compliant with one of the following device class specifications: CDC/ECM, CDC/NCM, CDC/EEM
• Compatible with device implementations based on the Linux USB gadget framework
• Supports devices that implement a subset of the specification only, i.e. a subset of the required class requests
• Implements an NDIS 6.20 compliant network adapter for Windows 7.
• Implements an NDIS 6.30 compliant network adapter for Windows 8 and Windows 8.1.
• Implements an NDIS 6.50 compliant network adapter for Windows 10.
• USB communication based on WDF (KMDF)
• Optionally the driver supports advanced USB power management including selective suspend (Windows 10 only)
• Driver behavior is highly configurable via customization settings
• Custom features or optimizations can be implemented on request
• Source code is available on request (subject to a separate license agreement)

• The driver will be delivered fully customized for licensee’s product.
• Customization includes USB VID/PID, file names, text strings, etc.
• Windows 10 version of the driver is signed with Microsoft Attestation signing.
• Windows 7/8 version of the driver is signed with Thesycon’s code signing certificate.
• Driver Customization Kit add-on: The Driver Customization Kit enables licensee to customize the driver by themselves.

• Supported scenarios: first-time installation, driver update, removal of driver software
• Interactive mode with graphical user interface
• Silent mode without user interface, enables integration into surrounding software installers
• Supports popup-free installation

The driver is conform with current WHQL and Hardware Lab Kit (HLK) requirements. To get a WHQL certification, HLK tests must be executed with licensee's device which can be done by licensee or Thesycon. If you are interested in a WHQL certification, please contact Thesycon for a quotation.

Our software is purely designed and implemented by our team in Germany - no outsourcing. Technical support is provided directly by the developers.

This driver is a replacement for the former USB CDC/ECM, USB CDC/NCM and USB CDC/EEM drivers. Latest version of these drivers is 2.56. Licensees can upgrade to the new TL-USBNet driver.

Current version of TL-USBNet driver: 3.40

The free evaluation version of the TL-USBNet driver works for an interval of 60 days without any limitation. After that evaluation period has expired, the driver stops working.

Current version of driver for Windows CE and Embedded Compact: 1.13

NOTE: The driver described on this page is *not for use by end users*. It will not help solve any problems you may experience with a consumer device such as a webcam, camcorder, card reader, external sound card, etc. Thesycon’s device drivers are software components intended to be used by hardware or software manufacturers to create end products.

For each USB device model an official USB vendor ID (VID) is required. Vendor IDs must be unique and will be assigned by the USB Implementers Forum (www.usb.org). Registration fees will be charged.

Thesycon owns a USB vendor ID and provides a subset of product IDs (PID) to licensees of Thesycon drivers.

© 2021 THESYCON

Table of contents

1. 1.4.3.1 Support for Multiple Virtual Network Adapters
2. 2.4.3.2 Virtual Network Adapter Creation and Setup
   1. 2.1.Creating a Virtual Network Adapter
   2. 2.2.Normal Virtual Network Adapter Settings
   3. 2.3.Changing Advanced Settings
   4. 2.4.Removing a Virtual Network Adapter
   5. 2.5.Enabling and Disabling a Virtual Network Adapter
   6. 2.6.Messages Indicating that a Network Cable is Unplugged
3. 3.4.3.3 Managing the Version of the Virtual Network Adapter Device Driver
4. 4.4.3.4 Bridge Connection Between a Virtual Network Adapter and Physical Network Adapter

SoftEther VPN Client communicates over a VPN by creating a Virtual Network Adapter on the system. The Virtual Network Adapter is recognized by the Windows operating system and applications running on Windows as a network device in the same way as a physical network adapter. This enables the user to use the Virtual Network Adapter with TCP/IP protocols and other network protocols (such as NetBEUI).

4.3.1 Support for Multiple Virtual Network Adapters

The earlier version of SoftEther 1.0 (older version) only allowed the user to create one Virtual Network Adapter on the system. In SoftEther VPN Client, however, multiple Virtual Network Adapters can be created on the system, unique TCP/IP protocol settings can be configured for each Virtual Network Adapter, and these Virtual Network Adapters can then connect to the VPN simultaneously as individual network devices.

Support for Multiple Virtual Network Adapters.

Jdsu Germany Port Devices Driver Ed

4.3.2 Virtual Network Adapter Creation and Setup

Creating a Virtual Network Adapter

When the VPN client is first installed, there will be no Virtual Network Adapters registered. The user can freely create as many Virtual Network Adapters as needed.

Each new Virtual Network Adapter must be given a name. A name consists of up to 31 alphanumeric characters. However, names are limited to four characters under Windows 98 Second Edition and Windows Millennium Edition. When multiple Virtual Network Adapters are created, the Virtual Network Adapter names must all be different.

Only users with administrator privileges on the computer can change Virtual Network Adapter settings. Only users who can connect to and control the VPN client service on the computer can create or delete Virtual Network Adapters.

To create a new Virtual Network Adapter, click [Create Virtual Network Adapter] under [Virtual Adapter] menu in the VPN Client Manager.

New Virtual Network Adapter Creation Dialog.

Normal Virtual Network Adapter Settings

A newly created Virtual Network Adapter will be recognized as a Windows device. It will be displayed as a [new network connection] icon in [Network Connections] in the Windows Control Panel.

If, for example, the name of the newly created Virtual Network Adapter was 'ABC', that Virtual Network Adapter device name will be registered and displayed as 'VPN Client Adapter - ABC' in the Device Manager. Also, the name of the icon registered in the Control Panel's [Network Connection] window will be 'ABC - VPN client'. The user can change this name at any time.

Virtual Network Adapter Display in Network Connections.

The TCP/IP protocol and other settings for the Virtual Network Adapter can be set in the same way a normal network adapter is set by right clicking the VPN client Virtual Network Adapter's icon in the Control Panel's [Network Connections] folder and selecting [Properties]. When a new Virtual Network Adapter was created, the user can set the protocol and clear any unneeded service bindings in the same manner as the user would for a physical network adapter. For details on the settings, please ask the administrator for the VPN server you want to connect to.

Jdsu Germany Port Devices Driver License Test

Virtual Network Adapter Network Properties.

Changing Advanced Settings

The following Virtual Network Adapter settings can be changed in the properties for a VPN client Virtual Network Adapter registered in the Windows Device Manager. Note that the VPN connection will be temporarily closed if these settings have been changed while the Virtual Network Adapter is being used for VPN communication.

Virtual Network Adapter Device Driver Setting Window.

Removing a Virtual Network Adapter

Jdsu Germany Port Devices Drivers

Once a Virtual Network Adapter has been added by the user, it remains in the system until the user removes it manually. There are two ways to remove a Virtual Network Adapter as shown below. These methods for removing a Virtual Network Adapter are equivalent.

• Removal using the Windows Device Manager
• Removal using the VPN Client Manager

Enabling and Disabling a Virtual Network Adapter

A Virtual Network Adapter registered in the system can be enabled or disabled at any time. When a new Virtual Network Adapter is created, it will be in the enabled state. When a Virtual Network Adapter is disabled, Windows handles it as though it has been disconnected from the system.

The Virtual Network Adapter enable/disable operations are performed from either the VPN Client Manager or the Windows Device Manager or [Network Connections] window.

Disabling a Virtual Network Adapter.

Messages Indicating that a Network Cable is Unplugged

Under Windows 2000 and later, when a new Virtual Network Adapter is created, an icon is displayed in the task tray at the lower right of the task bar and 'A network cable is unplugged.' message is displayed. This is normal operation.

When a VPN client uses a Virtual Network Adapter which is not connected to a VPN, the adapter operates in exactly the same state as when the network cable between a physical network adapter and the switching hub is disconnected. Therefore when a Virtual Network Adapter is used and a VPN is not connected, Windows handles that Virtual Network Adapter as a network adapter to which no network cable is attached. When a VPN connection is established using Virtual Network Adapter, the operation will start in the same fashion just as when a network adapter is connected to a switching hub by a network cable.

4.3.3 Managing the Version of the Virtual Network Adapter Device Driver

The version of the device driver of the Virtual Network Adapter created by the user is displayed in VPN Client Manager. This is the version of the device driver program file at the time the user registered the Virtual Network Adapter to Windows.

The version of the device driver of the Virtual Network Adapter is the same as the version of the VPN Client software used to create the Virtual Network Adapter. Even if a later version of the VPN Client software is installed thereafter, the version of the device driver of the previously created Virtual Network Adapter is not updated. To update the version of the device driver of the Virtual Network Adapter to the same version of the VPN Client software, use VPN Client Manager to select the Virtual Network Adapter to be updated and click [Reinstall Driver] on the [Virtual Adapter] menu.

4.3.4 Bridge Connection Between a Virtual Network Adapter and Physical Network Adapter

In SoftEther 1.0 (older version), it was possible to connect a virtual network to a physical network using the Windows function to create a bridge connection between the Virtual Network Adapter and physical network adapter.

Jdsu Germany Port Devices Driver

In SoftEther VPN, the user can create a local bridge connection between a Virtual Hub and an existing physical LAN with the functions provided in VPN Server and VPN Bridge. (For details, please refer to 3.6 Local Bridges.)Because the performance of the local bridge connection function of VPN Server / VPN Bridge is the same as or better than that when using VPN Client together with the bridge connection function of Windows XP or later, normally, there is no need to use the bridge connection function on the client side.

Jdsu Germany Port Devices Driver Updater

Under special circumstances or when the user wants to create a bridge connection between the Virtual Network Adapter and physical network adapter on the VPN Client side, a bridge connection can be created in the same way as the Virtual Network Adapter of SoftEther 1.0 (older version). In these cases, connect the Virtual Network Adapter and the physical network adapter using the same method for creating a bridge connection between two network adapters using the functions of Windows XP/Server 2003/Vista/7/8/Server 2008/Server 2012.

Using the Windows Function to Create a Bridge Connection
Between a Virtual Network Adapter and Physical Network Adapter.