Review on 🔌 TP-Link UE300 USB to Ethernet Adapter – Foldable USB 3.0 LAN Network Adapter for Desktop, Laptop, Apple MacBook, Linux – Supports Windows 10/8.1/8/7/Vista/XP & Gigabit Ethernet (10/100/1000) by Brandon Plowden

If you're using Raspbian, the old 4.19 kernel uses the old cdc_ether driver to run it, which can be problematic. You need to add a file to /etc/modprobe.d so the r8152 driver can talk to it. In the current 5.4 kernel on Raspbian it is plug and play. plug it in and bam, eth1. Presumably this will work the same on an x86 box. You may not need 5.4, this is just a simple test for me. It definitely works, and whatever happens next should definitely work. A nudge may be required for earlier kernels. This is a push: create a rtl_usb.conf file and put it in /etc/modprobe. d (on Debian derivatives) from. Specify exactly that in the file without quotes"alias usb: 4 (and above) have built-in ID codes 2357:0601 for this adapter. The r8152 driver should take over instead of the cdc_ether driver (which I understand doesn't work very well). This spell will call it right away on 4.19 for Raspberry Pi and will probably work on any latest Debian distro on any architecture. . Other distros like Arch might have different modprobe setup methods but the line above should make it work. No, I don't understand what that means either. The numbers are vendor and product codes, but the rest of that line is gibberish to me. Once you've updated to at least version 5.4, you can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. The r8152 driver should take over instead of the cdc_ether driver (which as far as I know doesn't work very well). This spell will instantly bring it up to 4.19 for Raspberry Pi and will probably work on any latest Debian distribution on any architecture. . Other distros like Arch may have different modprobe setup methods, but the line above should get it working. No, I don't understand what that means either. The numbers are manufacturer and product codes, but the rest of that line is gibberish to me. Once you have updated to at least version 5.4, you can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. and will probably work with any recent Debian distribution on any architecture. Other distros like Arch may have different modprobe setup methods, but the line above should get it working. No, I don't understand what that means either. The numbers are manufacturer and product codes, but the rest of that line is gibberish to me. Once you have updated to at least version 5.4, you can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. and will probably work with any recent Debian distribution on any architecture. Other distros like Arch may have different modprobe setup methods, but the line above should get it working. No, I don't understand what that means either. The numbers are manufacturer and product codes, but the rest of that line is gibberish to me. Once you have updated to at least version 5.4, you can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. You can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. You can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. 4 (and higher) have built-in ID codes 2357:0601 for this adapter. You can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. 4 (and higher) have built-in ID codes 2357:0601 for this adapter. You can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. 4 (and higher) have built-in identification codes 2357:0601 for this adapter. 4 (and higher) have built-in ID codes 2357:0601 for this adapter. You can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter. 4 (and higher) have built-in identification codes 2357:0601 for this adapter. 4 (and higher) have built-in ID codes 2357:0601 for this adapter. You can delete this file and run depmod -a again. Driver version 5.4 (and higher) have built-in identification codes 2357:0601 for this adapter.