forked from oats-center/isoblue2
-
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
ISOBlue network management #5
Labels
enhancement
New feature or request
Comments
For reference the current ISOBlue 3 tests are using network manager for
this. It appears to do the right thing most of the time.
The biggest issue is that it favors wired networks, but in my case that is
just local.
…On Mon, Aug 26, 2019, 10:54 AM Yang Wang ***@***.***> wrote:
The current ISOBlue 2.0 devices uses the following scripts and programs to
keep the LTE network alive:
- qmicli for establishing and connecting to AT&T network
- dhclient for getting an IP
- get-pgns.service and reconnect-cell.service to check and reconnect
to the network if necessary
This strategy works but it is rather messy and not very sustainable. With
ISOBlue HD and future iterations of ISOBlues, more network protocols will
be added into the device. Hence, it will be important to find a network
management tool that is built for this purpose.
networkmanager <https://wiki.gnome.org/Projects/NetworkManager> seems to
fit for our purpose. I (and also @abalmos <https://github.com/abalmos>)
had some success using it when the network is in optimum situation. I
didn't have the time to mess with the settings
<https://developer.gnome.org/NetworkManager/unstable/nm-settings.html>
for reconnect settings and network priorities (if multiple networks are
present). I think it will be a good idea to test and find out what we can
do with the networkmanager to oversee the network connectivity for
ISOBlues.
Here are some first steps:
- Check what version of networkmanager we will need for ISOBlue.
- Use networkmanager to manage multiple networks (LTE, Ethernet, WiFi,
Bluetooth, etc).
- Adjust the settings for suboptimal network scenarios.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AAOHLBNB3PNQPCICKIW7B4TQGPVDXA5CNFSM4IPQRDA2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHMZL6A>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOHLBJ3TZMNXSISATPQHTTQGPVDXANCNFSM4IPQRDAQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current ISOBlue 2.0 devices uses the following scripts and programs to keep the LTE network alive:
qmicli
for establishing and connecting to AT&T networkdhclient
for getting an IPget-pgns.service
andreconnect-cell.service
to check and reconnect to the network if necessaryThis strategy works but it is rather messy and not very sustainable. With ISOBlue HD and future iterations of ISOBlues, more network protocols will be added into the device. Hence, it will be important to find a network management tool that is built for this purpose.
networkmanager
seems to fit for our purpose. I (and also @abalmos) had some success using it when the network is in optimum situation. I didn't have the time to mess with the settings for reconnect settings and network priorities (if multiple networks are present). I think it will be a good idea to test and find out what we can do with thenetworkmanager
to oversee the network connectivity for ISOBlues.Here are some first steps:
networkmanager
we will need for ISOBlue.networkmanager
to manage multiple networks (LTE, Ethernet, WiFi, Bluetooth, etc).The text was updated successfully, but these errors were encountered: