diff options
author | Aleksander Morgado <aleksandermj@chromium.org> | 2023-11-15 15:26:33 +0000 |
---|---|---|
committer | Aleksander Morgado <aleksandermj@chromium.org> | 2024-02-15 21:01:52 +0000 |
commit | f31f42dda1cced436b1927d06fab36507f58210f (patch) | |
tree | df3c3bddca760817423b3c22679e58980c8b73e2 /src/mm-netlink.c | |
parent | b0add8c03b8c2e4588730a494f9abc190c349ba3 (diff) |
bearer-mbim: support async IP configuration indications reporting SLAAC result
When IPv6 is requested during a connection attempt, two things may
happen: either the modem itself runs SLAAC, or otherwise the host is
the one that should run SLAAC.
Until now we have assumed that the first IP configuration query that
is run upon finishing a connection attempt always gives us a "final
result", so if the modem did run SLAAC by itself, we would have
expected to see a global IPv6 reported in that first query. And if
there was no global IPv6 reported, then we would have assumed that the
host was the one tasked with running SLAAC.
There is a third option that we now consider, which is the case where
the first IP configuration query does not report a global IPv6, but
the modem is really running SLAAC, and the global IPv6 address will be
reported via a IP configuration indication as soon as SLAAC finishes.
This third option cannot be assumed by default, because it introduces
the possibility of MM waiting for the indication with the SLAAC
results and that indication never arriving in the 10s timeout used as
default. If a modem is supposed to use this third option, the feature
must be explicitly flagged by the modem plugin.
Diffstat (limited to 'src/mm-netlink.c')
0 files changed, 0 insertions, 0 deletions