Realtek RTL8157 5 GbE adapters with 10 Gb USB interface - Wavlink, WisdPi

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

agreenbhm

New Member
Nov 22, 2024
7
1
3
I asked and got this reply. Not sure if there is any difference or if they are doing some listings magic on Amazon.
Lol, their response makes no sense at all. Sounds like SEO or whatever the Amazon equivalent is, like you suggested.
 

agreenbhm

New Member
Nov 22, 2024
7
1
3
Been running my two adapters via iperf3 for 5 minutes straight now and am getting sustained 4.7Gbps and they're a little warm (not bad at all). I had all kinds of weirdness plugged into a Belkin USB-C hub that I've decided is defective (and have an Anker alternative coming later today). Plugged directly into my systems the NICs are doing great.

Edit: Ran it for an hour straight and averaged 4.7 Gbps without a single drop.
 
Last edited:

tusk9541

Member
Nov 23, 2022
65
75
18
Both of mine show "Rev. A", though only the second one was bought under the "341" listing; the other was from AliExpress which didn't list anything specific.
Yeah, both are "Rev. a", but the difference was in the "-A" at the end of the model name, not revision:

340G: WL-NWU340G-A Rev. a
341G: WL-NWU340G Rev. a

So far the 341G working perfectly, no disconnections at all when reconnecting the cable, or turning off/on the TB4 hub it's connected to.
 

agreenbhm

New Member
Nov 22, 2024
7
1
3
Yeah, both are "Rev. a", but the difference was in the "-A" at the end of the model name, not revision:

340G: WL-NWU340G-A Rev. a
341G: WL-NWU340G Rev. a

So far the 341G working perfectly, no disconnections at all when reconnecting the cable, or turning off/on the TB4 hub it's connected to.
I see. In that case it sounds like mine are both 341G.
 

MountainBofh

Beating my users into submission
Mar 9, 2024
385
277
63
I did some brief testing on an AMD 8845HS mini computer ( Beelink SER8) running Windows 10 LTSC.

I was limited by the 2.5gb switch I was plugged into, but both internet speeds and iperf3 tests were at 2.5gb, and in the hour I used the card to surf the net no issues were noticed.

I hoping to run my data center test tomorrow.
 

jerrythea

Member
Sep 12, 2022
37
12
8
So it definitely looks like there are major issues using these Realtek 8157 based USB dongles with NFS.

I have been running the exact same configuration, but with OWC 10 GbE TB3 adapters, and the systems are rock stable.

The performance is a a bit better (10 GbE versus 5 GbE), but the price is wildly higher.

However, it looks like the only stable upgrade option from 2.5 GbE is to go to the older, more stable, 10 GbE TB3 solution.

A simple low-cost USB-powered set of fans is a good idea, as these TB3 devices tend to get a bit hot.

There are a bunch of OWC 10 GbE open-box units available, since a bunch of people end up returning these.

At about $145 each (10 GbE OWC open-box), compared to the $35 each (WisdPi 5 GbE), they are about 4 times the cost.

But a lower cost solution that causes multiple nodes in a Proxmox cluster to randomly lock-up and hang isn't much of a solution!
 

jerrythea

Member
Sep 12, 2022
37
12
8
The solution causes NFS servers on this network interface to lock up the kernel.

same configuration with OWC TB3 10 GbE adapters have been stable for over a week.
 

jerrythea

Member
Sep 12, 2022
37
12
8
I tried most recent kernels on both Proxmox 8.2 (optin to 6.11) and Fedora (newer 6.11).

might be an NFS bug, but unlikely since a faster Network dongle (TB3) has no issues, nor does a slower 2.5 GBs Realtek dongle.
 

tusk9541

Member
Nov 23, 2022
65
75
18
FWIW the new one I got still running fine, no problems at all. WL-NWU340G Rev. a which was labeled "341G" at Amazon. I connect and disconnect my laptop every day and it reconnects fine every time (same other hardware as in the OP). It might be that the earlier revision had some issues that aren't related to the realtek chip.
 

jerrythea

Member
Sep 12, 2022
37
12
8
I was trying to use this in a server environment for a Proxmox cluster based on NUCs.

they worked fine for most requirements, but when I hosted my NFS shares via these dongles the Linux kernel would lock up pretty consistently.

