DSM 7.0 - Got it actually working (Update: Working installable SPK)

BeatSkip commented 3 years ago

Not necessarily an issue, just wanted to let you guys know that i got this driver actually working on the DSM 7.0 Beta with a DS415Play

Update

I've actually compiled a working SPK! ~~it just requires a simple ssh command after installation to change the privileges back to root after installation of the SPK. ~~

Update 2

Not sure if i just found a major problem in the DSM privilege system. But apparently, if you add a simple command to the postinst script file you can change the (mandatory) lowered privilege easily back to root, without user interaction.

sed -i 's/package/root/g' /var/packages/r8152/conf/privilege

this changes the execution user back to root and after the next boot, your Package is running fine and dandy as root xD the good part is, now i've got a working SPK that you can just install and you get your USB Access back!

See https://github.com/BeatSkip/r8152 for the complete functioning source. I won't make a pull rquest as this is a specific DSM 7.0 version only

Update 3

Sorry, i have been promoted to a new position at work and have been moving into a new appartement. Hence time is scarce these days. I understand a lot of people have been having reboot issues. As i'm investing in quite the network setup in this appartment, A working version will be needed. But i'm not exactly sure how to proceed with all these issues. I haven't had any reboot issues on either of my two NAS'es (DSM1515+ and DS415Play), so the reboot issues are pretty hard for me to pin down. My main problem is the connection cutting out above 1Gbit speeds. There are some inherent issues with the driver itself. So i'm not a 100% sure what to look for. As soon as i pick this back up updates will be posted here. Sorry guys, if anyone has any suggestions or get's something working, please do post your progress here so i can incorporate that into the driver.

My workflow (proof of concept !out of date!):

Install DSM toolkit on clean ubuntu VM and set up according to the official DSM 7.0 Beta PDF
Edit the pkgscripts-ng/include/applyEnv file. Line 40 from: KERNEL_SEARCH_PATH="$SysRootLib/modules/$PRODUCT-$DSM_SHLIB_MAJOR.$DSM_SHLIB_MINOR/build" to: KERNEL_SEARCH_PATH="$SysRootLib/modules/DSM-$DSM_SHLIB_MAJOR.$DSM_SHLIB_MINOR/build" (this fixes build errors)
Edit the required INFO.sh file and add the line: os_min_ver="7.0-40000"
compile SPK with: sudo ./PkgCreate.py -v 7.0 -p evansport -c r8152 --min-sdk 7.0
extract the resulting SPK file as a zip and extract the r8152.ko file.
put it on the synology and use insmod to load the module
enable interface with: ifconfig eth1 up

The result! yay! no downgrade needed. Now just a script to load it at boot. if anyone can point me to tips how to do this.

LuxKeiwoker commented 3 years ago

Thanks! That's super useful. I guess the same process would also apply to ARM based Synology devices?

BeatSkip commented 3 years ago

Honestly couldn't say, but I would suppose it wouldn't be any different

LuxKeiwoker commented 3 years ago

Ok I've been able to repack the driver for DSM7 as well for rtd1296 uarch and insmod did not give me an error at least. Now I just need to get the USB adapter to confirm that it's working. But boy oh boy - I remember now why I hate working with linux and it's command lines. I've been able to fill in the "gaps" of your instructions, but it took me like 50 browser tabs to overcome a lot of hurdles. Well in any case: thanks again :). I'll come back an confirm if it's working as soon as I've received the adapter - maybe someone else can confirm in the mean time.

DSM7_rtd1296_r8152.zip

BeatSkip commented 3 years ago

Yeah, sorry if I wrote the entire step by step instructions It would have taken an entire essay. And as It's just a proof-of-principle for me it would give me more trouble from people not knowing what they did getting errors. Just wanted to proof that it is possible and get people in their way to do it themselves. I'll probably make a fork later on that's a bit more usable. But I want to try to get that in a working spk and not extracting and copying the module manually.

BeatSkip commented 3 years ago

But great that it worked @LuxKeiwoker!

