-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arpl-i18n-23.8.3 choose NIC detection order (built-in intel i219-lm and PCIe RTL8125B network) #168
Comments
Thank you for the quick response. I've tried: Is there another way to reverse or reserve the NIC detection priority to the built-in (e1000e) to be eth0? Thank you. |
I have been quite busy lately and don't have time to study. It may take some days. |
Sure no problem. I will do some research, if I find a solution, will share it here. I appreciate your works. update1: using modprobe command in arpl loader. command/script above seen works, but only temporarily, and inside arpl loader. since arpl is ram base, it will reset any bash script on reboot. When use boot.sh to DSM, the order reverse again e1000e is assigned back to eth2(LAN 3), the dual port r8125 going back to eth0(LAN 1) and eth1(LAN 2). |
Yes, the order is related to the loading order of the network cards. The order of the network cards is a common problem in Linux. The naming rules of eth* have been eliminated in the new Linux. |
@wjz304 I have a similar problem with igb and bnxt_en. If I power cycle the VM, bnxt_en will be eth0 and igb will be eth1 and that brakes my HA cluster. In order to fix it I have to stop and start the VM again and the order will change once more... This is on the passive server (arpl 23.8.9) of the HA cluster. On my active server (arpl 23.7.1) which I have igb as eth0 and ixgbe as eth1 it does not happen. There is no way to fix it? |
顺序可以改,但是会带来很多麻烦 |
因为mac地址是arpl传下去的,所以如果要调整顺序需要保持 arpl 和dsm严格的一致。 |
给你一个方法 自己改吧,
|
可以写到计划任务里 |
Ok, thank u. |
/etc/rc.network restart |
Thank You. I will be testing this release on the weekend. |
No feedback, this issue close |
Hello Ing, I was bit busy with life, just able to try out the "sortnetif" feature this weekend. I rebuilt a brand new system to test it out. boot to arpl and dsm by default assign ip as order: I boot to arpl menu. launch menu.sh. After the config the sortnetif addon, ARPL still detect the order as: launching DSM, script still shows: Re-launching ARPL and remove sortnetif addon, everything goes back to default. DSM will launch normal with ip assign to: let me know if I doing something wrong. Thanks |
Today I've edited user_config.yml to add sortnetif:"e1000eMAC,rtl8125MAC1,rtl8125MAC2" like your instruction. However, it does not change, the original order remains the same. I've verified that the MAC ID is correct with "ip link" command. both is arpl, pcie rtl8125 2x nic will be 1st to register as eth0 & eth1 then built in e1000e nic will be on eth2. The same order is in DSM 7.2.1-update1 rtl8125 2x nic will be on LAN1 & LAN2, e1000e nic will be on LAN3. |
只能取日志看一下了 |
Hello,
Status: My system is Optiplex 7050 bare metal, DSM 7.2-update3, model DS918+, arpl-i18n-23.8.3 loader. The built-in nic detected as e1000 (intel i219-lm), PCIe x1 dual rt8125 nic. ARPL autodetect in this order:
eth0 - rt8125, eth1 - rt8125, eth2 - e1000
DSM Lan 1, Lan 2 to rt8125, and Lan 3 to e1000
Which is fine. However, DSM setting only enable for Lan 1 (rt8125 port 1) and Lan 2 (rt8125 port 2) to be wake-on-lan (WOL). PCIe NIC have no WOL feature in BIOS or active link light when system is off.
Problem: When DSM is being shutdown, Lan 3 (e1000) link light will be turn off, and WOL will not receive package on this port. The only way to make the built-in NIC back to normal is to cycle the power, or at power loss, then link light will be active again, and WOL will work.
Question: Is there a way to reverse the NIC detection order, or manually force ARPL to put e1000 to be eth0?
I've tried to modify the netif order by ssh to DSM, "vi /etc.defaults/synoinfo.conf" command, edit to [netif_seq=”2 0 1 3 4 5 6 7”]. However, after restart the system, the configuration file reverse back to original orders.
Thank you!
The text was updated successfully, but these errors were encountered: