USB to Gigabit Ethernet Problem Compilation (with raspberry pi 4 snapshot image)

I thought I should create new thread here, sorry if it's already discussed but after buying 3 separate USB 3.0 to Gigabit Adapter (all as WAN) I encounter multiple problem wtih Openwrt Snapshot (kernel 5.4.x) below :

  1. Generic USB 3.0 to Gigabit Ethernet with Realtek RTL8153 chipset
    Basically it's no great from the start, random disconnect and hardware not detected after getting wan
    activity, similar problem also occured when in Windows 10 but after updating the driver from realtek
    website the problem's gone. As for OpenWRT putting the adapter in USB 2.0 port solve the problem
    although for those with fast gigabit internet, the speeds will be halved to max USB 2.0 speed.
  2. Generic USB 3.0 to Gigabit Ethernet with AX88179 chipset
    At first all seems well but after a day or more (random but usually between 1 day) the WAN side
    failed to get DHCP Lease and can only resolved with usbreset command, unplugging and
    replugging the USB Adapter, or rebooting the pi.
  3. Tp-Link UE-300 USB 3.0 to Gigabit Ethernet with RTL8153
    I had better experience with this dongle, but after a week or more (at least better than the previous
    AX88179) similar problem occured when getting DHCP lease :
    Sun Jul 26 13:26:18 2020 daemon.notice netifd: wan (1702): udhcpc: sending renew to 10.x.x.x
    Sun Jul 26 13:26:19 2020 daemon.notice netifd: wan (1702): udhcpc: lease of 10.x.x.x obtained, 
    lease time 3600
    
    the solution also the same like previous adapter, usbreset, unplugging, or rebooting the pi.

I don't have device with stable kernel (4.9) to test (usually rpi 3b), but using Intel NUC and OPNsense with RTL8153 generic adapter seems stable enough, I do plan to use OpenWRT on x86 to test if in the future when I have spare time.

hello i have rl8152 usb 3 on a rpi4 without problem for me , but the wan lease is not unlimited

I have an i-tec with RTL8153 working fine since April.
I am using pppoe and dhcpv6, however I don't see any issue from the logs you attached. You sent a RENEW and next second you received the lease.

This is weird, as you know I am using a UE300 too. My RPi4 has been up and running for 25 days now on a 5.4 kernel. No need to reboot, reset USB or unplug the USB NIC. What's the problem with the DCHP lease? Would you be more specific? Is it forgetting the IP and you it is not renewing automatically?

For generic USB , I assume (or what I believe at least) the problem lies more than just chipset but other component that makes them. The generic RTL8153 and AX88179 both use similar housing which probably the other components outsourced from similar factory.

As for the UE300, maybe other combination like ISP, kernel version, and add-ins? I use layer_cake in SQM_QOS, other than that basic like luci_statistics and drivers for rtc.