wingsuiting commented 3 years ago

Can anyone confirm working on a synology 720+ NAS? If so it may be time to get a youtube tutorial together now that the beta's playing nice.

BeatSkip commented 3 years ago

Can anyone confirm working on a synology 720+ NAS? If so it may be time to get a youtube tutorial together now that the beta's playing nice.

If i send you a SPK, would you be willing to test? if you can confirm it as working i'll release it on my fork as a release. but i would like to have it confirmed tested before i do that. i'm setting up the build environment right now

wingsuiting commented 3 years ago

I

Can anyone confirm working on a synology 720+ NAS? If so it may be time to get a youtube tutorial together now that the beta's playing nice.

If i send you a SPK, would you be willing to test? if you can confirm it as working i'll release it on my fork as a release. but i would like to have it confirmed tested before i do that. i'm setting up the build environment right now

Thank you - I would but I'm still on a QNAP - it's the 1gbe that's been putting me (and many others) off moving to the 720+. Does anyone else have an [x]20 unit they can test on?

davidgirard commented 3 years ago

I have a 220+ (J4025) and can test

BeatSkip commented 3 years ago

@davidgirard

(link removed due to direct connection to my NAS)

how soon can you test? soon going to bed haha

BeatSkip commented 3 years ago

For anyone willing to test, here's the full first release:

R8152-All-2.14.0-11-SPK.zip

if everyone that tests it would kindly reply if it did or didn't work. then i can upload it as a full release tomorrow :D

DJNoblesse commented 3 years ago

For anyone willing to test, here's the full first release:

R8152-All-2.14.0-11-SPK.zip

if everyone that tests it would kindly reply if it did or didn't work. then i can upload it as a full release tomorrow :D

Tested on DS216+II(Braswell) and it works great!

BeatSkip commented 3 years ago

@DJNoblesse thanks! That's awesome. Seems like I'm one of the first on the internet to get device drivers working on dsm 7.0 :sunglasses: at least I couldn't find anything at all

lerry commented 3 years ago

For anyone willing to test, here's the full first release:

R8152-All-2.14.0-11-SPK.zip

if everyone that tests it would kindly reply if it did or didn't work. then i can upload it as a full release tomorrow :D

My DSM was broken after install this package and reboot , DS218+. It messed up nginx conf file in /etc/nginx/conf.d/, many packages can't start. Finally I fixed it manually, and reinstalled all broken packages

BeatSkip commented 3 years ago

@lerry you did use the Apollolake package? Really curious what happened there, as there's nothing to do with nginx in the package

Limoges65 commented 3 years ago

Did you guys use newer R8152-drivers than in the last 2.14.0-2 spk? There is still some malfunction with rtd1296-chipsets, not yet covered

BeatSkip commented 3 years ago

@Limoges65 no it is the same one as the 2.14-2, as that is also the latest one available from Realtek

Limoges65 commented 3 years ago

@Limoges65 no it is the same one as the 2.14-2, as that is also the latest one available from Realtek

Do you expect any improvement with the Club3d adapter, connected to Synologies with rtd1296 with DSM7.0 and the new package?

LuxKeiwoker commented 3 years ago

For anyone willing to test, here's the full first release:

R8152-All-2.14.0-11-SPK.zip

if everyone that tests it would kindly reply if it did or didn't work. then i can upload it as a full release tomorrow :D

With installing the spk, is the driver persistent? So no need to reinstall after restart of the NAS?

@Limoges65 no it is the same one as the 2.14-2, as that is also the latest one available from Realtek

Do you expect any improvement with the Club3d adapter, connected to Synologies with rtd1296 with DSM7.0 and the new package?

I think no one would know, as I believe I've been the first one to repack the rtd1296 driver for DSM7.0 in this project. Don't have the adapter yet, but it's in the mail.

BeatSkip commented 3 years ago

@LuxKeiwoker yes, it's persistent. Just like the original DSM 6 version. That is the reason I continued working on it.

BeatSkip commented 3 years ago