the exact same configuration using 2.5 GbE dongles was rock solid.

the exact same configuration using 10 GbE TB3 dongles is also rock solid.

the problem with Realtek is that their drivers are delivered as source code and seem to have no actual QA or technical support.

the community ends up doing that work for them.
 

lustyffh

New Member
Nov 28, 2016
1
0
1
43
got this one today. made it to work in a normal USB port in ubuntu 6.8 with the official driver. However, I found out that it's not being recognised in the Thunderbolt ports. I have a dock named Acasis DS-9002 and the power led on the realtek card simply doesn't light up. Also, no indication of a new device in dmesg. Luckily, that box also has a normal 10G USB port which worked flawlessly. Anyone tried it in Thunderbolt ports under Windows?
 
Last edited:

jerrythea

Member
Sep 12, 2022
37
12
8
Yet another symptom of a very early product with inconsistent driver support.

I am able to use it connected to a Dell TB4 Dock connected to a Dell computer.

There is a small performance dip compared to direct connection.

I have been studying this a bit and watching some youtube videos.

Apparently anytime a device is attached to a TB4 dock there is going to be performance loss.

The two alternative that do not have any performance losses are:
1. TB5 Docks when connected to support Macbook Pro M4 Pro
2. Ivanki has a unique TB4 dock that has two separate connections to a host device (2 TB4 host ports).
- This ends up making the dock behave as two separate docks.
- It is even possible to use a single dock connected to 2 computers.
 

Tinkerer

Member
Sep 5, 2020
89
28
18
I ordered 6 of the Wavlink and recieved model: WL-NWU340G Rev.A.

I cannot get them to work in Linux. Doesn't matter what distro I try, I tested with Archlinux on 6.10, 6.11 and 6.12. I tried on Ubuntu 24.04. They are meant for 6 node Proxmox cluster which runs a 6.8 kernel.

I tried compiling the kernels straight from the Realtek support page, on PVE I use these:

Often a ping between 2 of these is enough for the connection to drop. But when it doesn't and I start iperf3, it prints one line with a few KB, the next line is 0.0 bytes. Either one side driver crashes.

I am mailing support but they are not replying. It seems while people experience instability on Windows, it seems to be stable for me (Windows 11). Also MacOS seems to work fine.

Part of dmesg output when the driver loads and crashes:

