Electronics

StarTech.com USB C to Gigabit Ethernet Adapter - White - USB 3.1 to RJ45 LAN Network Adapter - USB Type C to Ethernet (US1GC30W)

★★★★4.3·44 ratings

The StarTech white 5 Gbps USB-C to Gigabit network adapter is compatible for use with desktop computers or notebooks. The StarTech US1GC30 white 5 Gbps USB-C to Gigabit network adapter offers a reliable network connection without having to install any drivers. Its compact, lightweight design fits nicely into any carrying case that lets you carry it with you wherever you go. It supports full Gigabit bandwidth by harnessing the performance of USB 3.1 Gen 1 and lets you access large files over the network at Gigabit speeds. Plug-and-play installation helps for a hassle-free setup, and native driver support ensures quick setup. Network adapter adds a Gigabit Ethernet network connection to your computer through the latest USB 3.1 Gen 1 technology and USB type-C port. Dimensions: 0.6"H x 8.3"W x 1"D. Data transfer rate: 5 Gbps. Jumbo frame support: 9K. Interfaces/ports: 1 x USB 3.1 USB type-C (24 pin, Gen 1, 5 Gbps) male, 1 x RJ-45 female. Media type supported: Twisted pair. Network technology: 10/100/1000Base-T. Chipset: Realtek RTL8153. Weight: 0.8 oz. Operating system compatibility: Windows 10, 8.1, 8, 7, Vista, XP, Windows Server 2012, 2008 R2, 2003, Mac OS 10.6-10.11, Linux Kernel 2.6.25- 3.17.0. USB powered supply provides the necessary power. Environmental conditions: 0- 70 deg C operating,-10- 80 deg C storage, 5- 90% RH humidity. Thunderbolt 3-port compatible, powered directly from the USB port, has built-in checksum and large send offload, wake-on-LAN support. Meets RoHS, FCC and CE certifications and standards. 2 year warranty.

ASIN: B013TPI66C
Embedding: CLIP ViT-L/14 · 768d
Distance metric: cosine
Doc fetch: 2mscache hitGET /v2/namespaces/amazon-products/documents/B013TPI66C
Similar query: 42msnearest_to_id → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query asks Layer for nearest neighbors of the stored product vector — queries don't go through the doc cache, so no cache header is set.

Visually similar