@Limoges65 I would'nt have the faintest clue about performance expectations. I just worked on the repack and adaptation to the new DSM platform. 99% of the fork is still to be credited to @bb-qq

LuxKeiwoker commented 3 years ago

@LuxKeiwoker yes, it's persistent. Just like the original DSM 6 version. That is the reason I continued working on it.

out of curiosity: what was necessary to be able to install the .spk ? I mean the whole process you described in the first post was giving me an SPK, but i extracted the .ko file out of it and installed with insmod. I never actually tried to use the *.spk

edit: lol never mind, I just noticed that your first post includes the details now.

BeatSkip commented 3 years ago

Include extra privilege file that states the package should run as user and not root
Include that privilege file in package 3.Edit post install script to edit the privilege file back to root permissions after install (dumb security bug in my mind)
Compile with new DSM 7.0 sdk

See https://github.com/BeatSkip/r8152 For the entire edit

BeatSkip commented 3 years ago

@lerry do you have any additional info? I don't want to be the responsible for people f'ing up their nas :flushed:

lerry commented 3 years ago

Yes I used the Apollolake package. I tried twice, at first I compiled the package with your forked repo, the second time I use your package. After installing, it can't work, nothing happened, so I reboot my NAS, and it restart once and once again itself. So I unplugged the USB adapter, this time it booted successfully, so I removed the package at once. but almost all packages can't up, such as Photos, Cloud Sync, The logs in /var/logs/ shows there was something wrong with nginx conf, I found many conf in /etc/nginx/conf.d became gibberish, I removed and reinstalled them, and the system became normal. I tried twice, and it behaved the same

BeatSkip commented 3 years ago

Hmm weird, and have you installed this driver from @bb-qq on DSM 6.2 before with success? Trying to figure out if it was a problem before my modifications or that i introduced it with my edits

BeatSkip commented 3 years ago

I checked, and the word 'nginx' isn't even once in the entire source code of the package :sweat_smile:, so I'm baffled how that file could be corrupted, and any other files related to that

BeatSkip commented 3 years ago

@lerry could you provide me with a zip of all the logs, including /var/log/packages/r8152 logs and The debug.dat https://jeremyverda.net/export-synology-nas-system-logs/ You can post it here or mail it my email from my github profile

lerry commented 3 years ago

Hmm weird, and have you installed this driver from @bb-qq on DSM 6.2 before with success? Trying to figure out if it was a problem before my modifications or that i introduced it with my edits

Yes, it's ok on DSM 6.2. I don't why ,but it just happened

Errors in Log Center it appeared when system is broken.

错误 | 系统 | 2021/01/24 12:50:01 | SYSTEM | Task Scheduler Output results path is inaccessible, please check output result folder is accessible.

/var/log$ sudo grep nginx *

synobootup.log:Jan 24 11:22:36 LerryStation synopkgctl[21076]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:22:36 LerryStation synopkgctl[21076]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:22:36 LerryStation synow3tool[24087]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:22:38 LerryStation synow3tool[24087]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:22:38 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 11:23:02 LerryStation synopkgctl[12689]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:23:02 LerryStation synopkgctl[12689]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:23:03 LerryStation synow3tool[26300]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:23:04 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 11:23:04 LerryStation synow3tool[26300]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:23:06 LerryStation synopkgctl[22086]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:23:06 LerryStation synopkgctl[22086]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:23:06 LerryStation synow3tool[26642]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:23:08 LerryStation synow3tool[26642]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:23:08 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 11:23:08 LerryStation synopkgctl[26787]: nginx_conf_register.cpp:755 nginx test fail, nginx: [emerg] too long parameter "nginx: configuration file /var/tmp/nginx/test/plugin_config/nginx.conf test failed
synobootup.log:Jan 24 11:23:15 LerryStation synopkgctl[27186]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:23:15 LerryStation synopkgctl[27186]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:23:15 LerryStation synow3tool[28026]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:23:16 LerryStation synow3tool[28026]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:23:16 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:          1.936s nginx.service
synobootup.log:  nginx.service                                                                                                        loaded    active   running Nginx
synobootup.log:Jan 24 12:50:50 LerryStation synopkgctl[18761]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 12:50:50 LerryStation synopkgctl[18761]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 12:50:50 LerryStation synow3tool[20586]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 12:50:51 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 12:50:51 LerryStation synow3tool[20586]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 12:51:09 LerryStation synopkgctl[19258]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 12:51:09 LerryStation synopkgctl[19258]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 12:51:09 LerryStation synow3tool[21650]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 12:51:10 LerryStation synow3tool[21650]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 12:51:10 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1

