feckert
commented
5 months ago What OpenWrt version are you using? I made some changes recently, that should fix this issue on boot. https://github.com/openwrt/packages/commits/master/net/modemmanager
Open yegorich opened 5 months ago
feckert
commented
5 months ago What OpenWrt version are you using? I made some changes recently, that should fix this issue on boot. https://github.com/openwrt/packages/commits/master/net/modemmanager
yegorich
commented
5 months ago OpenWrt: r24436-0f283ab4c9, packages: f9c90fce0aad9ebec04e09b10843da3571c09f83 and two patches from @osedlbauer.
feckert
commented
5 months ago Ok, so you already have the latest changes. Normally, the new monitor service is doing this task.
When the modemmanager has recognized the modem, then the monitor service marks the uci interface section as avialable. And only then the netifd should start a connection attempt.
Is your log the output when booting?
yegorich
commented
5 months ago Yes, it is the bootlog. I have added more output.
feckert
commented
5 months ago I think that could solve the problem. This change has the effect that the proto setup should be tried again and again as long as ifdown keep_retry for this, as it changes the current behavior. @yegorich Can you test this?
diff --git a/net/modemmanager/files/modemmanager.proto b/net/modemmanager/files/modemmanager.proto
index e67a84cf2..849e66709 100755
--- a/net/modemmanager/files/modemmanager.proto
+++ b/net/modemmanager/files/modemmanager.proto
@@ -587,8 +587,8 @@ proto_modemmanager_setup() {
append_param "${password:+password=${password}}"
mmcli --modem="${device}" --timeout 120 --simple-connect="${connectargs}" || {
- proto_notify_error "${interface}" MM_CONNECT_FAILED
- proto_block_restart "${interface}"
+ echo "connection failed -> attempting restart"
+ proto_notify_error "${interface}" MM_CONNECT_RESTART
return 1
}@feckert will do. Though, it will take some time.
feckert
commented
1 month ago The first part with the reconnect has been fixed https://github.com/openwrt/packages/pull/24370. Thanks to @osedlbauer. What is still missing is that the modem is not switched off during a reconnect in order to improve the reconnect time.
Maintainer: @mips171 / @aleksander0m Environment: ARMv7, TI Sitara AM335x, OpenWrt v23.05.2
Description:
In the following log, though the modem could be found, netifd is giving up and doesn't try to get it up once more. Restarting the interface via the web interface leads to a successful connection.
How to force netifd to try the initialization again?