The config below works on my 918+. After attaching the USB, I saw messages on dmesg that I interpreted as "not working properly"):
[437172.770537] netif_napi_add() called with weight 256 on device eth%d
and I did not see the interface in the DSM UI. I logged for the interfaces with ip link and it appeared correctly as eth2. I then copied the config of eth0 (/etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-ovs_eth0) as their eth2 equivalent and adjusted the values in the configs accordingly in a I don't have any idea what I am doing-methodology. After restarting the network with /etc/rc.network restart the interface appeared in the UI and can be configured to my liking now.
Can't say anything about stability. Cloning six VMs from a template using terraform didn't become quicker, but that's more related to the disk setup on the 918 than anything, I guess.
Description of your products
Synology 918+
Linux nas 4.4.180+ #42218 SMP Mon Oct 18 19:17:56 CST 2021 x86_64 GNU/Linux synology_apollolake_918+
DSM 7.0.1-42218 Update 3
Company: ULT-WIIQ, USB 2,5G Ethernet Adapter, USB 3.0 auf RJ45 LAN Netzwerk Adapter, 2500/1000/100/10 Mbps Gigabit Ethernet Internetadapter für Mac OS, Windows, Linux, Dell XPS, Surface Pro, Laptop, Tablet und PC, Link: https://www.amazon.de/gp/product/B09GBFZ9DZ
Description of your environment
connected using TL-SG108-M2 8-Port 2.5Gbe
cable category (Cat.6)
Output of dmesg command
[438501.818408] device ovs_eth2 entered promiscuous mode
[438501.824108] audit: type=1700 audit(1647262004.677:126): dev=ovs_eth2 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[438501.874108] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[438501.888340] device eth2 entered promiscuous mode
[438501.893649] audit: type=1700 audit(1647262004.747:127): dev=eth2 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[438501.929687] IPv6: ADDRCONF(NETDEV_UP): ovs_eth2: link is not ready
[438502.052429] r8152 2-1:1.0 eth2: Promiscuous mode enabled
[438502.058611] r8152 2-1:1.0 eth2: carrier on
[438502.063685] IPv6: ADDRCONF(NETDEV_CHANGE): ovs_eth2: link becomes ready
[438504.034107] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[438504.045108] IPv6: ADDRCONF(NETDEV_CHANGE): ovs_eth0: link becomes ready
Description of the problem
The config below works on my 918+. After attaching the USB, I saw messages on dmesg that I interpreted as "not working properly"):
and I did not see the interface in the DSM UI. I logged for the interfaces with
ip link
and it appeared correctly aseth2
. I then copied the config ofeth0
(/etc/sysconfig/network-scripts/ifcfg-eth0
and/etc/sysconfig/network-scripts/ifcfg-ovs_eth0
) as theireth2
equivalent and adjusted the values in the configs accordingly in a I don't have any idea what I am doing-methodology. After restarting the network with/etc/rc.network restart
the interface appeared in the UI and can be configured to my liking now.Can't say anything about stability. Cloning six VMs from a template using terraform didn't become quicker, but that's more related to the disk setup on the 918 than anything, I guess.
Description of your products
Description of your environment
Output of
dmesg
commandOutput of
lsusb
command