1.\" Copyright (c) 2004 Daniel Hartmeier 2.\" All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 8.\" - Redistributions of source code must retain the above copyright 9.\" notice, this list of conditions and the following disclaimer. 10.\" - Redistributions in binary form must reproduce the above 11.\" copyright notice, this list of conditions and the following 12.\" disclaimer in the documentation and/or other materials provided 13.\" with the distribution. 14.\" 15.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 16.\" "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 17.\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 18.\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 19.\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 21.\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 22.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 23.\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 25.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 26.\" POSSIBILITY OF SUCH DAMAGE. 27.\" 28.\" $NetBSD: cdce.4,v 1.4 2004/12/08 18:35:56 peter Exp $ 29.\" 30.Dd May 3, 2024 31.Dt CDCE 4 32.Os 33.Sh NAME 34.Nm cdce 35.Nd "USB Communication Device Class Ethernet (CDC ECM/NCM) driver" 36.Sh SYNOPSIS 37To compile this driver into the kernel, 38place the following lines in your 39kernel configuration file: 40.Bd -ragged -offset indent 41.Cd "device uhci" 42.Cd "device ohci" 43.Cd "device usb" 44.Cd "device miibus" 45.Cd "device uether" 46.Cd "device cdce" 47.Ed 48.Pp 49Mobile Devices (eg. Huawei E3372, E5573 and others) 50may need additionally the u3g command port: 51.Bd -ragged -offset indent 52.Cd "device ucom" 53.Cd "device u3g" 54.Ed 55.Pp 56Alternatively, to load the driver as a 57module at boot time, place the following line in 58.Xr loader.conf 5 : 59.Bd -literal -offset indent 60if_cdce_load="YES" 61.Ed 62.Sh DESCRIPTION 63The 64.Nm 65driver provides support for USB Host-to-Host (aka USB-to-USB) and 66USB-to-Ethernet bridges based on the USB Communication Device Class 67Ethernet Control Model (CDC ECM) and Network Control Model (CDC NCM) 68specifications. 69It also provides device-side CDC ECM support. 70.Pp 71The USB bridge appears as a regular network interface on both sides, 72transporting Ethernet frames. 73.Pp 74For more information on configuring this device, see 75.Xr ifconfig 8 . 76.Pp 77USB 1.x bridges support speeds of up to 12Mbps, and USB 2.0 speeds of 78up to 480Mbps. 79.Pp 80Packets are 81received and transmitted over separate USB bulk transfer endpoints. 82.Pp 83The 84.Nm 85driver does not support different media types or options. 86.Pp 87Mobile 88.Nm 89Network Devices may need a connect command sequence via u3g 90serial command port before they activate the NCM/ECM/ACM network 91interface. Example: echo 'AT^NDISUP=1,1,"internet"' > /dev/cuaU[0].0, 92where "internet" is your providers apn name. 93.Sh HARDWARE 94The following devices are supported by the 95.Nm 96driver: 97.Pp 98.Bl -bullet -compact 99.It 100Prolific PL-2501 Host-to-Host Bridge Controller 101.It 102Sharp Zaurus PDA 103.It 104Terayon TJ-715 DOCSIS Cable Modem 105.It 106Huawei 3G/4G LTE (eg. E3372, E5573) and other mobile network devices 107.El 108.Sh DIAGNOSTICS 109.Bl -diag 110.It "cdce%d: no union descriptor" 111The driver could not fetch an interface descriptor from the USB 112device. 113For a manually added USB vendor/product, the CDCE_NO_UNION flag 114can be tried to work around the missing descriptor. 115.It "cdce%d: no data interface" 116.It "cdce%d: could not read endpoint descriptor" 117.It "cdce%d: unexpected endpoint" 118.It "cdce%d: could not find data bulk in/out" 119For a manually added USB vendor/product, these errors indicate 120that the bridge is not compatible with the driver. 121.It "cdce%d: watchdog timeout" 122A packet was queued for transmission and a transmit command was 123issued, however the device failed to acknowledge the transmission 124before a timeout expired. 125.It "cdce%d: no memory for rx list -- packet dropped!" 126Memory allocation through MGETHDR or MCLGET failed, the system 127is running low on mbufs. 128.It "cdce%d: abort/close rx/tx pipe failed" 129.It "cdce%d: rx/tx list init failed" 130.It "cdce%d: open rx/tx pipe failed" 131.It "cdce%d: usb error on rx/tx" 132.El 133.Sh SEE ALSO 134.Xr arp 4 , 135.Xr cdceem 4 , 136.Xr intro 4 , 137.Xr ipheth 4 , 138.Xr netintro 4 , 139.Xr urndis 4 , 140.Xr usb 4 , 141.Xr ucom 4 , 142.Xr u3g 4 , 143.Xr ifconfig 8 144.Rs 145.%T "Universal Serial Bus Class Definitions for Communication Devices" 146.%U http://www.usb.org/developers/devclass_docs/usbcdc11.pdf 147.Re 148.Rs 149.%T "Data sheet Prolific PL-2501 Host-to-Host Bridge/Network Controller" 150.%U http://tech.prolific.com.tw/visitor/fcabdl.asp?fid=20679530 151.Re 152.Sh HISTORY 153The 154.Nm 155device driver first appeared in 156.Ox 3.6 , 157.Nx 3.0 158and 159.Fx 6.0 . 160.Sh AUTHORS 161.An -nosplit 162The 163.Nm 164driver was written by 165.An Craig Boston Aq Mt craig@tobuj.gank.org 166based on the 167.Xr aue 4 168driver written by 169.An Bill Paul Aq Mt wpaul@windriver.com 170and ported to 171.Ox 172by 173.An Daniel Hartmeier Aq Mt dhartmei@openbsd.org . 174.Sh CAVEATS 175Many USB devices notoriously fail to report their class and interfaces 176correctly. 177Undetected products might work flawlessly when their vendor and product IDs 178are added to the driver manually. 179