MUDI 7 + WindTre Italy (built-in eSIM) – Cellular stuck on “Connecting…” twice per day

Hello,

I am experiencing what appears to be the same issue as described in the thread:

“Mudi 7 (GL-E5800) Cellular WAN (modem_cpu) does not recover after carrier idle-deactivation”. (GL.iNet Official Forum)

Device

  • Router: GL.iNet MUDI 7 (GL-E5800)

  • Firmware: 4.8.5

  • Modem: Quectel RG650V-EU

  • SIM: Built-in eSIM (internal eUICC)

  • Carrier: WindTre Italy

  • Location: Italy

  • Usage: Stationary (not moving between cells)

Problem

About twice per day, the cellular connection drops and the Web UI shows “Connecting…” indefinitely.

The router does not automatically recover the cellular connection.

Recovery

A full reboot is not required.

The connection is immediately restored by simply:

  • Internet → Cellular → Mobile Data OFF

  • Internet → Cellular → Mobile Data ON

Within a few seconds the connection is back.

What I have already tested

  • Latest firmware (4.8.5)

  • 5G Auto

  • LTE Only

  • Correct APN

  • Good cellular signal

  • Router is stationary

  • Issue still occurs regardless of network mode.

Additional information

This looks very similar to the reconnect issue discussed in the thread above, where a test IPK reportedly fixed the automatic reconnection after the carrier terminated the data session. (GL.iNet Official Forum)

Is this the same bug?

If yes, could someone from GL.iNet please provide:

  • the latest cellular test IPK, or

  • a newer beta firmware containing this fix?

I am happy to provide system logs, modem logs, or perform additional tests if needed.

Thank you.

1 Like

Have you tried the test IPK provided in the thread in this answer: Mudi 7 (GL-E5800) Cellular WAN (modem_cpu) does not recover after carrier idle-deactivation - #14 by Cathy ?

1 Like

Hi,

thank you for your reply.

Unfortunately, I’m currently travelling and the MUDI 7 is my only Internet connection. I only have my iPhone with me and no laptop.

Because of that, I don’t think I can install the IPK package or use Telnet/SSH. Is that correct?

If there is another way to test the fix or collect the required logs using only the web interface, I’d be happy to try it. Otherwise, I’ll be able to test the IPK as soon as I’m back home with my laptop.

Thank you for your support.

I suppose there are iOS SSH clients, that could be used for that. But as I don’t use any iOS device, I can’t be affirmative about it.

The network disconnection might be related to the carrier, Please check and ensure the APN is correct. Try setting cellular TTL to 64.

The test ipk can help alleviate this problem. If you don't have a computer, please bind device to Goodcloud, and share it to support. We can help to update it remotely. Here are the instructions on how to share device: Technical Support via GoodCloud - GL.iNet Router Docs 4

Hello Cathy,

I’ve completed all the requested steps:

  • Verified the APN settings

  • Enabled the device share in Goodcloud

The device is now shared with your support team, so remote access is active. Please proceed with the remote update and let me know once it’s completed or if you need anything else from my side.

What du you mean by „Set the cellular mode to 64“?

Thank you!

Sorry for the typo. I mean changing the cellular TTL to 64. And I have remotely updated the package. Please continue to monitor the device and check if there is any improvement

1 Like

Hello Cathy,

since you updated the package, the router has been able to reconnect successfully. It seems that this has resolved the issue.

I also changed the TTL value to 64, as recommended.

Will this workaround still be included in future firmware updates, or will it no longer be necessary after updating?

Thank you for the great and incredibly fast support!