On Wed, 2017-02-15 at 21:14 +0100, Aleksander Morgado wrote: > On Wed, Feb 15, 2017 at 9:00 PM, Russ Westrem > <lspwaterproof...@gmail.com> wrote: > > Is there anything in the modemmanager scripts that I could change > > to have it > > ignore the deregistered modem and stop it from removing it from the > > bearer. > > I have a feeling these deregistrations happen often but very > > quickly and > > maybe if ignored, everything might work. > > You mean you want to totally ignore the modem-reported de- > registration > notifications to see what happens? I'm not sure that is easily > decoupled from the logic; maybe you can try to avoid connecting the > "serving-system" signal in > common_setup_cleanup_unsolicited_registration_events() in > mm-broadband-modem-qmi.c.
That shouldn't have any effect though, really? MM's logic on bearer initiated disconnection just changes some state, but doesn't do anything material to the WDS client. The WDS client and packet data handle are still there and haven't been cleaned up. Whether you can actually use them for anything is another question. But Russ, I don't quite understand why you'd want to ignore the deregistration, unless it's just for testing. If it's not for testing, well, the network kicked you off, and your packet bearer is likely gone (since the network has released resources for it when it kicked you off), and the IP details are gone too. That's not the modem, that's the network. The only thing you can really do is request a new bearer. Dan _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
