On 10/5/18 8:51 PM, Dan Williams wrote: >> I noticed, that in ip_configuration_query_ready() ipv6_config will be >> allocated and method will be set to MM_BEARER_IP_METHOD_DHCP even >> when >> ipv6configurationavailable is false, just based on the value of >> ctx->ip_type. >> >> So essentially every bearer which was *configured* with ip_type v6 or >> v4+v6 before connecting will report that v6 may be available via >> SLACC. >> This is even the case when the mbim ip configuration response >> explicitly >> says that no ipv6 is available. >> >> Is this intentional or should I submit a patch that takes the >> information from the mbim message into consideration when reporting >> the >> ip6_config? > I could be mis-remembering, but I don't think this was intentional and > if MBIM says IPv6 isn't available, then MM shouldn't say it's available > either. > > Bjorn or Aleksander, do you have more experience here that you could > share?
I agree that this could be a bug, so the patch would be very welcome. -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