When using AX88179, after a day I got similar message like above, but it failed to renew lease... on UE300 (From observation about 2 weeks more it only occured 2 times, usually on weekend but the only things strikes me is that it happened just when I got home usually (seeing from the log). bandwidth statistics usually low to none but when I got home bandwidth surged (although not huge) and that's when things get awry.

Zero issues... even ripped one open (don't attempt it)... damn they run cool...

running other usb devices / fancy drivers / services by any chance / extension cable or nearby RF?

If you saw the message lease of 10.x.x.x obtained, lease time 3600 in your logs, it means the packet was received and examined by OpenWrt. So it has passed already the part where a bad driver or faulty card would cause problems.

1 Like

no other usb devices than the usb card, the raspberry pi 4 itself positioned near ISP modem. but there are other cable (including PoE to AP) nearby.

I do plan to wait for few more weeks and observe if the problem persists or not, and maybe try switching the USB ethernet as LAN port and leaving the WAN side to native LAN, is it a good idea?

I see, that's also explained when using generic AX88179 in the interfaces I don't get WAN side IP (the 10.x.x.x part) and the error a bit different. I try to look for other possibilities then.

Is not a bad idea. Main reason to keep your USB NIC as WAN is to have access to your LAN interface for admin purposes, you can use your RPi4's WiFi for this purpose, tho'.

In any case, when I used my AX88179 I had no problems at all. My Pi is close to my cable modem right under my APs —like 30 cm apart of each other— and right besides a microwave oven, which is less than ideal and, I have none of your problems.

1 Like

hi guys,
I'm running for months a PI4 + Buster image + r8153 USB adapter, sniffing all my data (usb 3.0 port), with no disconnections or issues (ntop-ng on it).
And decide to try an openwrt image on it rpi-4_snapshot_1.7.66-7_r14267. BUILD_ID="r14267-18fbb9aa21"
So the HW is the same, but after a day playing, I came up with the infamous disappearances/instability listed above.
I performed

opkg update
opkg install kmod-usb-net-rtl8152

But it doesn't seem to be better.

[ 602.048544] usb 1-1: USB disconnect, device number 2
[ 602.350168] usb 1-1.2: device not accepting address 5, error -62
[ 602.367037] usb 1-1-port2: couldn't allocate usb_device

Any ideas?
tx

community build... to clarify...

  1. the build already has the driver installed
  2. i'd advise you to either remove all 'usbmode switch / qmi / lte / otg" style packages or test with an official build to be absolutely certain that your issues are not the result of package combinations within the build...

if I had to guess though... i'd say it's not build related... and more likely as stated above... related to particular device/chip / use case or environmental/hw combinations/subtlties/factors...

what is the exact adapter you are using? and exact rpi model?

Tx wulfy23

root@pi4_openwrt /34# cat /proc/cpuinfo | grep -A3 Revision
Revision : c03112
Serial : 100000004cbdd30d
Model : Raspberry Pi 4 Model B Rev 1.2

PI4B 4Gb, the adapter is the black chinese no-name one.. like the one from this post https://forum.openwrt.org/t/update-kmod-usb-net-rtl8152-driver-to-avoid-usb-3-0-to-gigabit-lan-issues/65466/14

What I found strange is that the exact same HW configuration on Buster image works with no issues, hence my suspicions in param/config.

which image would you like me to try (can u share a link, plz?)
tx again!

1 Like

in this case 99.999% sure it's not build related... and doubt using the official image assist... ( although particular package conflicts are still in the picture )...

official images ( i.e. to test with a bare minimum package set ) but again... fairly confident it will yeild identical outcomes...

note: there are two version of the pi4b-4gb

cat /proc/cpuinfo  | grep -A3 Revision
comparing these with yours or yours on buster may yeild something
/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0
################################################ /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0
authorized
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_02
ep_81
ep_83
modalias
net
power
subsystem
supports_autosuspend
uevent
drwxr-xr-x    7 root     root             0 Aug 29 01:21 .
drwxr-xr-x    6 root     root             0 Jan  1  1970 ..
-rw-r--r--    1 root     root          4096 Aug 29 01:28 authorized
-r--r--r--    1 root     root          4096 Aug 29 01:28 bAlternateSetting
-r--r--r--    1 root     root          4096 Aug 29 01:28 bInterfaceClass
-r--r--r--    1 root     root          4096 Aug 29 01:28 bInterfaceNumber
-r--r--r--    1 root     root          4096 Aug 29 01:28 bInterfaceProtocol
-r--r--r--    1 root     root          4096 Aug 29 01:28 bInterfaceSubClass
-r--r--r--    1 root     root          4096 Aug 29 01:28 bNumEndpoints
lrwxrwxrwx    1 root     root             0 Aug 29 01:28 driver -> ../../../../../../../../../../bus/usb/drivers/r8152
drwxr-xr-x    3 root     root             0 Aug 29 01:28 ep_02
drwxr-xr-x    3 root     root             0 Aug 29 01:28 ep_81
drwxr-xr-x    3 root     root             0 Aug 29 01:28 ep_83
-r--r--r--    1 root     root          4096 Aug 29 01:28 modalias
drwxr-xr-x    3 root     root             0 Aug 29 01:21 net
drwxr-xr-x    2 root     root             0 Aug 29 01:28 power
lrwxrwxrwx    1 root     root             0 Aug 29 01:28 subsystem -> ../../../../../../../../../../bus/usb
-r--r--r--    1 root     root          4096 Aug 29 01:28 supports_autosuspend
-rw-r--r--    1 root     root          4096 Aug 29 01:28 uevent
############################################## netsub: /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/addr_assign_type
3
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/addr_len
6
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/address
00:11:32:99:99:99
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/broadcast
ff:ff:ff:ff:ff:ff
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/carrier
1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/carrier_changes
4
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/carrier_down_count
2
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/carrier_up_count
2
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/dev_id
0x0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/dev_port
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/dormant
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/duplex
full
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/flags
0x1003
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/gro_flush_timeout
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/ifalias
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/ifindex
4
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/iflink
4
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/link_mode
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/mtu
1500
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/name_assign_type
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/napi_threaded
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/netdev_group
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/operstate
up
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/phys_port_id
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/phys_port_name
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/phys_switch_id
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/proto_down
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/speed
1000
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/tx_queue_len
1000
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/type
1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/net/eth1/uevent
INTERFACE=eth1
IFINDEX=4
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../authorized
1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../avoid_reset_quirk
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bConfigurationValue
1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bDeviceClass
00
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bDeviceProtocol
00
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bDeviceSubClass
00
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bMaxPacketSize0
9
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bMaxPower
256mA
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bNumConfigurations
2
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bNumInterfaces
 1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bcdDevice
3000
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../bmAttributes
a0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../busnum
2
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../configuration
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../descriptors
EgEAAwAAAAlXIwEGADABAgYCCQI5AAEBAKAgCQQAAAP//wAABwWBAgAEAAYwAwAAAAcFAgIABAAG
MAMAAAAHBYMDAgAIBjAAAAIACQJiAAICAKAgCQQAAAECBgAFBSQAEAEFJAYAAQ0kDwMAAAAA6gUA
AAAHBYMDEAAIBjAAAAgACQQBAAAKAAAACQQBAQIKAAAEBwWBAgAEAAYwAwAAAAcFAgIABAAGMAMA
AAA=
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../dev
189:129
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../devnum
2
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../devpath
2
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../devspec
(null)
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../idProduct
0601
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../idVendor
2357
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../ltm_capable
yes
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../manufacturer
TP-LINK
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../maxchild
0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../product
USB 10/100/1000 LAN
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../quirks
0x0
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../removable
unknown
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../remove
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../rx_lanes
1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../serial
000001000000
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../speed
5000
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../tx_lanes
1
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../uevent
MAJOR=189
MINOR=129
DEVNAME=bus/usb/002/002
DEVTYPE=usb_device
DRIVER=usb
PRODUCT=2357/601/3000
TYPE=0/0/0
BUSNUM=002
DEVNUM=002
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../urbnum
167032
#################### /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/../version
 3.00

im using rpi4 with rlt8152 usb 3 1000mbits without probleme

in the context of this thread... not stating the actual adapter is of little benefit...

was also reading other posts, about link power mgt or other
eg. disable link power mgt? usbcore.quirks=0bda:8153:k ? how would I do this on the PI4 openwrt to see if any diff?

or things about Link Negotiation:auto or not... how to change all those params?

note, I have 2 of those adapaters, let me play & see if any difference as well ...
tx

yeah... you could try the quirks but to be honest... when troubleshooting things like this you are best to start broad and work your way down...

is buster 32bit? there is 32bit openwrt for the pi... well worth a comparison imho... especially any differences in sysfs/ethtool regarding usb/that nic...