Open nogcha234 opened 3 weeks ago
WP-UT5 is now available for purchase on : Amazon: https://www.amazon.com/dp/B0DF2TTT9H Aliexpress: https://s.click.aliexpress.com/e/_oBoAd9v WisdPi.com: https://www.wisdpi.com/sc240602
Same here, the MTU cannot be set either via Synology tool or the shell
The ifconfig returned: TNETLINK answers: Invalid argument
The ip tool returned: RTNETLINK answers: Invalid argument
This is lack of Link Speed is also an issue for Active/Standby on bonding. The below eth2
is the wisdpi r8157-based adapter, connected to 10G switch. However, it seems the bonding driver still decides not to use this adapter even though the primary slave is set to it. After digging a while it seems like the bonding driver doesn't like the Unknown speed and duplex. From dmesg, the link speed is 0 Mbps for some reason. [ 1227.088463] bond0: link status definitely up for interface eth2, 0 Mbps full duplex
user@synology:/$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth2 (primary_reselect always)
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 100
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: REDACTED
Slave queue ID: 0
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: REDACTED
Slave queue ID: 0
Slave Interface: eth2
MII Status: up
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: REDACTED
Slave queue ID: 0
This is lack of Link Speed is also an issue for Active/Standby on bonding. The below
eth2
is the wisdpi r8157-based adapter, connected to 10G switch. However, it seems the bonding driver still decides not to use this adapter even though the primary slave is set to it. After digging a while it seems like the bonding driver doesn't like the Unknown speed and duplex. From dmesg, the link speed is 0 Mbps for some reason.[ 1227.088463] bond0: link status definitely up for interface eth2, 0 Mbps full duplex
user@synology:/$ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth2 (primary_reselect always) Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 100 Down Delay (ms): 0 Slave Interface: eth0 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: REDACTED Slave queue ID: 0 Slave Interface: eth1 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: REDACTED Slave queue ID: 0 Slave Interface: eth2 MII Status: up Speed: Unknown Duplex: Unknown Link Failure Count: 0 Permanent HW addr: REDACTED Slave queue ID: 0
@yunhao-jiang Many 10Gbps SFP modules do not negotiate the 5Gbps speed correctly, although they may function normally. You need to use an SFP module that supports the 5Gbps speed for testing. We will investigate this issue.
@yunhao-jiang Tested works. Speeds exceeding 5000Mb/s and bond supported.
I have the same problem
=============================== The RTL8157 chipset works with 2.18-1-1. 2.18-1.1 package shows the RTL8157 chipset in action.
I actually confirmed that data transfer at 5GbE speed is possible. However, I can't check the link speed connected to 5000Mbps (5GbE) in Synology's ethtool or Synology network information, and I can't modify the MTU.
The product used is WisdPi WT-UT5.
RTL8152/RTL8153 driver [2.18-1-1] Synology DS920+ [DSM 7.2.1-69057 Update 5]
==========================================
The RTL8157 chipset works with 2.18-1-1. 2.18-1.1 package shows the RTL8157 chipset in action.
I actually confirmed that data transfer at 5GbE speed is possible. However, I can't check the link speed connected to 5000Mbps (5GbE) in Synology's ethtool or Synology network information, and I can't modify the MTU.
This problem is unlikely to be fixed right away, but I'll leave it here for reference.
The product used is WisdPi WT-UT5.
|__2-2 0bda:8157:3000 00 3.20 5000MBit/s 544mA 1IF (WisdPi USB 5G Ethernet 000334C**10017)
eth2 Link encap:Ethernet HWaddr 34:::B1::17
inet addr:10.1.0.* Bcast:***** Mask:255.255.255.0 inet6 addr: fd3b:*:bee2::36c8:d6ff:feb1:17/64 Scope:Global inet6 addr: fe80:::d6ff::17/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:141772521 errors:0 dropped:0 overruns:0 frame:0 TX packets:390506389 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:198520946899 (184.8 GiB) TX bytes:552978638476 (515.0 GiB)
Settings for eth2: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseX/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseX/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: Unknown! Duplex: Full Port: MII PHYAD: 32 Transceiver: internal Auto-negotiation: on Cannot get wake-on-lan settings: Operation not permitted Current message level: 0x00007fff (32767) drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol Link detected: yes