synobootup.log

Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd

-- | -- | -- | -- | --

--

BeatSkip commented 3 years ago

Hmm weird, and have you installed this driver from @bb-qq on DSM 6.2 before with success? Trying to figure out if it was a problem before my modifications or that i introduced it with my edits

Yes, it's ok on DSM 6.2. I don't why ,but it just happened

Errors in Log Center it appeared when system is broken.

错误 | 系统 | 2021/01/24 12:50:01 | SYSTEM | Task Scheduler Output results path is inaccessible, please check output result folder is accessible.

/var/log$ sudo grep nginx *

synobootup.log:Jan 24 11:22:36 LerryStation synopkgctl[21076]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:22:36 LerryStation synopkgctl[21076]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:22:36 LerryStation synow3tool[24087]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:22:38 LerryStation synow3tool[24087]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:22:38 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 11:23:02 LerryStation synopkgctl[12689]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:23:02 LerryStation synopkgctl[12689]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:23:03 LerryStation synow3tool[26300]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:23:04 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 11:23:04 LerryStation synow3tool[26300]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:23:06 LerryStation synopkgctl[22086]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:23:06 LerryStation synopkgctl[22086]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:23:06 LerryStation synow3tool[26642]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:23:08 LerryStation synow3tool[26642]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:23:08 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 11:23:08 LerryStation synopkgctl[26787]: nginx_conf_register.cpp:755 nginx test fail, nginx: [emerg] too long parameter "nginx: configuration file /var/tmp/nginx/test/plugin_config/nginx.conf test failed
synobootup.log:Jan 24 11:23:15 LerryStation synopkgctl[27186]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 11:23:15 LerryStation synopkgctl[27186]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 11:23:15 LerryStation synow3tool[28026]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 11:23:16 LerryStation synow3tool[28026]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 11:23:16 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:          1.936s nginx.service
synobootup.log:  nginx.service                                                                                                        loaded    active   running Nginx
synobootup.log:Jan 24 12:50:50 LerryStation synopkgctl[18761]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 12:50:50 LerryStation synopkgctl[18761]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 12:50:50 LerryStation synow3tool[20586]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 12:50:51 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1
synobootup.log:Jan 24 12:50:51 LerryStation synow3tool[20586]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 12:51:09 LerryStation synopkgctl[19258]: systemd_reload.cpp:17 synosystemd: [nginx] reloading ...
synobootup.log:Jan 24 12:51:09 LerryStation synopkgctl[19258]: systemd_reload.cpp:21 synosystemd: [nginx] reloaded.
synobootup.log:Jan 24 12:51:09 LerryStation synow3tool[21650]: nginx_deploy.cpp:906 Nginx config has problem, change to abnormal mode
synobootup.log:Jan 24 12:51:10 LerryStation synow3tool[21650]: nginx: [emerg] too long parameter "
synobootup.log:Jan 24 12:51:10 LerryStation systemd[1]: nginx.service: control process exited, code=exited status=1

synobootup.log

Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd
Jan 24 14:01:50 LerryStation cloud-control[20408]: (20408:47648) [ERROR] file-lock.cpp(58): wrong fd

-- | -- | -- | -- | --

--

okay, that means it's introduced in my package. can you provide me with the Debug.dat file. As the nginx error is the resulting problem but not the source. the debug.dat should provide me possibly with the source of the corruption (hopefully)