Code:
[Sun Feb 16 08:08:10 2025] r8152-cfgselector 3-1: USB disconnect, device number 2
[Sun Feb 16 08:08:10 2025] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Sun Feb 16 08:08:10 2025] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Sun Feb 16 08:08:10 2025] usb 3-1: new SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd
[Sun Feb 16 08:08:10 2025] usb 3-1: New USB device found, idVendor=0bda, idProduct=8157, bcdDevice=30.00
[Sun Feb 16 08:08:10 2025] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[Sun Feb 16 08:08:10 2025] usb 3-1: Product: USB 10/100/1G/2.5G/5G LAN
[Sun Feb 16 08:08:10 2025] usb 3-1: Manufacturer: Realtek
[Sun Feb 16 08:08:10 2025] usb 3-1: SerialNumber: 0003000001
[Sun Feb 16 08:08:10 2025] cdc_ncm 3-1:2.0: MAC-Address: 80:3f:5d:fd:bb:1b
[Sun Feb 16 08:08:10 2025] cdc_ncm 3-1:2.0: setting rx_max = 16384
[Sun Feb 16 08:08:10 2025] cdc_ncm 3-1:2.0: setting tx_max = 16384
[Sun Feb 16 08:08:10 2025] cdc_ncm 3-1:2.0 eth0: register 'cdc_ncm' at usb-0000:01:00.0-1, CDC NCM (NO ZLP), 80:3f:5d:fd:bb:1b
[Sun Feb 16 08:08:10 2025] cdc_ncm 3-1:2.0 eth0: unregister 'cdc_ncm' usb-0000:01:00.0-1, CDC NCM (NO ZLP)
[Sun Feb 16 08:08:10 2025] r8152-cfgselector 3-1: reset SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd
[Sun Feb 16 08:08:10 2025] r8152 3-1:1.0: ram code version is wrong 0000(0013
[Sun Feb 16 08:08:11 2025] r8152 3-1:1.0 eth0: v2.19.2 (2024/10/21)
[Sun Feb 16 08:08:11 2025] r8152 3-1:1.0 eth0: This product is covered by one or more of the following patents:
                                   US6,570,884, US6,115,776, and US6,327,625.
[Sun Feb 16 08:08:11 2025] r8152-cfgselector 3-1: reset SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd
[Sun Feb 16 08:08:11 2025] r8152 3-1:1.0: ram code version is wrong 0000(0013
[Sun Feb 16 08:08:11 2025] r8152 3-1:1.0 eth0: v2.19.2 (2024/10/21)
[Sun Feb 16 08:08:11 2025] r8152 3-1:1.0 eth0: This product is covered by one or more of the following patents:
                                   US6,570,884, US6,115,776, and US6,327,625.
[Sun Feb 16 08:08:11 2025] r8152 3-1:1.0 enx803f5dfdbb1b: renamed from eth0
[Sun Feb 16 08:08:18 2025] r8152-cfgselector 3-1: USB disconnect, device number 3
[Sun Feb 16 08:08:18 2025] usb 3-1: new SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
[Sun Feb 16 08:08:18 2025] usb 3-1: New USB device found, idVendor=0bda, idProduct=8157, bcdDevice=30.00
[Sun Feb 16 08:08:18 2025] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[Sun Feb 16 08:08:18 2025] usb 3-1: Product: USB 10/100/1G/2.5G/5G LAN
[Sun Feb 16 08:08:18 2025] usb 3-1: Manufacturer: Realtek
[Sun Feb 16 08:08:18 2025] usb 3-1: SerialNumber: 0003000001
[Sun Feb 16 08:08:18 2025] cdc_ncm 3-1:2.0: MAC-Address: 80:3f:5d:fd:bb:1b
[Sun Feb 16 08:08:18 2025] cdc_ncm 3-1:2.0: setting rx_max = 16384
[Sun Feb 16 08:08:18 2025] cdc_ncm 3-1:2.0: setting tx_max = 16384
[Sun Feb 16 08:08:18 2025] cdc_ncm 3-1:2.0 eth0: register 'cdc_ncm' at usb-0000:01:00.0-1, CDC NCM (NO ZLP), 80:3f:5d:fd:bb:1b
[Sun Feb 16 08:08:18 2025] cdc_ncm 3-1:2.0 eth0: unregister 'cdc_ncm' usb-0000:01:00.0-1, CDC NCM (NO ZLP)
[Sun Feb 16 08:08:18 2025] r8152-cfgselector 3-1: reset SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
[Sun Feb 16 08:08:18 2025] r8152 3-1:1.0: ram code version is wrong 0000(0013
[Sun Feb 16 08:08:18 2025] r8152 3-1:1.0 eth0: v2.19.2 (2024/10/21)
[Sun Feb 16 08:08:18 2025] r8152 3-1:1.0 eth0: This product is covered by one or more of the following patents:
                                   US6,570,884, US6,115,776, and US6,327,625.
[Sun Feb 16 08:08:18 2025] r8152-cfgselector 3-1: reset SuperSpeed Plus Gen 2x1 USB device number 4 using xhci_hcd
[Sun Feb 16 08:08:19 2025] r8152 3-1:1.0: ram code version is wrong 0000(0013
[Sun Feb 16 08:08:19 2025] r8152 3-1:1.0 eth0: v2.19.2 (2024/10/21)
[Sun Feb 16 08:08:19 2025] r8152 3-1:1.0 eth0: This product is covered by one or more of the following patents:
                                   US6,570,884, US6,115,776, and US6,327,625.
[Sun Feb 16 08:08:19 2025] r8152 3-1:1.0 enx803f5dfdbb1b: renamed from eth0
I also captured an actual driver crash:

Code:
[Sun Feb 16 08:20:32 2025] r8152-cfgselector 3-1: USB disconnect, device number 2
[Sun Feb 16 08:20:32 2025] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Sun Feb 16 08:20:32 2025] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[Sun Feb 16 08:20:32 2025] usb 3-1: new SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd
[Sun Feb 16 08:20:32 2025] usb 3-1: New USB device found, idVendor=0bda, idProduct=8157, bcdDevice=30.00
[Sun Feb 16 08:20:32 2025] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[Sun Feb 16 08:20:32 2025] usb 3-1: Product: USB 10/100/1G/2.5G/5G LAN
[Sun Feb 16 08:20:32 2025] usb 3-1: Manufacturer: Realtek
[Sun Feb 16 08:20:32 2025] usb 3-1: SerialNumber: 0003000001
[Sun Feb 16 08:20:32 2025] cdc_ncm 3-1:2.0: MAC-Address: 80:3f:5d:fd:bb:1b
[Sun Feb 16 08:20:32 2025] cdc_ncm 3-1:2.0: setting rx_max = 16384
[Sun Feb 16 08:20:32 2025] cdc_ncm 3-1:2.0: setting tx_max = 16384
[Sun Feb 16 08:20:32 2025] cdc_ncm 3-1:2.0 eth0: register 'cdc_ncm' at usb-0000:01:00.0-1, CDC NCM (NO ZLP), 80:3f:5d:fd:bb:1b
[Sun Feb 16 08:20:32 2025] cdc_ncm 3-1:2.0 eth0: unregister 'cdc_ncm' usb-0000:01:00.0-1, CDC NCM (NO ZLP)
[Sun Feb 16 08:20:33 2025] r8152-cfgselector 3-1: reset SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: ram code version is wrong 0000(0013
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -71
[Sun Feb 16 08:20:33 2025] ------------[ cut here ]------------
[Sun Feb 16 08:20:33 2025] WARNING: CPU: 2 PID: 25 at /var/lib/dkms/r8152/2.19.2/build/src/r8152.c:1385 wait_tgphy_cmd_ready+0x74/0xc0 [r8152]
[Sun Feb 16 08:20:33 2025] Modules linked in: ceph libceph netfs ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter sctp ip6_udp_tunnel udp_tunnel nf_tables nvme_fabrics nvme_keyring bonding tls softdog sunrpc binfmt_misc nfnetlink_log nfnetlink intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 r8152(OE) aesni_intel crypto_simd cdc_mbim cryptd input_leds cdc_wdm hid_generic usbkbd usbmouse amdgpu usbhid snd_hda_codec_hdmi hid amdxcp drm_exec gpu_sched snd_hda_intel drm_buddy snd_intel_dspcfg drm_suballoc_helper drm_ttm_helper snd_intel_sdw_acpi ttm snd_hda_codec drm_display_helper snd_hda_core snd_hwdep snd_pcm cec hp_wmi sparse_keymap ipmi_devintf snd_timer platform_profile rapl rc_core snd i2c_algo_bit wmi_bmof soundcore ccp pcspkr ipmi_msghandler k10temp mac_hid zfs(PO) spl(O) vhost_net vhost vhost_iotlb tap efi_pstore dmi_sysfs ip_tables x_tables autofs4 cdc_ncm cdc_ether
[Sun Feb 16 08:20:33 2025]  usbnet mii xfs btrfs blake2b_generic xor raid6_pq libcrc32c xhci_pci nvme xhci_pci_renesas video ehci_pci r8169 crc32_pclmul ehci_hcd nvme_core xhci_hcd ahci realtek i2c_piix4 nvme_auth libahci wmi gpio_amdpt
[Sun Feb 16 08:20:33 2025] CPU: 2 PID: 25 Comm: kworker/2:0 Tainted: P           OE      6.8.12-8-pve #1
[Sun Feb 16 08:20:33 2025] Hardware name: HP HP ProDesk 405 G6 Desktop Mini PC/872E, BIOS S27 Ver. 02.15.01 04/25/2024
[Sun Feb 16 08:20:33 2025] Workqueue: events_long rtl_hw_phy_work_func_t [r8152]
[Sun Feb 16 08:20:33 2025] RIP: 0010:wait_tgphy_cmd_ready+0x74/0xc0 [r8152]
[Sun Feb 16 08:20:33 2025] Code: 83 fb 0a 74 57 48 8d 4d dc ba 04 00 00 00 4c 89 e7 44 89 6d dc 41 b8 33 00 00 00 be 34 d6 00 00 e8 91 ea ff ff 83 f8 04 74 b7 <0f> 0b 8b 55 dc 85 c0 79 b1 48 8b 55 e0 65 48 2b 14 25 28 00 00 00
[Sun Feb 16 08:20:33 2025] RSP: 0018:ffffb4d1002afd20 EFLAGS: 00010282
[Sun Feb 16 08:20:33 2025] RAX: 00000000ffffffb9 RBX: 0000000000000000 RCX: 0000000000000000
[Sun Feb 16 08:20:33 2025] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[Sun Feb 16 08:20:33 2025] RBP: ffffb4d1002afd48 R08: 0000000000000000 R09: 0000000000000000
[Sun Feb 16 08:20:33 2025] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9280d4f959e0
[Sun Feb 16 08:20:33 2025] R13: 0000000000000000 R14: ffffb4d1002afdbe R15: ffffb4d1002afd64
[Sun Feb 16 08:20:33 2025] FS:  0000000000000000(0000) GS:ffff9287dd900000(0000) knlGS:0000000000000000
[Sun Feb 16 08:20:33 2025] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Sun Feb 16 08:20:33 2025] CR2: 0000625350f6a6d8 CR3: 000000016aa36000 CR4: 0000000000350ef0
[Sun Feb 16 08:20:33 2025] Call Trace:
[Sun Feb 16 08:20:33 2025]  <TASK>
[Sun Feb 16 08:20:33 2025]  ? show_regs+0x6d/0x80
[Sun Feb 16 08:20:33 2025]  ? __warn+0x89/0x160
[Sun Feb 16 08:20:33 2025]  ? wait_tgphy_cmd_ready+0x74/0xc0 [r8152]
[Sun Feb 16 08:20:33 2025]  ? report_bug+0x17e/0x1b0
[Sun Feb 16 08:20:33 2025]  ? handle_bug+0x46/0x90
[Sun Feb 16 08:20:33 2025]  ? exc_invalid_op+0x18/0x80
[Sun Feb 16 08:20:33 2025]  ? asm_exc_invalid_op+0x1b/0x20
[Sun Feb 16 08:20:33 2025]  ? wait_tgphy_cmd_ready+0x74/0xc0 [r8152]
[Sun Feb 16 08:20:33 2025]  rtl_tgphy_access+0x12d/0x1b0 [r8152]
[Sun Feb 16 08:20:33 2025]  r8157_phy_read+0x13/0x30 [r8152]
[Sun Feb 16 08:20:33 2025]  ocp_reg_w0w1+0x48/0xa0 [r8152]
[Sun Feb 16 08:20:33 2025]  r8157_hw_phy_cfg+0x7cf/0x13d0 [r8152]
[Sun Feb 16 08:20:33 2025]  ? srso_return_thunk+0x5/0x5f
[Sun Feb 16 08:20:33 2025]  rtl_hw_phy_work_func_t+0x63/0xc0 [r8152]
[Sun Feb 16 08:20:33 2025]  process_one_work+0x176/0x350
[Sun Feb 16 08:20:33 2025]  worker_thread+0x306/0x440
[Sun Feb 16 08:20:33 2025]  ? __pfx_worker_thread+0x10/0x10
[Sun Feb 16 08:20:33 2025]  kthread+0xf2/0x120
[Sun Feb 16 08:20:33 2025]  ? __pfx_kthread+0x10/0x10
[Sun Feb 16 08:20:33 2025]  ret_from_fork+0x47/0x70
[Sun Feb 16 08:20:33 2025]  ? __pfx_kthread+0x10/0x10
[Sun Feb 16 08:20:33 2025]  ret_from_fork_asm+0x1b/0x30
[Sun Feb 16 08:20:33 2025]  </TASK>
[Sun Feb 16 08:20:33 2025] ---[ end trace 0000000000000000 ]---
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -19
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -19
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -19
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -19
.. snipped similar lines
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -19
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -19
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: read type=0x0033, index=0xd634 fail -19
[Sun Feb 16 08:20:33 2025] r8152 3-1:1.0: write type=0x0111, index=0xe81c fail -19
[Sun Feb 16 08:20:33 2025] ------------[ cut here ]------------
I tried different kernel parameters:
usbcore.autosuspend=-1
usbcore.old_scheme_first=1 usbcore.nousb2lpm=1
usbcore.usbfs_memory_mb=256

I tried several different versions from the link I provided above.

Typically, there is no specific kernel logging, the above are exceptions. Usually, it just stops working.

Code:
root@pve01:~# iperf3 -c 172.16.10.17 -t 60
Connecting to host 172.16.10.17, port 5201
[  5] local 172.16.10.16 port 52886 connected to 172.16.10.17 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   150 KBytes  1.23 Mbits/sec    2   1.41 KBytes
[  5]   1.00-2.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
[  5]   2.00-3.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
[  5]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
[  5]   4.00-5.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
[  5]   5.00-6.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes
[  5]   6.00-7.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes
On PVE02 (the other side)
Code:
root@pve02:~# iperf3 -s
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 172.16.10.16, port 52872
[  5] local 172.16.10.17 port 5201 connected to 172.16.10.16 port 52886
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  7.07 KBytes  57.8 Kbits/sec
[  5]   1.00-2.00   sec  0.00 Bytes  0.00 bits/sec
[  5]   2.00-3.00   sec  0.00 Bytes  0.00 bits/sec
[  5]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec
[  5]   4.00-5.00   sec  0.00 Bytes  0.00 bits/sec
[  5]   5.00-6.00   sec  0.00 Bytes  0.00 bits/sec
ethtool on both sides show:
Link detected: yes

ping no longer works.

I tried all six of them on different proxmox nodes. I also tested a few of them on another PC that runs Archlinux and dual boots to Windows 11. The devices work on Windows but not on Linux. The devices also seem to work on my M1 macbook pro.

The PC's in question are six HP prodesk 405 G6 with USB-C 10gpbs port. The Archlinux PC is also HP, but Elitedesk 805 G6.

Im quite sick of this to be honest :(.
 
  • Wow
Reactions: pimposh

jerrythea

Member
Sep 12, 2022
37
12
8
Make sure you also have the udev rules:

Code:
# cd /etc
# ls -CF
hwdb.d/  rules.d/  udev.conf
# cd rules.d/
# ls -CF
50-usb-realtek-net.rules  55-thunderbolt.rules    60-bridge-network-interface.rules@  99-usb-power.rules
# cat 50-usb-realtek-net.rules

----
# This is used to change the default configuration of Realtek USB ethernet adapters

ACTION!="add", GOTO="usb_realtek_net_end"
SUBSYSTEM!="usb", GOTO="usb_realtek_net_end"
ENV{DEVTYPE}!="usb_device", GOTO="usb_realtek_net_end"

# Modify this to change the default value
ENV{REALTEK_MODE1}="1"
ENV{REALTEK_MODE2}="3"

# Realtek
ATTR{idVendor}=="0bda", ATTR{idProduct}=="815[2,3,5,6,7]", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="0bda", ATTR{idProduct}=="8053", ATTR{bcdDevice}=="e???", ATTR{bConfigurationValue}!="$env{REALTEK_MODE2}", ATTR{bConfigurationValue}="$env{REALTEK_MODE2}"

# Samsung
ATTR{idVendor}=="04e8", ATTR{idProduct}=="a101", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"

# Lenovo
ATTR{idVendor}=="17ef", ATTR{idProduct}=="304f", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="3052", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="3054", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="3057", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="3062", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="3069", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="3082", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="3098", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="7205", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="720a", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="720b", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="720c", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="7214", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="721e", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="8153", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="a359", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"
ATTR{idVendor}=="17ef", ATTR{idProduct}=="a387", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"

# TP-LINK
ATTR{idVendor}=="2357", ATTR{idProduct}=="0601", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"

# Nvidia
ATTR{idVendor}=="0955", ATTR{idProduct}=="09ff", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"

# LINKSYS
ATTR{idVendor}=="13b1", ATTR{idProduct}=="0041", ATTR{bConfigurationValue}!="$env{REALTEK_MODE1}", ATTR{bConfigurationValue}="$env{REALTEK_MODE1}"

LABEL="usb_realtek_net_end"
----
 

jerrythea

Member
Sep 12, 2022
37
12
8
Also, I did extensive testing of these Realtek USB NICs, and they are not reliable when used with NFS.

For standard scp,ssh they may be usable.

However, they made my cluster unstable, so I switched to OWC TB3 10g NICs.

On sale, the open box cost for the OWC is ~$150 each, about 5 times as much as the Realtek.

More expensive, but only real solution until all the Realtek 8157 bugs are ironed out (but who I don't know).

However, there is actual support, and since the OWC are TB3, they are directly connected via PCIe bus, so almost as good as an actual PCIe card.