Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Unfortunately we cannot fully remove the blacklist name forever, as we
must keep API. We move it to -compat so that it gets removed whenever
we decide to break API.
|
|
|
|
|
|
|
|
The option receives a key-value pair string that can be used to define
zero or more filters.
E.g. if we want to add TCP and UDP packets to the filters, we could run:
$ PF_TCP="packet-filter=40000000000000000006,packet-mask=F00000000000000000FF"
$ PF_UDP="packet-filter=40000000000000000011,packet-mask=F00000000000000000FF"
$ sudo mbimcli -v -d /dev/wwan0mbim0 -p --set-ip-packet-filters="session-id=0,${PF_TCP},${PF_UDP}"
Or, if we want to remove all filters, we could run:
$ sudo mbimcli -v -d /dev/wwan0mbim0 -p --set-ip-packet-filters="session-id=0"
|
|
This command is an extension for the existing MBIM_CID_IP_PACKET_FILTERS
defined in the MBIM specification revision 1.0. This extension adds a new
member called "FilterId" to the data structure to set command and response.
|
|
When cross-compiling, the compiled binaries cannot be run on the build
machine, unless one defines a helper (e.g. qemu) in the meson
configuration, which is most of the time undesirable.
If help2man is installed on the build machine, then the build would fail
because of this, so add an option to disable generating the man pages.
With later versions of meson, it will be possible to automatically
detect this condition.
|
|
`MBIM_USERNAME` is quoted twice in the
`76-mbim-proxy-device-ownership.rules` rules file. This is because
the definition is used in two files.
The first one is `config.h` file, that is used in source code files
and needs to be explicitly quoted. The second one is the rules file,
mentioned above that already has quotes in the template file.
The explicit quotes have been removed in the rules file generation.
Fixes #21
|
|
|
|
|
|
When running the tests normally under ninja, the output is not verbose
at all; so we can enable the traces by default so that we get them if
we run the tester manually.
|
|
|
|
This CID is used by host to query the modem for its wake reason when
power up because of device wake. If the device supports this function,
but fails the query from host, it means the power up is not caused by
a wake from the device.
Includes updates by Aleksander Morgado to fix coding style issues,
message definitions add missing documentation items.
|
|
This CID is used to notify the host of the configuration progress and
parameters of the device. This CID is added as part of MBIM 3.0
extension.
Includes updates by Aleksander Morgado to fix coding style issues,
memory handling fixes add missing documentation items.
|
|
|
|
In this version MBIMDataClass5G_NSA and MBIMDataClass5G_SA are renamed
to MBIMDataClass5G with corresponding data subclasses. These subclasses
will give more detailed combination of 5G attach possiblities.
|
|
This is a TLV that contains an array of guint16 values. For now we
only add reading support,
|
|
|
|
The type is introduced in MBIMEx v3.0, so just name it with the v3
suffix, not to confuse with the updated introduced in MBIMEx v2.0,
which is compatible with the original type in MBIM v1.0.
|
|
|
|
|
|
The logic now uses the read_tlv_string() method, using the new TLV
types.
|
|
The data length needs to be converted to HE before using it.
|
|
|
|
We're not taking a full reference to the MbimMessage with
g_object_get_data() and therefore we must not free the object when
going out of context.
|
|
|
|
|
|
|
|
MBIM extension spec already provides update on ready state
to inform the host on whether the inserted esim has profile
in it or not. This needs an enum addition to enhance the info
capability.
|
|
|
|
|
|
|
|
|
|
|
|
These two fields should be treated as optional fields that may or may
not be given in the message response, and therefore %NULL is a valid
output value for them even when the parsing is successful, unlike most
other fields in the MBIM protocol.
|
|
The supported way to use the connect operation is through key-value
pairs; the positional arguments method is fully deprecated and should
no longer be used or updated.
|
|
This type was the original implementation of string TLVs, that
required an intermediate struct to exist. The new 'tlv-string' type
hides the need of the intermediate struct, and so this old type is no
longer needed.
|
|
The logic is updated to avoid requiring intermediate structs in the
API; for the string TLVs that are included as named fields we'll use
the 'tlv-string' types.
We also add support for the unnamed IEs as 'tlv-list' fields at the
end of the messages.
|
|
|
|
|
|
The Microsoft Extensions define a new generic TLV type that allows
including any kind of data in it: from strings, to arrays of uints, to
more complex types.
We define support for the generic 'tlv' type and the generic
'tlv-list' type, which allow implementing the "unnamed IEs" that are
appended to some new messages in the MS extensions.
And we also define support for a more specific 'tlv-string', used
exclusively when the TLVs are part of the named fields, so that we can
provide strings in our libmbim-glib APIs, instead of requiring the
user to build MbimTlv instances.
|
|
This command is an extension for the existing MBIM_CID_CONNECT defined in
the MBIM specification revision 1.0. This extension adds 5G SA specific
parameters.
|
|
The PLMN field is not a single 32 bit value, it's really 2 separate
guint16 values. This is important because the endianness change in BE
systems would be different.
Also, the format of the MCC and MNC inside the PLMN fields is very
specific to the implementation (BCD encoded, MNC PCS digit indicated
in most significant bit of the MNC field...).
|
|
printed
No need to fully print the whole output in v3, just print the extra
new things.
|
|
This command is an extension for the existing MBIM_CID_PACKET_SERVICE
defined in the MBIM specification revision 2.0.
|
|
|
|
If a given command didn't change in the new version update of the
service, skip creating methods to handle it, just use the ones from
the original version.
|
|
If a given command didn't change in the new version update of the
service, skip creating methods to handle it, just use the ones from
the original version.
|
|
If a given command didn't change in the new version update of the
service, skip creating methods to handle it, just use the ones from
the original version.
|