lerry commented 3 years ago

r8152.log

lerry commented 3 years ago

generating of Debug.dat is very slow

BeatSkip commented 3 years ago

@lerry wait, are you doing anything with or inside docker? i see docker come up in the log file a lot

lerry commented 3 years ago

@BeatSkip I use Docker a lot, just common usage, redis, mysql, and so on

BeatSkip commented 3 years ago

@lerry yeah, but are you using this with docker in any way on the machine, or is it "just installed on the same system" as docker souldn't come up in the r8152 log if you just install it normally via the package manager. Otherwise i would say docker is the issue here. preventing the spk file from properly installing the kernel module.

BeatSkip commented 3 years ago

my system doesn't support docker, so don't know how the docker stuff on synology works, I just know it from the command line

lerry commented 3 years ago

I install docker from package manager, they just installed on the same system

lerry commented 3 years ago

I can't give you all logs for privacy, maybe you can tell me which one is useful for debugging

BeatSkip commented 3 years ago

@lerry that's understandable, i'm generating my own debug.dat to see wich files might be interesting to look at

BeatSkip commented 3 years ago

debug\dsm\var\log\synosystemd.log debug\dsm\var\log\synoservice.log debug\dsm\var\log\syslog.log debug\dsm\var\log\dmesg (this one is very interesting) debug\dsm\var\log\messages (this one too) debug\dsm\var\log\kern.log debug\dsm\var\log\synoinstall.log

lerry commented 3 years ago

logs.zip

lerry commented 3 years ago

messages1.zip

BeatSkip commented 3 years ago

@lerry is see r8152 errors going back to beginning of this month, do you have any residual files/stuff or anything still on you system from those attempts that might interfere with this package? if there's an older non-functioning r8152.ko file somewhere that my package can't overwrite or anything that could interfere. as it seems the kernel crashed quite a few times in the earlier attempts. i see this coming up a lot:

2021-01-24T10:11:59+08:00 LerryStation kernel: [ 177.269680] r8152: module verification failed: signature and/or required key missing - tainting kernel

but that doesn't pop-up in my logs, that means either my system doesn't care about the signatures and yours does, or your system persists the older .ko file and keeps trying that instead of mine. either way, the kernel module can't load.

edit: seems that it might be the first one, is secure boot enabled on your system?

BeatSkip commented 3 years ago

@lerry can you try to extract the r8152.ko file from the spk, put it on the nas somewhere and load the kernel manually with insmod? then you can check if it's the actual module that won't load or something else about the package that messes with things

lerry commented 3 years ago

I tried again just now, I run sudo insmod r8152.ko and plug in the adapter, the DSM system rebooted itself immediately. Luckily the system is good after reboot

BeatSkip commented 3 years ago

Okay, can you gather the same logs as earlier? I'll look at them tomorrow and check if it's indeed the module signing problem.

lerry commented 3 years ago

Okay, can you gather the same logs as earlier? I'll look at them tomorrow and check if it's indeed the module signing problem.

logs.zip

LuxKeiwoker commented 3 years ago

ok just received the Club3D Adapter for my DS418j. I can confirm that your package is working (kind of) @BeatSkip. After installation I see the adapter, I can configure it and connect to DSM with the PC attached to it. But I can't transfer big files - as soon as it starts transferring data, the connection collapses. Reducin the Link-Speed to 1 GBit/s makes usable, but defeats the purpose. I think I've read about this issue already somewhere else and it might be related to MTU size? (I had Auto = 1500)

Edit: increasing MTU Size to 9000 didn't help. I can't find a solution for this.

BeatSkip commented 3 years ago

I had a problem that I needed to reboot windows on my pc (oddly enough) for everything to work correctly. And had to use a USB hub between the synology and the USB ethernet adapter. @LuxKeiwoker could you try both of those and see if that improves, just curious if those are limited to my setup.

BeatSkip commented 3 years ago

As for the USB hub, I suspect something odd is going on with the synology driver for the USB 3.0 card in the nas

bb-qq / r8152