modemmanager: Modem connected but without internet
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux
- Domain
- networking
Research direction
Start by reading the modemmanager package files in this repository and the issue’s report of the Huawei E3531s-2 losing internet while OpenWrt still shows it connected. Check whether the package or its reported settings handle a lost data connection and reconnection; the payload names no specific source file or test. Done means identifying why internet access is lost and whether modemmanager can restore it without rebooting the router.
Written by the indexing model from the issue text.
Description
Package Name
modemmanager
Maintainer
openwrt
OpenWrt Version
25.12.5
OpenWrt Target/Subtarget
bmips/bcm63268
Steps to Reproduce
I have a 3g modem Huawei E3531s-2 (v21.318.35.00.00) connected to OpenWrt (v25.12.5 r33051-f5dae5ece4), I use modemmanger (1.24.0-r11) as protocol in wan interface to connect to ISP.
The problem is that after several hours (sometimes not even one hour) I lose internet and everyone in my home gets a message saying limited connectivity, the modem is still showing being connected in OpenWrt overview page but without internet, the only solution to fix it is to reboot the router.
I tried using watchcat to restart router or interface when internet is lost, but it introduced other racing bugs while booting and enter a loop of errors without fixing the problem.
Is there any setting which I don't know and should be enabled to keep modemmanager restarting connection with ISP when internet is lost, because I think ISP is redistributing IPs to connected devices at random intervals and modemmanager doesn't detect the changes.
Actual Behaviour
Only rebooting fixes the lost internet.
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
- Dominant language
- Makefile
- Stars
- 4.7k
- Forks
- 4k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 251
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openwrt/packages
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openwrt/packages#31307 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
openwrt/packages#31306 · 1 comment ·
Maintainers usually reply within 1 day
All issues in openwrt/packages
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
webtorrent/webtorrent#3131 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100