BUG wlanX name cause coredump

[Kali-]

请填写以下信息.
Please fill in the following information.

Install ENV: (You can find it in the boot interface.)

• DMI:
• CPU: N100
• NIC: (pid & vid)

RR version: (You can find it in the update menu.)

• RR: 25.1.2
• addons:
• modules:
• lkms:

DSM:

• model: DS3622xs+
• version: 7.2.2-72806 Update 2

Issue:
loading and configuring a wifi device named wlan0, wlan1 or ovs_wlan0 (i didnt tryed more) cause issue. Network page in Info Center is completly empty and everytime the tab is selected cause a coredump (journalctl -f). To be picky, the issue do not start instantly after configuring the devices, sometime after few minutes sometime take longer, and will be broken until device is removed (rmmod) or taken down (ifconfig wlan0 down)
i have found a workaround, loading the wifi modules with a ovs_eth9 seems to prevent this issues. it also allow to get the device showed in Network page (as LAN 10) which was completly hidden with wlan0 or ovs_wlan0

example:
insmod /lib/modules/8188eu.ko ifname=ovs_eth9

logs:

(## 因为 log中存在 SN/MAC 等一些敏感信息, 当提供完整文件时请自行抹除他们, 当然你也可以发送到我的邮箱. ##)
(## Because the log contains some sensitive information such as SN/MAC, please delete them when providing the complete file. Of course, you can also send it to my email. ##)
...

(请先看一下#173、#175、#226 的内容)
(Plz review the content of #173, #175, #226 first)
...

(如果你只是说 XXX 不能用, 什么详细信息也不提供, 我也只能说感谢你的反馈.)
(If you just say XXX doesn't work without providing any details, I can only say thank you for your feedback.)
...

[Kali-]

nvm, ovs_wlan0 still cause issue, happened after 30 minutes!
ill dig more before open it

[wjz304]

Try using eth99 ?

[Kali-]

right now i'm using ovs_eth9, looks promising but last night i got a power failure and my nas rebooted
ill continue to monitor
did u prefer eth99 or ovs_eth99 ?

[wjz304]

right now i'm using ovs_eth9, looks promising but last night i got a power failure and my nas rebooted ill continue to monitor did u prefer eth99 or ovs_eth99 ?

I just thought of 99 after seeing your explanation, but 99 seems to be reserved for the management port.

[wjz304]

As a general script, we can add a base number, such as 20, 90, wlan0 -> ovs_eth90

[Kali-]

switched to ovs_eth90
btw, did u know if ovs_ devices (OpenVirtual Switch) is default in DSM 7.2.2 or i have it beacause i have Virtualization pkg configured?

[wjz304]

[ -n "$(cat /usr/syno/etc/synoovs/ovs_reg.conf 2>/dev/null)" ] && echo "Used OVS"

That's all I know at the moment

[Kali-]

the "workaround" of use ovs_eth90 looks to be working, 1 day no crash :)

[wjz304]

ovs_wlan0 你试过吗？

[Kali-]

ovs_wlan0 still crash, its the 1st test i did

[wjz304]

OK

ovs_wlan0仍然崩溃，这是我做的第一次测试

[Kali-]

also ovs_wlan0 is not shown in Network pages

[wjz304]

嗯，我现在没环境，稍后我测试下，优化下脚本

[wjz304]

It seems that ovs* is not needed, just rename wlanX to ethX