On Tue, Mar 28, 2017 at 8:39 PM, Dan Williams <d...@redhat.com> wrote: >> > > RE PolicyMismatch: we're not quite sure what that error >> > > represents; >> > > we've determined that in some cases it means IPv4 vs. IPv6 >> > > mismatch and >> > > profiles in the modem, but that doesn't seem to always be the >> > > case. >> > >> > I'm not sure what is causing it, but it's quite easy to reproduce >> > by >> > messing with the kernel module (e.g. reloading it): >> > $ sudo rmmod qmi_wwan >> > $ sudo modprobe qmi_wwan >> >> My best guess is that you experience some mismatch between an >> auto-connected bearer and the bearer you try to connect. But it's a >> wild guess. Try messing with the preconfigured profiles, changing >> between IP, IPV6 and IPV4V6 contexts and see if you can prevent the >> issue that way. > > Are the QMI "autoconnect" settings actually the EPS Default Bearer, or > are they different? Maybe > > qmicli --wds-set-autoconnect-settings=disabled > > would do the trick, but I don't know for sure.
I don't think the auto-connection in QMI relates to the EPS Default Bearer, although also, not sure :) -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel