Closed deckard2123 closed 3 years ago
This situation happens also on my NAS 918 with ugreen 2.5G. I muss change the ip address of the nas, then it could be connected with my computer.
Could you try this workaround? https://github.com/bb-qq/r8152/issues/92#issuecomment-783863386
Could you try this workaround? #92 (comment)
I tried changing "sleep 5" to sleep 7, 10, and 20. Each time following reboot, the 2.5 Gbps adapter was still inaccessible until I switched it to DHCP and back to manual in DSM.
On my 916+ I use a fixed IP and via Task Scheduler following commands
ifconfig eth2 up synonet –dhcp eth2
Everything works fine with this after startup...
On my 916+ I use a fixed IP and via Task Scheduler following commands
ifconfig eth2 up synonet –dhcp eth2
Everything works fine with this after startup...
Is this how you have it configured in Task scheduler @Sjekke? Screenshots are below. I tried rebooting the DS416Play with this enabled and the 2.5 Gbps adapter set to a static ip address. I still couldn't access the 2.5 Gbps adapter until switching DHCP on and then back off.
Hi @deckard2123 indeed like that. But I use a Plugable 2.5 adapter.
I submitted a pull request that should fix the dhcp issue.
I created the 2.14-3 including the fix of that PR.
2.14-3 Works fine with DHCP on my DS918+. But then again it would be nice if someone else could verify that it fixes the problem.
By the way: if you want to assign a static ip, add this in synology taskmanager - without it, the ip in syno settings was not assigned for me with ds918+ after reboot:
taskmanager (user root, boot-up)
synonet --set_ip -4 eth2 add 192.168.178.3/24
Change ip And/or subnet to your needs. 24 means 255.255.255.0
I close this issue. If you are still having problems, please feel free to reopen this issue.
Description of the problem
Whenever the DS416Play boots up, the Sabrent 2.5 Gbps Adapter is listed as one of the network interfaces, however it can't be reached via the network or pinged until I switch the adapter's IPv4 setting in DSM from "Use manual configuration" to "Get network configuration automatically (DHCP) and then back to "Use manual configuration."
On boot, the fields for Gateway and DNS Server are are always blank when "Use manual configuration" is selected prior to a reboot. If I fill these fields in manually without clicking "Get network configuration automatically (DHCP)" the Sabrent adapter is still unreachable on the network. It doesn't become reachable until I select "Get network configuration automatically (DHCP)" click ok, and then switch it back to "use manual configuration" and click ok that the network adapter becomes reachable. When switching the adapter to "Get network configuration automatically (DHCP)" DSM fills in the Gateway and DNS Server fields with default IP addresses that work for my network. If I delete the the addresses automatically filled in these fields after switching back to "Use manual configuration" the adapter is also reachable on the network.
Keeping the adapter configured to "Get network configuration automatically (DHCP)" when rebooting doesn't solve the issue. When rebooting with this configuration, the network adapter remains unresponsive on the network following the reboot.
Is there a workaround for this or a startup script could be created to have DSM automatically cycle through these settings (DHCP off--> DHCP on--> DHCP off) on startup?
Note: dmesg, lsusb, and ifconfig commands were done immediately after rebooting the DS416Play and connecting via SSH through the built in 1 Gbps ethernet port.
Description of your products
NAS Model: DS416Play output of uname -a command Linux DS416Play 3.10.105 #25426 SMP Mon Dec 14 18:45:24 CST 2020 x86_64 GNU/Linux synology_braswell_416play DSM version: DSM 6.2.3-25426 Update 3 Dongle: Sabrent USB to 2.5 Gigabit Ethernet Adapter [10/100/1000/2500] (NT-S25G)
Description of your environment
The dongle is connected to the front USB port on the DS416Play.
Output of
dmesg
commandOutput of
lsusb
commandOutput of
ifconfig -a
command