network error in newest version(arpl-1.1beta2a)

[sunshe35]

the right network result: version: 0.4-alphe11 and 1.0beta10a system: vm in pve these version works good.

the bad network result: version: 1.1beta2a system: vm in pve I cant not find any synology from synology assistant in this version.

[remuxs]

Man taipat mano serveris HP Microserver n40l

[sunshe35]

Man taipat mano serveris HP Microserver n40l

Is it works right for you? I use i5-6600, lenovo M720Q, it works wrong in synology vm in pve7.3-3.

[fbelavenuto]

the right network result: version: 0.4-alphe11 and 1.0beta10a system: vm in pve these version works good.

the bad network result: version: 1.1beta2a system: vm in pve I cant not find any synology from synology assistant in this version.

This behaviour is normal, recent versions will show the shell prompt. The problem is with module/driver for you hardware.

[sunshe35]

thanks for your answer. I use the same environment for compare. The "1.0beta10a" works well but "1.1beta2a" works bad and the ip "192.168.10.77" will lost in my Router a fews munites later.
I test the problem in a new synology vm in pve. It has the same result.
I update addons and modules for "1.0beta10a" to newest version. It is not works too.

I think the differents drive/modules between "1.0beta10a" and "1.1beta2a" is the root cause of the problem.

[unitea1992]

I am also encountering the same problem. With 1.0-beta13, the NIC links down once at boot and links up after a few minutes. After that, DSM can be accessed. (1.0-beta10a seems to work fine as well)

After 1.1-beta1, the NIC does not link up and no matter how many minutes I wait, I cannot access the DSM. Ping does not work either.

CPU: Intel core i5-11400 MB: ASUS B560M-Plus (internal NIC is disabled) NIC: Intel X550-T2 Installation type: Baremetal

The status of the screen with and without the problem is the same as the thread owner. Each version has not been updated with any add-ons or modules.

[Silverbolt12]

Same issue，it generally happens after restart PVE directly, I can't find any DSM. And must have to stop the VM directly and start it again.

[sashakozlov86]

Hello, friends! On a baremetal laptop HP x360 Pavilion ba103ur (connected via USB3.0-LAN Adatep D-Link DUB-1312, also tried TP-link) the same problem - after a certain period of time (after determining the IP address), the device disappears in the router.

[sashakozlov86]

Good afternoon friends! After deactivating the "cdc-ncm" module (in the "modules" section in the bootloader), everything started up for me and the network no longer disappears!

[ostarcn]

I also encountered the same problem, after deactivating the "cdc ncm" module, the problem still exists