-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
wwan0 gets stuck on :lan connection status after a VintageNet.deconfigure/configure #124
Comments
Hi @taun, Thanks for reporting this and giving all of the detail. There's definitely an issue here. I'm distracted by one thing in the report which is may be a red herring. Are you using a Twilio or T-Mobile SIM on the device that's losing its connection? If you're using Twilio, then roaming needs to be allowed for the super SIM so the line should be:
See the Twilio roaming document. Of course, vintage_net shouldn't revert the interface to |
Thanks for looking at it @fhunleth. Yes, all of the above is with Twilio Super SIMs. Roaming was not specifically enabled however I have been seeing "roaming", true as shown below. The following is from a test site where the uptime has been 4 days as of today. None of the other units are currently showing a roaming status although I have seen a roaming, true status for some of the others occasionally. I will specifically enable roaming and continue to test. But as you say, that is a separate issue. Every little bit helps.
|
Roaming has been enabled and we are still seeing connection state issues. Meaning, the modem is connected and the internet is pingable when specifying the ifname but the VintageNet connection state is :lan or even :disconnected. After more investigation, it seems our issues and this one might be related to I have lots of logs but the current premise is:
Maybe this is one case where "let it crash" should be avoided? I am still trying to determine the root cause of the crashes besides: The below are just various crashes from the logs. Some like the :timeout are probably expected. I am trying to figure out which results in the cache being lost and then the client_id pool exhausted.
|
Interesting. Thank you for posting the update. I'd like to offer some wisdom, but I have none at the moment. I do appreciate the update, though. |
Describe the bug
Modem: Quectel BG96
Starting with a good working :internet connection on wwan0
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It was expected that deconfigure followed by a configure with no other change would result in restoring the :internet connection for "wwan0"
VintageNet Info
Output of
VintageNet.info
Note, we have given route priority to wwan0 over eth0.
Before
deconfigure
After
deconfigure
After configure
Environment
mix nerves.env --info
)Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: