Skip to content
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

ModemManager: fix auto-config #55

Closed
adeebshihadeh opened this issue Apr 8, 2022 · 2 comments
Closed

ModemManager: fix auto-config #55

adeebshihadeh opened this issue Apr 8, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@adeebshihadeh
Copy link
Contributor

May just work with a newer version after #54

nmcli connection modify --temporary lte gsm.auto-config yes

@adeebshihadeh adeebshihadeh added the bug Something isn't working label Apr 8, 2022
@adeebshihadeh
Copy link
Contributor Author

adeebshihadeh commented May 25, 2022

Seems to be a NetworkManager issue. Changing the yes/no values makes the warning go away, but doesn't actually get the config to be read properly. Verbose logging doesn't show any more issues.

keyfile: connection.autoconnect: invalid setting: Key file contains key “autoconnect” which has a value that cannot be interpreted.
keyfile: gsm.auto-config: invalid setting: Key file contains key “auto-config” which has a value that cannot be interpreted.
keyfile: gsm.home-only: invalid setting: Key file contains key “home-only” which has a value that cannot be interpreted.

@adeebshihadeh
Copy link
Contributor Author

Got the bottom of this:

  • gsm.auto-config doesn't work if any of the other GSM connection settings are specified
  • gsm.home-only=no doesn't work, need to just exclude it from the config when roaming is allowed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant