CDCE(4)

NAME
cdce - USB Communication Device Class Ethernet driver

SYNOPSIS
cdce* at uhub? port ?

DESCRIPTION
The cdce driver provides support for USB Host-to-Host (aka USB-to-USB) bridges and USB-to-Ethernet adapters based on the USB Communication Device Class (CDC) and Ethernet subclass, including the following:

•   Acer Labs USB 2.0 Data Link
•   Anker A7611
•   DIEWU USB-DW8152
•   G.Mate YP3X00
•   Huawei E5573s-320s
•   Motorola USBNET
•   NetChip EthernetGadget
•   Prolific PL-2501
•   Realtek RTL8152B Ethernet controller
•   Sharp Zaurus

The USB bridge appears as a regular network interface on both sides, transporting Ethernet frames.

For more information on configuring this device, see ifconfig(8).

USB 1.x bridges support speeds of up to 12Mbps, and USB 2.0 speeds of up to 480Mbps.

Packets are received and transmitted over separate USB bulk transfer endpoints.

The cdce driver does not support different media types or options.

DIAGNOSTICS

cdce%d: no union descriptor The driver couldn't fetch an interface descriptor from the USB device. For a manually added USB vendor/product, the CDCE_NO_UNION flag can be tried to work around the missing descriptor.

cdce%d: no data interface

cdce%d: could not read endpoint descriptor

cdce%d: unexpected endpoint

cdce%d: could not find data bulk in/out For a manually added USB vendor/product, these errors indicate that the bridge is not compatible with the driver.

Also see usbnet(4) for diagnostics.

SEE ALSO
arp(4), intro(4), netintro(4), usb(4), usbnet(4), ifconfig.if(5), ifconfig(8) Universal Serial Bus Class Definitions for Communication Devices, http://www.usb.org/developers/devclass_docs/usbcdc11.pdf. Data sheet Prolific PL-2501 Host-to-Host Bridge/Network Controller, http://tech.prolific.com.tw/visitor/fcabdl.asp?fid=20679530.

HISTORY
The cdce device driver first appeared in OpenBSD 3.6 and NetBSD 3.0.

AUTHORS
-nosplit The cdce driver was written by Craig Boston <craig@tobuj.gank.org> based on the aue(4) driver written by Bill Paul <wpaul@windriver.com> and ported to OpenBSD by Daniel Hartmeier <dhartmei@openbsd.org>.

CAVEATS
Many USB devices notoriously fail to report their class and interfaces correctly. Undetected products might work flawlessly when their vendor and product IDs are added to the driver manually.