Commit Graph
15 Commits
Author SHA1 Message Date
Lubomir Rintel eaaf64ffce base-bearer: fix check for cancellation
If we cancel connect_cancellable, the connect task will return a
G_IO_ERROR_CANCELLED. We may need to do some cleanup (like, disconnect
if the connection went far enough to actually start the network
connection), thus it's important we check for cancellation correctly.
2019-05-14 09:47:54 +02:00
Aleksander Morgado 9c3ac2fb60 api,modem-3gpp: new 'InitialEpsBearer' property
This property contains the DBus path of a Bearer object of type
MM_BEARER_TYPE_DEFAULT_ATTACH, which is automatically exposed by the
modem when registered in the LTE network.

Unlike standard bearer objects created by the user, this bearer won't
allow any connection/disconnection request, as its status is bound to
the LTE registration exclusively.

The bearer settings exposed by the object include the APN details that
have been used during the initial packet network attach, which may be
defined by modem settings (e.g. if previously configured in the
firmware which APN to use for the given SIM card operator) or by the
network itself (e.g. if none configured, or if a network override is
required as when roaming).

The bearer object will be created as soon as the LTE attach status
details are known, and only while the modem is enabled. The
implementation allows modems to update the LTE attach status details
during runtime, so the bearer object with the settings may be
recreated during runtime as well.
2018-12-07 16:20:53 +00:00
Aleksander Morgado dc154cf005 api,bearer: new 'BearerType' property
Until now we have only allowed to use and setup 'default bearers' (in
4G) or 'primary contexts' (in 2G/3G).

We can define a couple of additional bearer types, though:

* The 'dedicated bearers' (in 4G) or 'secondary contexts' (in 2G/3G),
  which are associated to a specific default/primary one, but which
  provide specific QoS settings configured via traffic flow templates.

* The 'initial default EPS bearer', which is a special case of default
  bearer in LTE, which is automatically created and connected when the
  modem is registered in the LTE network.

This commit introduces a new 'MMBearerType' enumeration that will be
associated to each bearer through a 'BearerType' property in the
org.freedesktop.ModemManager1.Bearer interface, showing what kind of
bearer/context this is.

By default, right now, all bearer objects created are 'default'
bearers.
2018-12-07 16:20:53 +00:00
Aleksander Morgado 689dad9f6e base-bearer: fix reporting tx/rx stats
The numbers were actually swapped!
2017-10-19 11:43:50 +02:00
Ben Chan 1f4cd9ac91 base-bearer: port mm_base_bearer_disconnect to use GTask 2017-07-03 10:42:57 +02:00
Ben Chan 98f4fe2f85 base-bearer: port mm_base_bearer_connect to use GTask 2017-07-03 10:42:57 +02:00
Aleksander Morgado 34ac81071b base-bearer: use an initial longer timeout for connectivity check
If we ask too quick for the PDP context status after a successful
connection attempt reported by the modem, we may find it still flagged
as inactive if the modem is still busy setting up the PPP session.

Do an explicit longer initial timeout before we run the first check,
and after that one setup the additional checks at a higher rate.

Reported-by: Colin Helliwell <colin.helliwell@ln-systems.com>
2017-06-05 15:18:00 +02:00
Aleksander Morgado 15d135b9c4 base-bearer: stop connection status monitoring if no TTY available
On modems with a single TTY for both control and data, we cannot use
the TTY to load connection status once we're in connected mode:

    Connection through a plain serial AT port (ttyUSB2)
    (ttyUSB2): --> 'ATD*99***2#<CR>'
    (ttyUSB2): <-- '<CR><LF>CONNECT 100000000<CR><LF>'
    (ttyUSB2): port now connected
    Connected bearer '/org/freedesktop/ModemManager1/Bearer/0'
    Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    Simple connect state (8/8): All done
    checking if connected failed: Couldn't check current list of active PDP contexts: No AT port available to run command
    checking if connected failed: Couldn't check current list of active PDP contexts: No AT port available to run command
    checking if connected failed: Couldn't check current list of active PDP contexts: No AT port available to run command
    ...

So, disable connection monitoring right away if that situation is
detected:

    Connection through a plain serial AT port (ttyUSB2)
    (ttyUSB2): --> 'ATD*99***2#<CR>'
    (ttyUSB2): <-- '<CR><LF>CONNECT 100000000<CR><LF>'
    (ttyUSB2): port now connected
    Connected bearer '/org/freedesktop/ModemManager1/Bearer/0'
    Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    Simple connect state (8/8): All done
    Connection monitoring is unsupported by the device
    ...

https://bugs.freedesktop.org/show_bug.cgi?id=100376
2017-03-24 21:49:23 +01:00
Aleksander Morgado 1775544dbc base-bearer: allow deactivating stats loading if device says unsupported 2016-10-12 13:24:09 +02:00
Aleksander Morgado fe460b2f54 3gpp: update registration state enumeration with CSFB related states
Introduce "sms only" and "CSFB not preferred" home/roaming states to be reported
for the CS context, while already registered on LTE.

Based on 3GPP TS 27.007 v13.5.0.
2016-10-12 13:24:08 +02:00
Aleksander Morgado 26d0d718f7 base-bearer: new periodic monitoring of connection status 2016-10-12 11:29:52 +02:00
Aleksander Morgado 7fb366c41a core: use MM-specific logging methods always instead of the generic GLib ones 2016-08-15 13:14:47 +02:00
Aleksander Morgado 3bf118d01a base-bearer: setup periodic stats loading
If the bearer implementation supports it, load stats periodically. By default
every 30s for now.
2015-12-07 14:20:54 +01:00
Aleksander Morgado ffde429843 core: use G_SOURCE_REMOVE and G_SOURCE_CONTINUE in GSourceFuncs 2015-12-02 17:07:39 +01:00
Aleksander Morgado 3ca267b01f bearer: rename 'MMBearer' to 'MMBaseBearer'
Just so that we don't have same header names in src/ and /libmm-glib.
2014-07-06 16:55:29 +02:00