1
Hardware and Performance / Advice on ditching USB nic or wait for better support
« on: November 17, 2018, 02:51:02 pm »
So first before you start butchering me for running a USB nic.. We are talking about a home user here that used to run a crappy TP-Link router with OpenWRT.
I had serious issues with my previous router. Every streaming service was lagging and it was basically unusable.
So I had a J1900 based PC laying around (Q1900-ITX). Problem was that my case did not support external PCI-E cards so I could not add a nice Intel based Ethernet card to it.
Decided to give a USB nic a try since I only have 100Mbit down and 10Mbit up.
Got a RTL8153 Gigabit Ethernet USB3 Adapter and plugged it in. Works fine lag is gone but when I test my speed I only get 40Mbit down.
How could this be? USB3 is 5 Gbits right?
Anyway I'm prepared to get a new system with real nics, but it will probably be Realtek based too since I'm a home user and not willing to spend the big bucks...
Is it even worth it to buy a new system? I figure this is a driver issue and might be fixed in a newer freebsd release?
I had serious issues with my previous router. Every streaming service was lagging and it was basically unusable.
So I had a J1900 based PC laying around (Q1900-ITX). Problem was that my case did not support external PCI-E cards so I could not add a nice Intel based Ethernet card to it.
Decided to give a USB nic a try since I only have 100Mbit down and 10Mbit up.
Got a RTL8153 Gigabit Ethernet USB3 Adapter and plugged it in. Works fine lag is gone but when I test my speed I only get 40Mbit down.
How could this be? USB3 is 5 Gbits right?
Code: [Select]
ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ugen0.3: <Realtek USB 101001000 LAN> at usbus0, cfg=1 md=HOST spd=SUPER (5.0Gbps) pwr=ON (64mA)
Anyway I'm prepared to get a new system with real nics, but it will probably be Realtek based too since I'm a home user and not willing to spend the big bucks...
Is it even worth it to buy a new system? I figure this is a driver issue and might be fixed in a newer freebsd release?